I'm all for adding cool taglibs like eg. menu's or tabs or other presentation goodies. If we are going that road, we should set up some direction, such as which browsers, DHTML or all server side, using third party javascripts (webfx) etc.
The thread originally started with examples for new tags like simple string formatting, and I think that is already covered by Jakarta. Mathias ----- Original Message ----- From: "Fabrizio Giustina" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 01, 2003 8:46 PM Subject: RE: [displaytag-devel] DisplayTag Mission I agree with Andy here... There are still many features that can be added to the table tab, but there are also new useful tags that can be implemented. Jakarta taglibs are not focused on presentation, so there is still lot to do there. My proposal for the plan is: - fix known bugs in the current beta and release a stable version - add el support (using Jakarta el package) in the 1.1 version - start developing new tags based on a stable code base, removing everything is now deprecated - all the tags based on el support I think there is a lot of space for simple tags which can simplify development with jstl. For example tags to output html form elements starting from lists or maps, tags to output menu or tabbed layers, and so on... fabrizio -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Pruitt Sent: Friday, October 31, 2003 4:17 PM To: [EMAIL PROTECTED] Subject: RE: [displaytag-devel] DisplayTag Mission > > I tend to disagree. For starters, there are already a lot of > tags that do this, such as Jakarta Taglibs > (http://jakarta.apache.org/taglibs/). The jakarta tags are really focussed on cfml-like or programming functionality; tags like cache, dbtags, logs, mailer, scrape. There's not really anything there (outside of the JSTL tags) that are focussed on presentation. > I think we should focus on table design (everything where > lists need to be displayed). There is a lot left to be desired, among: We have a huge brand. We have approx. 10 committers, and many active contributors, but only a handful of classes. The table tag is important and large, and should continue to be the centerpiece of the library, but there is no reason that we can't accomplish much more. My gut feeling is that although there is still much work to do on the table tag, the main bulk of the work is complete. We don't need 10 developers to just maintain one custom tag. Tabletag 2.0 may have some important differences. We might move the text formatting code into independent tags, and issue a release that removes support for 1.0 deprecated features. But, I think the project should have an explicit agreement on general direction before any tabletag 2.0 planning discussions begin. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
