> 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...
Once again, I don't understand the flexibility issue. We were not talking about replacing the imodel interface, but the list interface, both approaches can be wrapped in an imodel. What flexibility do you lose? Igor ------------------------------------------------------- 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
