Sorry, I didn't mean dropping JSPs... I meant that this kind of
component communication (like having a UI component able to add
javascript to the header) would not be possible in JSP. I don't think it
would be possible (easily) in Velocity either. I'd love to be wrong
about that, of course, but both of these technologies write out to a
Stream as they process the page, so it's hard to go back and insert
things earlier in the page... I think this would require some kind of
multi-pass processor to run the page then render it.

> -----Original Message-----
> From: Chris Widhelm [mailto:[EMAIL PROTECTED] 
> Sent: Monday, September 22, 2003 11:28 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] Thought concerning HTML form rendering
> 
> 
> -1 on dropping JSPs from WW technologies.
> 
> One of my selection criteria was that the MVC provided 
> support for JSPs.  I personally don't have time to learn a 
> new framework and a new display technology at the same time 
> (e.g. velocity).
> 
> My two cents,
> 
> Chris
> 
> ----- Original Message ----- 
> From: "Jason Carreira" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, September 22, 2003 10:10 AM
> Subject: RE: [OS-webwork] Thought concerning HTML form rendering
> 
> 
> 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
> 
> 
> 
> -------------------------------------------------------
> 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
> 


-------------------------------------------------------
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

Reply via email to