Re: [Pharo-users] About GTSpotter matching

Hi, By the way, is it possible to have exact match now? At least, I expect to have expect match on the top of the result list. A simple use case, open Spotter search number dive into implementors category The exact matches are lost in the middle of hundreds of other selectors. This way, it is

Re: [Pharo-users] About GTSpotter matching

Hi Christophe, Not yet, but this is definitely way to improve Spotter. Thanks for the comment, Juraj -- Juraj Kubelka 8. 12. 2015 v 5:10, Christophe Demarey : > Hi, > > By the way, is it possible to have exact match now? > At least, I expect to have expect match

Re: [Pharo-users] About GTSpotter matching

On Tue, Dec 8, 2015 at 5:10 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi, > > By the way, is it possible to have exact match now? > At least, I expect to have expect match on the top of the result list. > +1 > A simple use case, > >- open Spotter >- search number >

Re: [Pharo-users] About GTSpotter matching

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 #

Re: [Pharo-users] About GTSpotter matching

On 12/07, Juraj Kubelka wrote: > Hi, > > # is a category filter. Try #class, #instance, etc. Oh... right. I've been using this for long time, my brain just didn't connect the dots. In either case, once you dive in the category filter is no longer applicable. So normally I would do "#i

Re: [Pharo-users] About GTSpotter matching

Hi, # 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

Re: [Pharo-users] About GTSpotter matching

> 7. 12. 2015 v 11:59, Peter Uhnak : > > On 12/07, Juraj Kubelka wrote: >> Hi, >> >> # is a category filter. Try #class, #instance, etc. > > Oh... right. I've been using this for long time, my brain just didn't > connect the dots. > > In either case, once you dive in the

Re: [Pharo-users] About GTSpotter matching

Currently wildcard are not supported. I think this is in the roadmap of the GT team. But not supported for now. However, there is strictly no need for it. Since you have the dive-in category: https://dl.dropboxusercontent.com/u/31543901/MyPapers/Kube15a-VISSOFTNIER-SpotterAnalyzer.pdf Cheers,

Re: [Pharo-users] About GTSpotter matching

Yes, I asked about this also some months ago. +1 for the desired feature! On Sat, Dec 5, 2015 at 8:40 PM, Peter Uhnak wrote: > Hi, > > are there some wildcards in GTSpotter matching? > > Currently it searches anywhere in the (method) name, which makes it hard > for shorter

[Pharo-users] About GTSpotter matching

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.