yes but that is the same with the normal listview..
As long has he is showing the same indexes.. Which he does.
If you are showing db objects or a real grid then dataview is handy in
that optimized
Because dataview really compares the model if he can reuse the item...
But i dont think in his case that is needed. (it is more a dynamic for
or something like that)
johan
Phil Kulak wrote:
Oh, looks like you have to explicitly set userOptimizeItemRemoval now.
However, when you do that, it is all handled for you. Take a look at
populateItemsOIR().
On 8/30/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
how so?
private void populateItems()
{
final IDataProvider dataProvider = getDataProvider();
final int size = getViewSize();
super.removeAll();
that one is called if you don't do optimizedRemoval
so also then very component (== dataitem with its content) is recreated
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
-------------------------------------------------------
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
