2) in order to use primary keys we need to translate an object into a
pk-based model. Currently this is done by overriding a method in a listview,
however, this is a horizontal concern and should be separated.
I don't want those methods in the model. That is a -1 from me.
I like the current way of overriding a method so that you can make
you're own ListItemModel so that you
can decide what to store and what not.
If it is not clear that you can do that then we need some other way to
let you know that you can make youre own listitemmodels
3) a more concrete interface makes it a lot clearer to see what is needed.
Interface ListViewDatasource { List getItems(first, count); int
getTotalItemCount(); Imodel getObjectModel(Object o) } presents a much
clearer picture as to what needs to be done and how listview works.
What does that IModel getObjectModel(Object o) do there?
What should it return? Not clear to me.
-------------------------------------------------------
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
