Re: Question / Best Practise / (List)Model vs. (List)DataProvider

2014-05-22 Thread Patrick Davids
comprise their data. > > DataProvider could be described as a 'Model Factory', and is not a Model in > itself. > > Cheers, > Col. > > -Original Message- > From: Sven Meier [mailto:s...@meiers.net] > Sent: Friday, 16 May 2014 6:17 AM > To:

RE: Question / Best Practise / (List)Model vs. (List)DataProvider

2014-05-18 Thread Colin Rogers
data. DataProvider could be described as a 'Model Factory', and is not a Model in itself. Cheers, Col. -Original Message- From: Sven Meier [mailto:s...@meiers.net] Sent: Friday, 16 May 2014 6:17 AM To: users@wicket.apache.org Subject: Re: Question / Best Practise / (List)Model

Re: Question / Best Practise / (List)Model vs. (List)DataProvider

2014-05-16 Thread Sven Meier
IDataProvider is all about efficiency, it provides efficient access to a subset of the data. Perhaps we can make it even more efficient with the recent proposal on the @dev list. Regards Sven On 05/08/2014 01:37 PM, Patrick Davids wrote: Hi all, what I often think about, and I cannot real

Re: Question / Best Practise / (List)Model vs. (List)DataProvider

2014-05-16 Thread Paul Bors
Models: http://wicket.apache.org/guide/guide/modelsforms.html Data Providers (ie: Repeaters): http://wicket.apache.org/guide/guide/repeaters.html Long story short, a repeater's DataProvider gives you a single items model. A model who wraps a collection, gives you a collection of items for a singl