I'd would say for a current solution of Gili's problem
ColumnedDataProvider is a good approach. As Igor has said it is not the
cleanest solution, but it is now workable and with the current impl of
dataview I think it is also the best to understand.
On Fri, 12 Aug 2005 10:55:30 -0700, Phil Kulak <[EMAIL PROTECTED]> wrote:
I think that may be the best way to go, although you should extend
pageabledataview instead. Then you'd be in trouble if you wanted to
use a plain dataview, but at least you would just have more
functionality then you need, not less.
My first though was something like the attached file, but now I'm not
so sure. This way the user has to do the looping for the columns
themselves.
On 8/12/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
I don't think that's the right approach. The dataprovider is meant to
provide the data, and not really know how its displayed. Sure the
sortabledataprovider is kind of on the fance, but I think sorting is
more of
a data artifact rather then a presentation one. I think the breakage
into
columns should be handled by the display component. The rows container
can
pull the iterator out and just pass that to the columns container...a
orderedrepeatingview inside a dataview? Just thinking out loud...
-Igor
--
Christian Essl
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-------------------------------------------------------
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
