Closed jecisc closed 2 months ago
hummm or this is the work for another tool (eg. queryBrowser) The idea is to do only one thing in each browser and use propagation between tools to combine their behavior.
I started to add tagging facilities in all browsers and I am thinking how to do some simple queries in all tools. But we must be careful not to put all functionalities in all tools, otherwise they will become un-maintainable.
In this specific case, we could just use a list with a filter at the bottom. This does not cost much and would already help filtering
I was also thinking about the query browser but there is a list of all untagged entities with the possibility to tag them in the tag browser. So I was thinking than a little filter could be useful.
Or maybe we should not keep this untagged entities list in the tag browser? I don't have a big opinion on that
The list of untagged entities is what is propagated by other tools and it was in the past the only way to add an entity to a tag (or the opposite)
The idea is that:
But it can be nice to have a list filtered on names to add extra functionality
In the tag browser we have the list of untagged entities in case we want to tag them by hand.
It would be nice to be able to filter this list if we look for specific entities.