The ASPx Blog - Mehul Harry's DevExpress Blog

This is a great step forward for the AspxGridView and will work really well as a basic filter builder.  There are still some major aspects that could be improved to both the winforms version and this version of the Filter Control that could make it un-beatable.  See suggestion S20272 for suggestions.  

Anyway, great work.

Accepted yes :)  But I'm not very hopeful that it will get implemented anytime soon...  it's been accepted for over a year now.  Oh well :(  maybe one day....

This looks great, thanks!

Hi Steven,

Regarding your issue:  www.devexpress.com/issue=S20272.

We will definitely implement this feature one day. Roman (our XAF architect) constantly tells me that a database scheme is not flat, it is a tree. However, we deal with root nodes only.

Several weeks ago, when Roman came to our room to talk about integrating ASP.NET filter control into XAF, he started yelling at us. He was disappointed because to introduce the filter control, his guys have  to implement a couple of interfaces (IWebFilter…). The problem is simple; the filter control needs to get properties and their types (or editor types) to build criteria. There is nothing wrong from our point of view, the guys who wrote ASP.NET filter control. However, from XAF guys’ point of view, they have to introduce some more damn interfaces. Is it a big deal? Nope, but they already did a similar thing for WinForms filter control, Winforms and ASP.NET field customization window. There are several other places where they have to work with different API that does the same. It will make mad any agile development and it is hard to disagree with Roman.

A good solution is to introduce these interfaces into our core dll and use them through our entire control library. And of course, this API should support the tree structure.

I hope we will do it rather sooner than later. Although our management understands that changing our code will not introduce more features and, as a result, will not make our customers feel better. They respect these types of changes.  Because they understand that it will keep our code clean and as a result we will introduce new features faster and our customers will report less issues, the product line will be more solid.

PS: I have to say that we are fighting against refactoring that doesn’t give us any reasonable benefits. However, this situation is not a case.

Looks good. When can we get it? When is 2008.3 due?

Looks really nice. We are using the Winforms control allready and waiting for this control. Can you give an date on when it's available?

Andrew,

I appreciate the insight.  It is nice to know that it is at least being talked about internally.  I can understand the debate and agree that the code should be centrally located.  Anyway, thanks for the post!

The next major release of DXperience and the ASPxGridView & Editors Library includes new controls

[Post Updated: Sunday, October 26th, 2008] The next major release of DXperience and the ASPxGridView

Awesome control, thank you, is there any suggestions which could allow as a part of the filter control to specify how particular column should be sorted, sometimes this is not very optimal to sort asc and then descending, would be really cool to have possibility to specify sort type or filtering or both together, what do you think?

I think that suggestion S20272 is a not a good idea to implement for ASP.NET.

Hi,

The control is cool. I would like to know, whether the below supported?

1. Is it possible to use it independently (outside of GridView)?

2. I would like to allow user to specify filter expression and save it somewhere. Then user can re-use it.

3. Able to filter any GridView supported data source.

4. Generate filter expression for C#, SQL, Javascript

Thank you