Definitely a great idea to do some clean up - take the opportunity to correct design mistakes or legacy across the board. I'd need to think more carefully on it but I don't actually think there's much that I'd want to change about the input taglib. It's pretty barebones... Maybe some renaming of attributes based on the current bug-discussion on the options Map attributes. Summary: I'm not finding it limiting working with backwards compatibility in mind.
Cheers, Karl -----Original Message----- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Wednesday, 23 November 2005 1:31 p.m. To: Tag Libraries Developers List Subject: Re: Input taglib On 11/22/05, Karl von Randow <[EMAIL PROTECTED]> wrote: > Thanks, > > Yes, attributesText remains so you can work it both ways :) There's > even an attributes map that takes names and values. > > I did notice that struts used styleClass. I based className on other > implementations with the same problem, it seems to be a bit of a > defacto > standard: > > http://www.mozilla.org/docs/dom/domref/dom_el_ref4.html > > http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/c > lassna > me.asp > > I think it is a case of 'no way to do it'. The <jsp:useBean> tag just > tantalises us :) > > Yes I've read about Silk but I'm not completely up with the play on > where and how it's happening. I guess it's an opportunity to ignore > regression and throw out deprecated bits and pieces? > <snip/> Well, its been silent for a while, atleast as much as I'm aware. But I do wonder whether that might serve as an opportunity to do some "clean up" as you point out above. Opinions? -Rahul > Cheers, > Karl > <snip/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
