Currently we have two classes providing navigation for pageable list
views: PageableListViewNavigation and
PageableListViewNavigationWithMargin with the latter providing a
pageable navigation. Assuming your list has 1000 entries and your
pages 10 entries each, the navigation would have 100 links. It is very
unlikely that you want to print a navigation bar with so many links.
PageableListViewNavigationWithMargin, similiar to PageableListView
provides a pageable navigation bar with a maximum number of links
(view size) and automatic adjustment of the windows. E.g. current page
is 16, the windows will automatically be adjusted to print page link
for page 16 somewhere near the middle of window. A very useful feature
for next/prev button as well. E.g.
[first | prev] 14, 15, 16, 17, 18, 19 [next | last]
IMO PageableListViewNavigation in itself is not very useful because it
is missing the features, which is the reason why I suggest to move the
extra functionality into PageableListViewNavigation and remove
PageableListViewNavigationWithMargin. And I think it cleans up the
overall usage of navigation a bit.
What do you think? any objections?
Juergen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
