--- Chris Gastin <[EMAIL PROTECTED]> wrote: > As I can tell from the list I have opened topic that is pretty well > beaten. > Let me first apologize. I did not realize this was such a political > topic > in the Struts community.
I wouldn't describe anything in Struts as political. We've all openly stated our opinions and reasoning. > > I am starting to think that there should be some sort of Struts Tag Lib > Extensions, which would address some of these issues while being totally > separate from the Struts project. I am starting to agree with David I > don't > want to polute Struts with non standard HTML, but it would be nice to > have > an add on module which is dependant on Struts that could give users the > functionality which it seems that other are requesting. I am willing > contribute to this effort. > > I did not realize there were so many bugs for the taglibs, which some of > you > pointed out. I will see if I can help out. I will check out bugzilla, > and > try to contribute in that area. I ran an informal bugzilla report a while back that indicated a large percentage of our total historical bugs are custom tag related. I don't remember the exact number but it was between 25% and 50%. This is one reason I don't think duplicating JSTL functionality is a good idea. David > > Chris Gastin > > ----- Original Message ----- > From: "David Graham" <[EMAIL PROTECTED]> > To: "Struts Developers List" <[EMAIL PROTECTED]> > Sent: Thursday, September 25, 2003 3:39 PM > Subject: RE: Editable Fields V/S Static Text > > > > > > --- Edgar P Dollin <[EMAIL PROTECTED]> wrote: > > > I think it is more than a 'preference' based on the rapidity with > which > > > INVALID or WONTFIX is stamped on tag suggestions and patches. > > > > I can't speak for anyone else but here is my view on the tags: > > > > There are 3 things that earn my -1 on tag enhancements: > > 1. Functionality already provided by the JSTL. > > 2. Functionality that supports non-standard HTML generation. > > 3. Tags that don't tie into the Struts core functionality. These are > > better suited for the Jakarta Taglibs project. > > > > I'm personally open to other tag enhancements. If you check cvs, > you'll > > see that I have volunteered some time at refactoring and enhancing the > > tags. > > > > Whenever tag extendability enhancements are discussed, we always hear > > complaints from a vocal minority but no tested working patches show > up. I > > haven't heard any good suggestions that would make the tags easier to > > subclass. If the current factoring isn't good enough, provide patches > for > > something better. > > > > The fact is that the current tags work great for my needs so I'm not > > motivated to spend a bunch of time pondering some ultimate > extendability > > framework. There's not much we can do without use cases and patches. > > > > David > > > > > > > > Perhaps it would be best if the tags were cut loose from struts and > a > > > different group of committers were responsible for them. I > wouldn't, > > > nor > > > would I expect anyone else interested in the tags to make any time > > > commitment with the current 'RULES' placed on the tags, i.e. ONLY > emit > > > HTML > > > 4.01 or XHMTL 1.0, only a 'thin' layer over standard html tags, etc. > > > > > > Edgar > > > > > > > -----Original Message----- > > > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > > > > Sent: Thursday, September 25, 2003 2:23 PM > > > > To: Struts Developers List > > > > Subject: Re: Editable Fields V/S Static Text > > > > > > > > > > > > It's only a "political football" in the sense that most of > > > > the current > > > > committers would prefer not to work on the HTML tags. If other > folks > > > > came to the fore and committed themselves to supporting those > tags, > > > > including writing unit tests and answering questions on the > > > > user list, I > > > > don't think you would see much opposition to development in > > > > that area -- > > > > along with an eventual nomination for committer status for the > > > > individuals involved so that they can do their work directly. > > > > > > > > Asking the existing committers to do all the work isn't the way to > > > > leverage how open source operates :-). > > > > > > > > Asking the existing committers to apply patches (and add unit > > > > test cases > > > > that already work), and pestering them until they get around > > > > to it (or > > > > nominate you to committer status so you can do it yourself) > > > > *is* the way > > > > to leverage how open source operates :-). > > > > > > > > Craig > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Shopping - with improved product search > > http://shopping.yahoo.com > > > > --------------------------------------------------------------------- > > 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] > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
