On Sun, 09 Jan 2005 11:36:37 -0800, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > this package may have the features we want, but it's gotten sloppy. i > think we ought to refactor it so it becomes consistent in terms of > naming. also, there are some confusing API issues to resolve. like > what is the different between > SortableTableHeaderGroup and SortableTableHeaders? should both of these > be public? >
This s from javadoc: ...Headers * This is a convinient component to create sorted table headers very easily. * It first scans the markup for <th id="wicket-.*" ..>> tags and * automatically creates a SortableTableHeader for each. * <p> * The component can only be used with <thead> tags. Because it is a component, it probably should be public. Except we provide something lke SortableListView and SortablePageableListView and SortablePagesableListViewWithNavigation and so on. It is different for the ..Group though. It is a kind of helper to group all sortable columns (must not be all columns) of a ListView. I can imagine to hide it within a SortableHeader, say a static Map, but than the key must be unique for all sortable headers of table (not single header). May be we could use the "parent container relative path" + autoIndex or "the underlying tables relative path" + ".headerGroup". Juergen ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
