How would you prompt for the location or person? It would be nice if custom filters could do that somehow. (If they can, then it’s something I’ve been missing out on.)
Some of the custom filters I use as building blocks for others include these:
Active person [uses the Active person rule]
Bookmarked people [uses the Bookmarked people rule]
Default person (or home person) [uses the Home person rule]
It would also be nice if it were easy to see which custom filters use a given filter rule or other custom filter (without having to go into the xml file to figure it out).
One of the nice extras in the Plugin Manager Enhanced V2 is the (debug mode) Edit button that opens the plugin’s source file in a whatever editor is tied to .py extensions. This simplifies inspecting the code.
Also very nice feature is in Kari’s prototype Filter2 gramplets. They scrape all the settings in the Filter gramplet to build a custom filter.
Also, his experimental FilterParams tool makes inspection in the GUI easy. (Particularly since it isn’t like the Gramps Filter Editor that doesn’t let you switch the category silos for the filters.
0012830 Filter Rules are missing basic rules for inter object working
You missed this one. The whole idea behind filters appears to be “To obtain a list of People”.
But if you want to start with a list of people and end with a list of events or citations, then you start hitting obstacles very quickly.
I realise that having a filter rule for every occasion would result in a very long list in deed.
Yes. Eventually, we’ll need some sort of codex/grimoire/formulary/Rulebook GUI for finding, instruction & sharing of Filter Rules.
Hopefully, there will be competing systems of organization.
Like the OCLC’s Query Collection, when the database grows too complex (they have 856 bibliographical fields describing WorldCat holdings) it becomes difficult to grok organizational potential.
I’m not a developer but as stated there is no limit to the number of filters that users may want. I think a longer term strategy might be to put the effort into moving gramps to a full sql based system, then users can develop any sql query they need.
The work could be divided up into chunks. As I understand it, a lot of work has been done defining the schema already.
The idea of listing the requested filters is so we might begin a discussion of how to do the requested filters without creating a glut of addon rules.
And so that some of these MantisBT requests can be closed with workaround. Although we might determine that some are foundation rules that actually DO need to be added.
Sorry, I forgot about the Super Tool. It isn’t loaded on my system so I have never used it. Out of sight out of mind. I’m a guy that just likes to go to the menu and find the tools that I can use.
I have tried the “Supertool” and failed to design the filter of my choice. Its lack of any instructions, hints or tips deters me and, no doubt, many others, from using it.