If you still work with windows forms and cannot move all of your projects to WPF, you probably gets annoyed by the limitation of the standard BindingList<T> included in the framework. In an old post I showed how can you create a specialized BindingList<T> to support generic Find() thanks to reflection, but this is not enough.

Another annoying limitation is that BindingList does not support IBindingListView. For those that does not knows this interface, it is the one used by the windows forms binding engine to support filtering and advanced sorting. I think that filtering is a real basic functionality needed by the binding engine, and in fact WPF support for filtering, sorting and grouping, make these operations really a breeze. But BindingList does not offers such a functionality.

My question is: is it possible to inherits from BindingList<T> adding generic filtering support as for the DataView component?. The answer is yes, here is a simple implementation.

public string Filter { get { return filterClause; } set { if (filterClause == value) return; filterClause = value; DoFilter(); } }

This is really simple, I implement the FIlter property with a simple check, if the filterClause changes, I call the DoFilter function.

private Func<T, Boolean> filterPredicate; private List<T> original = new List<T>(); private void DoFilter() { if (String.IsNullOrEmpty(filterClause)) { Items.Clear(); original.ForEach(e => Items.Add(e)); } else { original.Clear(); original.AddRange(Items); Items.Clear(); filterPredicate = DynamicLinq.ParseToFunction<T, Boolean>(filterClause); foreach (T element in original.Where(filterPredicate)) Items.Add(element); } }

The implementation is based on this standard trick, if a filter is applied I copy all the elements in a temp list, then clear the base.Items list and add again only the elements that satisfies the filter. The big work is done in DynamicLinq.ParseToFunction that takes a string and dynamically compiles a function with that criteria. Here is a simple test showing this class in action.

[Test] public void TestLogicAnd() { Func<Customer, Boolean> f = DynamicLinq.ParseToFunction<Customer, Boolean>("Name == 'Gian Maria' && Age > 5"); Assert.That(f(aCustomer), Is.True); }

Actually I use three main component, a tokenizer that takes a string and separates into token, then I pass the tokenized expression (is a List<String>) to another component that convert the infix form in postfix form (reverse Polish), finally I create an expression from the reverse Polish form, creates a LambdaExpression on it and finally call compile() to make dynamic generation happens. The result is a dynamic generator of LINQ expression from a string. It still misses a lot, you cannot express condition on nested properties and parameter support is still experimental, but the basic is there.

The code is still under development, if you are curios you can check out the repository at http://dotnetmarcheproject.googlecode.com/svn/trunk the code is still in rough form, but if you like it you can give it a shot. The class is the BindingListExt<T>

Alk.

Tags:

5 Responses to “Extend BindingList with filter functionality”

  1. Cool. I love you!
    Very cool code example.

  2. Edited: The link to the google repository linked to the https version, that needs password, I corrected the link.

    Alk.

  3. Hi,

    this is good but I had implemented this a little bit more usable.

    BR Simon

  4. @simon. good, can you share your implementation?

    Alk.

Trackbacks/Pingbacks

  1. Extending BindingList with filter functionality « Codenoise