Why not just do what WW1 had and create a base class for each tag, something like HTMLComponentTag that has all the HTML attributes in it? (onchange, onmouseup, class, style, id etc)
M On 3/7/03 6:24 PM, "Matt Ho" ([EMAIL PROTECTED]) penned the words: > Ara brought up a really good point about the existing ui tags. There's > really no mechanism to pass along additional presentation information > such as onChange for HTML views or fetchhint for VoiceXML views. The > param tag is available, but that seems a little heavy for this. It > strikes me this would be a good thing to have, but doing it the struts way > > http://jakarta.apache.org/struts/userGuide/struts-html.html#text > > seems silly. Under Velocity, this would be pretty easy: > > #tag( TextField .... "onChange=blah blah" "onMouseUp=..." etc ... ) > > the data could then be stored into an internal attribute map (or perhaps > the existing param map). The question, however, becomes what does the > JSP version of this look like? > > Thoughts? > > M > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
