I share your pain on this one. I too am a "subform user" in all my web applications, and I was hoping that you'd have the solution to this little thorn in the side.
Like you, most of my apps have common html that's used on (nearly) every form, and therefore, shoving all this into subforms saves lots of time. For example, one of my subforms contains the beginning of a html tag set, and another closes said tag set. Placing these two subforms into a form creates a "container-like" html element. I like that design method, so naturally, I *expected* XPages to accommodate. And so, noting that custom controls are supposed to be "subforms on steriods", I added some custom html to a custom control and hit 'save' ... only to find little red X's in my designer sidebar because my html elements are unclosed (WTF?! ... ugly).
And so, as I hear that the new XPages method means throwing out all aspects of traditional Domino Dev, I wonder how we're supposed to store partial html blocks without those ugly errors. Further, I note to myself that our method of subform development is a very, very good way to design new applications, and now I'm stuck. The only other solution that I see is to retype this common html e v e r y time a new XPage is created... which is not ideal. In my opinion, this is a major drawback to XPages development. (Not to mention what happens if the user turns off JavaScript)
I liked subforms just fine before they went on the juice.
Hi Jake,
I share your pain on this one. I too am a "subform user" in all my web applications, and I was hoping that you'd have the solution to this little thorn in the side.
Like you, most of my apps have common html that's used on (nearly) every form, and therefore, shoving all this into subforms saves lots of time. For example, one of my subforms contains the beginning of a html tag set, and another closes said tag set. Placing these two subforms into a form creates a "container-like" html element. I like that design method, so naturally, I *expected* XPages to accommodate. And so, noting that custom controls are supposed to be "subforms on steriods", I added some custom html to a custom control and hit 'save' ... only to find little red X's in my designer sidebar because my html elements are unclosed (WTF?! ... ugly).
And so, as I hear that the new XPages method means throwing out all aspects of traditional Domino Dev, I wonder how we're supposed to store partial html blocks without those ugly errors. Further, I note to myself that our method of subform development is a very, very good way to design new applications, and now I'm stuck. The only other solution that I see is to retype this common html e v e r y time a new XPage is created... which is not ideal. In my opinion, this is a major drawback to XPages development. (Not to mention what happens if the user turns off JavaScript)
I liked subforms just fine before they went on the juice.