Matt wrote: > > Personally, I don't think there's any reason to do menus or tabbed > layers with the displaytag. But that's only because I currently work > on a project that does this - struts-menu. Demo at > http://raibledesigns.com/struts-menu. I think it might be better to > enhance that library rather than enhancing the displaytag. New <SNIP/> .. > > So I guess what I'm trying to say is that it might be better to use the > brains on this team to enhance existing projects that have "display" > functionality, rather than duplicating efforts. Especially when I have > admin rights over both projects ;-).
As a user, I think there is a real benefit to being able to get my tags/components in one place. It would be better for the users and for the community to have fewer, stronger projects. It's all about the brand. I think DisplayTag, I think presentation tags. Didn't Ed's original vision include adding tree structure navigation to the library? What's more, I think it would be perfectly fine for DisplayTag to adopt best-of-breed presentation components and projects. Why not put it all in one place? Wouldn't it make sense to promote projects like struts menu to the display tag user base? --andy ------------------------------------------------------- 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
