this is a good point. it may be that my idea to combine this is wrong. maybe we should go the opposite direction by creating a ListViewNavigator component that lets you page through a list view and a ListViewSorter component that lets you sort a list view by column. then you can attach these to the ListView you want to work with. does that make more sense?
Juergen Donnerstag wrote:
That sounds like a very easy user interface to use. But I'm not sure how easy it'll be to implement without loosing flexibility. Talking a look at the html markup, the header is not contained within the table. Even worse, the navigation bar seems to me could have many many different look and feels. That is, we may need to provide some means to sepcify different implementations. If that is true, what is the difference between Components and such classes?
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
------------------------------------------------------- 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
