Itâs cool that you have this, category filters are very useful. But itâs not discoverable from the user interface so itâs very unlikely that people will know they exist (except if they are reading this message ;-) ). How about adding a âfiltersâ UI element at the top, that adds the #<relevant> expression to the search string when a filter is selected?
On Dec 7, 2015, at 09:52, Juraj Kubelka <juraj.kubelka@gmail.com> wrote:
Hi,
#<anything> is a category filter. Try #class, #instance, etc.
Wild characters are not possible to use. We are aware of this. But the case is not that simple. If I remember well, there were some performance issues. Then I have learnt that people are not aware of regular expressions or any other kind of wild-characters. Even such simple thing like #<category name> is confusing. We need to find out different way having this feature apparent.
Cheers, Juraj
On Dec 5, 2015, at 20:40, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
are there some wildcards in GTSpotter matching?
Currently it searches anywhere in the (method) name, which makes it hard for shorter names, because it will match a lot of junk.
I've also discovered (by accident), that I can use '>>#selector' to anchor the start of the selection. ('#selector' for some reason doesn't work). But I would like to also search by a simple ? (any character), * (any characters) wildcard. Is that possible?
Additionally constraining it from the end would be also nice. For example I want to look through #default methods, however 90% of the matches will be junk, so I would like to write '#default$' and it will not match '#defaultIcon', etc.
Is this possible?
Thanks, -- Peter
---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile