Alternatively we should make an PageableOrderedRepeatingView.
I want to wait for the new navigation to be done so we don't need to have
the regular - pageable pairs.
I am currently inclined to keep this difference.
Because now i have
IPageable
{
getCurrentPage();
setCurrentPage(int);
getPageCount();
}
and i think i will make this one:
IRangePageable extends IPageable
{
getRowsPerPage();
getMaxRows();
}
instead of
IRangePageable extends IPageable
{
setRowsPerPage(int);
getMaxRows();
}
i think setting the number of rows a page should display is a property
of the View that displays them
Not something of the Navigation/Navigator that is attached to it..
But if others are more in for pushing the rows per page instead of
pulling then i could change my mind.
and ListView doesn't have to be a RangePageable it could also be used to
display a panel and that it is only a Pageable
So giving a listview by default the RangePageable interface is also wrong.
ListView could be directly an IPageable and PageableListView an
IRangePageable.
looks that logical?
johan
johan
-------------------------------------------------------
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
