Symphony 2.3 – filtering
The idea of a filtering interface comes with extensions like Publish Filtering (PF) and Events, Datasource and Utilities Indexes (EDUI). The purpose of this page is to collect thoughts and opinions concerning a possible, future standardized filtering interface & logic.
Filters are distinct, separate entities responsible for filtering over a set of data by one (or more) axes.
Note: It's not clear if filters should accept multiple axes, or each axis has to be considered a filter itself. Since each solution has no technical benefits over the other, we decided to postpone the discussion until more important topics are covered.
Filters might come with their own filtering logic (e.g. contains, is, is empty and so on). As far as Symphony fields are concerned, this logic is borrowed from Datasources' one, which in turn is informed by the new filtering logic. For instance, fields like "Text input" and "Textarea" already support contains (i.e. "regexp:" in the Datasource editor) and is (i.e. simply typing the string in the Datasource editor). If new modes are needed, these should be ideally available on both the Filters editor and the Datasource editor.
Experience suggests that the Filters editor might work in conjunction with Symphony 2.3 – Drawer. Some screenshots from both PF and EDUI show how filters are actually styled at the moment:
As you can see, we expect to provide users with basic options like filters addition and deletion. More might come in the future.
Do we handle markup generation in PHP, or is it better to make a heavy use of JavaScript? Don't miss next episode!