Martin Cooper wrote:
In light of how *I* build web apps today, we don't need the taglibs at all! ;-) ;-)
Ironically, I don't think I've ever used the taglibs in a production app at all, so you and I would agree on that point :)
But, I do think there is an opportunity to encapsulate some more functionality than is there now and make them more versatile and overall useful in more "modern" webapp development. They almost get in the way now if your trying to do more advanced things, and I really don't think that needs to be the case.
If there are some ideas floating around on how to do that, why not be receptive to them? I think the slippery slope that James referred to is a completely valid concern, but one that can be managed. To not want to develop them because they might be considered "feature-complete" now doesn't strike me as a great argument... I think the automobile circa 1969 was pretty close to feature-complete at the time... love that '69 Mustang :) ...but new ideas came about, and they got incorporated, and now we realize that calling cars feature-complete back them would have been wrong. Might that not be the case with the taglibs now?
But, this boils down to there being some ideas and someone being able to convince everyone they are worth wild and, of course, willing to do the work. But, it also comes down to those who have commit priveleges being willing to entertain the ideas.
Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
