No it is not the same issue again.
However I was thinking about it and somehow realized that most of pagable
db views have identical rows (with different data of course).
So I though maybe even a stronger optimization than optimized item
removal, would be to build at the start of DataView all the DataItems for
the viewSize and allways keep them. Than just repopulate the dataitems
through populate(DataItem dm,IModel newModel) with the new data. The non
used DataItems should be hidden.
I also wonder why the DataItem needs an IModel, wouldn't it be enought to
pass the object gotten from the iterator straight through to
populateItem(DataItem i, Object data)?
Christian
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-------------------------------------------------------
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
