Hi,
I find sometimes just subclassing ArrayCollection works. This way your are
defining certain types of collections that do different things.
You can then add functionality to the class with methods or whatever. This
works well for me. Then I define the different filter functions based on
that
I simply assign the input values to some properties of the filter whenever
they change.
Cheers,
Ralf.
On 5/24/07, Kevin <[EMAIL PROTECTED]> wrote:
using this approach the filter functions still need to reference the
view to get optional filter parameters correct. For example, if you want to
using this approach the filter functions still need to reference the
view to get optional filter parameters correct. For example, if you
want to filter based on a user inputed text field you can just do this:
collection.filterFunction = filter.filterFunction (textFld.text);
since the filt
I'm using a FilterClass, which holds just the filterFunction and some
optional ways to configure the filtering.
Every collection, which needs filtering, gets an instance of this
FilterClass by assigning collection.filterFunction = filter.filterFunction;
Cheers,
Ralf.
On 5/24/07, Kevin <[EMAIL P
I would like to attempt to separate my filter functions from my view
so that I am not duplicating code when two views share similar filter
functions. My idea was to create a class that contains a
ListCollection and all the appropriate FilterFunctions for that
collection. The FilterFunctio
5 matches
Mail list logo