I haven't, but this sounds like a great idea to me. This sounds like what Tapestry does (from what I know of it), but I've never been clear on how it does it. I think it may require the dumping of JSP to be able to add things to the header (Tapestry does not use JSP), which is fine for me, but I'm not sure about everyone else.
If anyone has thoughts along these lines I'd love to hear them and see them get into WebWork2... For now the <ww:component> tag lets you componentize your JSP page by using custom templates, but it's not as advanced as what you're describing. Jason > -----Original Message----- > From: John Patterson [mailto:[EMAIL PROTECTED] > Sent: Monday, September 22, 2003 10:37 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Thought concerning HTML form rendering > > > Hi Jason. > > Have you given any more thought to how components would work > with WW? Currently I use the Include tag to build my page up > from smaller parts. This is quite limiting though. It would > be great if components could interact with each other. ie A > date picker could add some JavaScript the header and maybe > interact with other date pickers (ie when from date is > increased, to date can be increased automatically). Or a > form field could add some JS code to the form validation > function that determines whether the page can be submitted or not. > > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork