Add filters to layers

I already had plans for adding filters to entity types, but there just was no issue yet. I can assure you this issue will get fixed before the final.

This is just a first stab at adding filters. They can be defined for every entity type in hook_index_entity_type_info(). Currently only boolean filters and (select) lists are supported, meaning you can either enable or disable a filter or choose values from a select list. Some notes:

- I will have to create a separate page for each filter, because they depend on a layer's entity type, which may change while a user is configuring an index. We cannot simply display the filters from the first page load. Of course AJAX support will be added later.
- The 'value' column in {index_filter} currently is varchar. This means there might be problems when matching it against an integer column when filtering.

Follow-up, including a new icon.

Follow-up.

The UI sucks and needs to be redesigned.

The filter buttons are on the right. We need a place to put the filters. I can't find anything suitable within the table. I've been thinking about some kind of overlay or to theme the layer selectors in a totally different way without using a table.

Here's the filter icon in its disabled state.

Great job Xano, thank you very much.

Please, tell me, are u going to include this feature in the next dev build?

I don't know about the next dev build (they're automatically generated every twelve hours, provided the code has been changed), but it will definitely get in before the release.

ok, so i'll wait to the release.

It's the result of all previous patches and extra development.

can't apply this patches on build from 2010-Jan-17. can somybody upload already patched files?

thanks

Code changes have been made since the patch was created, so the patch doesn't apply anymore. You can apply the chunks that fail manually if you know how.

It's done when it's done. This means you gotta sit back and wait patiently or give me a helping hand to fix the problem. Dev means not ready for production use ;-)

This is a hobby, which means I am not obliged to do anything and are free to enjoy my spare time by doing something else than coding. And I take that very literally, even though I want to see this project finished as much as you do.

I need to revamp the interface and underlying code before filters can get in. I expect this will take a couple of weeks. My intentions are to make whatever features already exists rock solid before adding new stuff. This has worked out pretty good so far, but it does delay new stuff a bit.

Looking forward to filters!

Adding the possibility for storing filter information is being moved to #735164: Conditions API. This issue will deal with the UI and some entity-specific filters.

Subscribing.

Subscribing

sub