On Monday, 17 July 2006 08:21 pm, Aaron Hiniker escreveu:
> Yes, a List implement that filters on the fly would avoid the copy, but
I am not sure if you are talking the Collections api list, but if you
are
then the Glazedlists stuff provides an implementation of the Collections api
list
refreshingview is not pageable so you dont need to know the size upfront
-Igor
On 7/18/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
But then you need to pre filter the list. Because what would size() return??But going with something out of the repeater package would be better.But then still you
But then you need to pre filter the list. Because what would size() return??But going with something out of the repeater package would be better.But then still you need to filter up front because all those Repeaters do want to know the total size?
And filtering on demand doesn't work then.johanOn 7
another key reason for list is that the index of the list is used as a primary key to identify the right item on callbacks.-IgorOn 7/17/06, Aaron Hiniker
<[EMAIL PROTECTED]> wrote:
Yes, a List implement that filters on the fly would avoid the copy, but probably incur greater performance
there is RefreshingView that works off an iterator which is incidentally very wasy to filter in real time. it lives in wicket-extensions. there has been talk of moving that and dataview into core, but nothing concrete.
-IgorOn 7/17/06, Aaron Hiniker <[EMAIL PROTECTED]> wrote:
Yes, a List
Yes, a List implement that filters on the fly would avoid the copy, but probably incur greater performance hits than a single List copy (due to the "Linked List" nature of the filtering). The current ListView implementation only works on lists.. rightfully so because you can extract the active
im sorry but why will there be a listcopy?that is certainly a way to go but its not the only way. from the model return a List interfcace that filters on the fly.-IgorOn 7/17/06,
Aaron Hiniker <[EMAIL PROTECTED]> wrote:
Yeah, there's no problem implementing this in the model, other than
Yeah, there's no problem implementing this in the model, other than the fact that there will be a list copy.
Aaron
On Mon, 2006-07-17 at 17:02 -0700, Igor Vaynberg wrote:
the filtering should be performed in the model - it is the perfect place for it.
-Igor
On 7
the filtering should be performed in the model - it is the perfect place for it.-IgorOn 7/17/06, Juergen Donnerstag <
[EMAIL PROTECTED]> wrote:Just out of my head. Paging which is based on windows size and list
size would need to take these into consideration. Not sure this changeis trivial.Juergen
Just out of my head. Paging which is based on windows size and list
size would need to take these into consideration. Not sure this change
is trivial.
Juergen
On 7/18/06, Aaron Hiniker <[EMAIL PROTECTED]> wrote:
>
> I frequently have the need to filter the elements in a ListView.. of
> course I
I frequently have the need to filter the elements in a ListView.. of
course I can filter elements before passing them to ListView by creating
a new List, but it seems a lot cleaner to have an accept() method, just
like in IFeedbackMessageFilter or whatever.
ie:
add( new ListView( "list", m
11 matches
Mail list logo