> How would you envision it working? Thats where I thought you could help :)
Currently I define templates with "holes" in them to be filled in by include tags. Then in my xwork.xml action definition I define static parameters such as "<param name="main">car.jsp</param>. I use an action base class ParametersAction which implements Parameterizable and pushes all the static params onto the stack for use from my page. This works great. I am a little concerned about the overhead of using the servlet dispatcher for each of these included components (should I be?) Component actions could be called directly without using the servlet dispatcher. As for components interacting together, I don't know what is possible with JSP tags. One of the problems is getting a child tag (lets say a text input field) to add content to a parent tag (eg put an onLoad in the body tag). Maybe this could be solved by caching the body content and then prepending or appending the parents content. John. ----- Original Message ----- From: "Pat Lightbody" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 6:49 AM Subject: [OS-webwork] HTML Components [Was: Thought concerning HTML form rendering] > John, > I did this kind of stuff all the time in WebWork to some extent, but not at > the level of interaction you've proposed. > > -Pat > > ----- Original Message ----- > From: "John Patterson" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, September 22, 2003 7:36 AM > 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. > > > > > > ----- Original Message ----- > > From: "Jason Carreira" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, September 22, 2003 3:23 PM > > Subject: RE: [OS-webwork] Thought concerning HTML form rendering > > > > > > Well, I would hate to have custom object types for this.... Tying apps > > to WebWork is opposed to the general WebWork idea. > > > > I see where you're coming from, but I'm not sure (without the custom > > types) how you can specify text vs. textarea... Also, how do you specify > > a radio-button set with enumerated values vs. a text box. > > > > I'm all for custom components, though, and I think adding things like a > > pre-built date-picker, etc. would be very valuable. > > > > Jason > > > > > -----Original Message----- > > > From: Joseph Ottinger [mailto:[EMAIL PROTECTED] > > > Sent: Monday, September 22, 2003 8:26 AM > > > To: [EMAIL PROTECTED] > > > Subject: [OS-webwork] Thought concerning HTML form rendering > > > > > > > > > Would it be better to have something like this: > > > > > > <ww:field name="foo.bar" label="'Bar'" /> > > > > > > instead of > > > > > > <ww:text name="foo.bar" label="'Bar'" /> > > > > > > Consider: the rendering engine can see that the field is a > > > String, so it can generally figure out the rendering type. > > > Maybe String isn't a brilliant idea - maybe there's a > > > possibility of creating new types in WebWork such that the > > > form can look at the type and say "Gee, this is supposed to > > > be a textarea, let's render it that way," or "Gee, this is a > > > numeric type, integral, let's generate an input field that > > > doesn't allow non-numerics or decimal points," etc. > > > > > > No, I don't have any code to show off for this, nor am I > > > convinced this is a "solution," and in fact, I'm not even > > > sure there's a problem... just trying to think in terms of > > > how a user might use this, without having to know the > > > destination types. Imagine: a Phone type, or a ZIP, or a > > > State... all with custom renderers that don't require > > > anything special on the front end... just a reference to the > > > field in question. > > > > > > ------------------------------------------------------------------- > > > Joseph B. Ottinger http://enigmastation.com > > > IT Consultant [EMAIL PROTECTED] > > > J2EE Editor - Java Developer's Journal [EMAIL PROTECTED] > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > > > ------------------------------------------------------- > 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
