You are right I can do that no problem. What I was trying to achieve in all these discussions is to create a simpler/standard/non-list-dependent/more user-aware way to do this because I thought other people would have the same problem and thus would need a similar solution. However, since no one chimed in on this, I guess I am alone. So, maybe, the best solution is for me to roll my own version of listview that works how I want it to and leave the framework default as it is since it looks like it works for most people.
Discussing on improvements is allways good. I think we could improve in the field of type safety, and model clarity. However, as far as I can see, this is hard/ impossible to do without either losing flexibility (e.g. being able to use property models directly) or ending up with a lot of semi duplicate models (like a property model for the normal IModels, and a property model for ListView models). I might have overlooked something though...
I think for right now, it is best to make this an RFE for 1.2, and keep focussing on 1.1 features which we do agree on for now. I opened an RFE at : https://sourceforge.net/tracker/index.php?func=detail&aid=1244593&group_id=119783&atid=684978
Regards, Eelco ------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
