I enjoy admitting when I am wrong, when I am really wrong. The first thing I whacked when I refactored Ed's library was the concept of Decorators. Personally, I thought that the idea was too heavy for a simple table library. It requires table users to write java code which at the corporate app developer level invites disaster! I replaced it with built it sorting intelligence that ... is still flawed, buggy and will never be correct because correct is subjective when it is your data on display.
Decorators are good, but I still don't like the fact that it is a class instead of an interface, but we can work with that and maintain backwards compatibility. So, this library we are working on has decorators. I like them becuase it permits the user to customize his view without changing the displaytag library. They are correctly a good part of what we are offering. In fact, we should be offering more of them (which I believe has been mentioned before). I am proposing a separate module (or at least a package) that consists of Decorator implementations. I am sure there are displaytag users out there with Decorator extensions that could be reused as well. What do you think guys? Is anyone awake? Ben ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
