[Feature Request] Filtering support about backgrid

[wyuenho]

Hi! Thx and congrat for being the first person to open a ticket besides myself!

Yes I suppose I will need a filter widget at some point. Will be an extension for sure and it'll be able to listen directly to the collection events and tell the filtered rows to disappear. You will probably be able to attach as many of them on each grid as you want. Right?

But I'm going to shelf this for the next version. I've been working on this first version long enough I really need to get a release out. BTW, if you have a clone, I plan to do some major refactoring for Backbone 0.9.9 and then some major squashing on master... don't say I didn't tell you :)

[stnor]

Yeah, sounds good.
Keep up the good work!

/Stefan

[jayelkaake]

+1 to this. Looks great, but a filtering system would make it awesome.

[wyuenho]

I've started working on this. Any concreate ideas what you guys want with this? Will a naive prefix search on predefined fields good enough? Search on the server and rerender afterwards? Any awesome algorithm dudes out there that can help me implement a Levenshtein distance search box purely on the client-side?

[ihortymoshenko]

First of all, I think need to do search on the server and rerender afterwards. For this issue also need some specifications about data that will be send to the server. For instance, http://www.trirand.com/jqgridwiki/doku.php?id=wiki:advanced_searching#options. I also think about writing the bundle for Symfony2 to realize the search on the server. For instance, using by Doctrine2 and QueryBuilder and maybe some logic to easy configurate grids from the server-side.

[jayelkaake]

I agree with @IgorTimoshenko with using the jqgrid filters spec for sending server-side filter requests. Just make sure the UI is as simple as possible. Something like a collapsible filter box for each field would be good enough, and maybe the ability to add a fulltext search on the data (that would hit the server too). The jqgrid filters are too complicated.

In terms of client-side architecture you would want to create a Filter class and that decorates the grid with the filters (ie Decorator design pattern).

Thanks!!

[wyuenho]

Ok. I think for the first version of a filter I'll do the following:

1. Separate search box with no connection to the grid, no excel style filter. The only connection the filter has with the grid is they are sharing the same collection.
2. There will be a well-defined way to turn the stuff inside the search box to queries sent to the server.
3. No client-side filtering.

Things that you guys can help me decide:

1. Which query engine to use? There are a number of query engines/plugins for Backbone out there.
2. Yes or no for autocomplete? Probably leverage bootstrap-typeahead?

[ihortymoshenko]

I am not sure that autocomplete needed for the first version.

[jayelkaake]

I agree with @IgorTimoshenko

[Integral]

Hi! Any update here?

[phillycoder]

+1, I like the idea of keeping the Search box separate from grid. Will this search queryParams be used along with BackGrid queryParams?

[wyuenho]

Hi guys, ServerSideFilter and ClientSideFilter are now in the branch. ServerSideFilter performs your boring send-a-request-to-the-server type of searching. ClientSideFilter integrates with lunrjs to do client-side full-text searching. It's more suitable for a grid with a small number of records.

Please try them out and let me know if there are any problems.