> I don't think this will work with the current structure of this tag. > Without using a real iterate-like structure, you'll never really be > able to customize the pieces that most users want to customize > without adding hacks like decorators.
Does you "table-york" module use this iterate-like structure? I'd love to use JSTL's iterate stuff and just make display 1.0 require a 2.3 container. > I don't understand why you would want to be able to override the > title attribute from within the <display:column>, the table column > only has 1 title, so what's wrong with using the title attribute to <display:column>? Only because with Struts I have to use a scriptlet to set the title from a ResourceBundle - that's the only reason. > I know I've said this a million times, but these are exactly the > reasons why I refactored all this code to begin with. I'm not even > sure it's worth adding any new functionality in the existing code > base. In my opinion, you be better off declaring a brand new 1.0 > release that will have better structure and customizabilty but not > necessarily be backward compatible. Many of the features in this tag > are not needed once you can actually customize the <display:column> bodies. I'm interested - does you code provide this? Can I convert all the examples to use your code and all the functionality will be provided? I'm ready and willing to work to make this happen. Let me know what I need to do. Thanks, Matt ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
