> Because defining how many rows there are are useless if you don't attach > a paging component...
I disagree. So you're stuck on page one with no way to get to other pages until you add a pager. What's the problem with that? I don't think it's so disasterous that we need to clutter the IPageable interface. Let the pageable component worry about how it renders itself and and the pager worry about paging. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
