Hmmm, little late, but - now I understood your intention. Interface, simple, powerful, but limited only to the navigation component. Then your 3 method interface is enough.
Where exactly is it going to be used? Only to describe some page footer, or something more? Dariusz Wojtas On 8/3/05, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > this is where we differ. my first guess is that a page has no "size". > it's an abstract thing. > > Dariusz Wojtas wrote: > > >If I understand correctly, IPageable describes something that: > > * represents some range of data > > * data is divided into pages > > * every page has some size (although it doesn't oblige that all > >pages are of the same size) > > * some component, or some user logic, may need to have access to the data > > > >The 3 methods IPageable interface below is simple, nice, > >but I think it lacks 2 important methods > > public int getPageSize(); > > public Iterator iterator(); > > > >Exposing these methods is trivial on whatever the component is based: > >a collection, Map or an array - but makes this interface really > >powerful. > > > >Dariusz Wojtas ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
