Hi,
ok, now I understand. You are right that you "loose" state information for ListItems like visibility and I guess besides setOptimizedItemRemoval() (which in this case is not very obvious) there is no other means today. As wicket is about components and extensability, may be you can come up with patch to ListView or an extension to it to achieve exactly that.
well for the moment I'm quite happy with setOptimizedItemRemoval, but I think this will not last very long because removing all components isn't the thing to do when a model update occurs. When I need this functionality I will see what I can do. Getting this "done right" seems to be a bit tricky... I think the right solution would involve not working with collection indexes for matching model object and ListItem. One solution could be building an internal map of model objects and ListItems (so it doesn't get out of order when removing or adding items from the model list). The populateItem method could be called with the ListItem which maybe was generated already, so the populateItem method can decide if it wants to generate (first time) or regenerate or refresh the components. I'm not sure if this is the right way and if this should be implemented as patch to ListView or as separate component... What do you think?
Regards, Ralf ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
