Everyone, Looks like 0.8.5 is "delivered". Congratulations to all concerned!
Now, what's next? I have one immediate agenda: I'd like (me and/or anyone else) to quickly refactor the existing code according to modern object-oriented/pattern practices to achieve the following benefits: 1. Reusability. It is virtually useless to subclass anything in the TableTag; its methods are excessively "coarse". 2. Appropriate Coupling. There is no reason for the same class to handle HTML output _AND_ XML _AND_ Excel _AND_ etc. etc. These renderers should be in separate classes. There are probably other reasons as well, but these reasons are the driving forces for me. I have already refactored TableTag for internal use and have added several features I think the group would be interested in; however there is no chance of folding them in smoothly with the code implemented the way it is. When this is done, it will be much more likely that people who are presently hacking away at copies of this tag library will instead offer their enhancements to the open source. Perhaps we could, as a group, play with a class diagram; when we're close one of us could refactor the actual code. Maybe test the code on a branch. Anyways, I'm in favor of moving now while the table tag is not so complex that it can't be done quickly. Any other thoughts? -Scott Smith ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
