AbstractPageableView introduces automatic flushing and repopulation of items into the repeaters, that is why the strategy lives there. it wouldnt make sense for it to live in the repeatingviews imho. by default the number of rows is set to Integer.MAX_VALUE so effectively the paging is disabled. you can easily extend abstractpageableview and use that if you do not want to use the dataprovider interface.
perhaps we can introduce something between the pageable view and the repeating view. factor out the repopulation into that and only introduce paging in the pageable view. i will need to evaluate that idea when i have a bit more time.
-Igor
On 11/29/05, Laurent PETIT <[EMAIL PROTECTED]> wrote:
Hello,
I've looked with *great* interest the Repeater/OrderedRepeater ...
stuff in wicket-extension, as suggested to me by Igor.
When reading it, I was surprised by something I want to share with you :
Why not introduce the concept of IItemReuseStrategy at the
OrderedRepeater level (should also be of interest at the Repeater
level, except the fact that in this case the index parameter will not
be usefull).
Indeed, I would like to only use the "Ordered" aspect of the repeater
for Forms, not the Pageable (no interest with the current strategy
used for Forms submission/validation).
Any reason I didn't see to not having done that ?
If no, could it be refactored to be so ?
My 0,02 EUR,
--
Laurent
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&opclick
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
