It is not duplicated.
The logic is different:
- GTSpotterCandidatesProcessor>>is:matching: works as a filter on a given
collection.
- GTSpotter>>spotterImplementorsFor: is an iterator that tries to match as
it runs.
Anyway, this part of Spotter will be reworked soon.
Doru
On Fri, Jan 9, 2015 at
Both GTSpotter>>spotterImplementorsFor: and
GTSpotterCandidatesProcessor>>is:matching: do substring matching, so
I'm wondering if the matching logic is duplicated/distributed in
several places.
On 9 January 2015 at 15:55, Tudor Girba wrote:
> I am not sure I understand the question. A duplication
I am not sure I understand the question. A duplication of what?
Doru
On Fri, Jan 9, 2015 at 3:48 PM, Damien Pollet wrote:
> I've seen #includesSubstring: in
> GTSpotterCandidatesProcessor>>is:matching: as well… is it duplication
> or a legitimately different use? (just trying to understand the
I've seen #includesSubstring: in
GTSpotterCandidatesProcessor>>is:matching: as well… is it duplication
or a legitimately different use? (just trying to understand the
architecture)
On 9 January 2015 at 14:46, Tudor Girba wrote:
> The includesSubstring: is the simplest thing we could do to get som
The includesSubstring: is the simplest thing we could do to get some value
out of the interface. More is definitely required in this direction.
To build a custom search logic, you should use "processor filter: [...]".
For an example, look at GTSpotter>>spotterImplementorsFor: aStep.
This is stil
Back to this thread!
I'm not completely fond of the way GTSpotter matches candidates using
just #includesSubstring:
Are there provisions already to rank candidates instead of binary
matching/rejecting them? I'd like to try one of the fuzzy matching
algorithms that other quick-selection tools have.
Hi,
Sorry I don't want to "kidnap" the thread, but just inspecting
"KMRepository default" and selecting an empty row brings and error. In
an other thread today I talked about this error still being present, so
is not just about my project, but a way to select empty places on GT
objects (trees
Doru’s blog has some neat things. One led me to the following:
Inspect:
KMRepository default.
With GTools installed, you can see all the shortcuts nicely formatted. I
finally found a ‘scope selection’ (Cmd+Sh+P) which makes me a very happy user
(it’s my primary selection method in IntelliJ/AppCo
Thanks Esteban,
that is the perfect attitude to build a nice tool and later embrace if a better
one arrives. So let's celebrate Spotlight for being good companion and wish it
farewell.
Norbert
> Am 12.12.2014 um 13:07 schrieb Esteban Lorenzano :
>
> shift+enter is better.
> I will remove Sp
could not agree more, this is a great tool with a huge potential and really
upgrades the Pharo experience.
I have not see anything similar in other IDEs I have been using in the
past.
On Fri, Dec 12, 2014 at 2:07 PM, Esteban Lorenzano
wrote:
>
> shift+enter is better.
> I will remove Spotlight s
shift+enter is better.
I will remove Spotlight soon… honestly spotter is so much better than even when
not everything is working perfect, is already a huge improvement
Esteban
> On 12 Dec 2014, at 12:11, Tudor Girba wrote:
>
> I would like to get Shift+Enter (because Cmd+Enter will be useful
no objections here :)
On Fri, Dec 12, 2014 at 1:11 PM, Tudor Girba wrote:
>
> I would like to get Shift+Enter (because Cmd+Enter will be useful in other
> contexts), but we wanted to have something that can live next to the
> Spotlight for a while.
>
> But, now that we are over the first set of p
I would like to get Shift+Enter (because Cmd+Enter will be useful in other
contexts), but we wanted to have something that can live next to the
Spotlight for a while.
But, now that we are over the first set of problems, I would like to use
Shift+Enter. Any objections?
Cheers,
Doru
On Fri, Dec
I got the same problem and Cmd+ENter was already used on my machine set up.
So it was not really simple.
Le 11/12/14 17:25, Damien Pollet a écrit :
Cmd+Enter: ‘Package'
Doru, your blog post does not mention this piece of information: how
to invoke GTSpotter
It does not seem to be mentioned in y
Hi,
I made a mistake and the post got reverted to a previous version that did
not mention Cmd+Enter. The shortcut is present again in the post.
But, the discoverability problem is still present and we need to fix it. It
won't be a workspace, but likely a visual element or at least a menu entry.
A big +1 on Damien’s comment. Discoverability of useful things is too low. For
example, I did not know about Shift-enter for searching until somebody showed
it to me inadvertently when he was demoing something else :-/
That being said, I don’t have a good solution to the problem either :-( Mayb
> Cmd+Enter: ‘Package'
Doru, your blog post does not mention this piece of information: how
to invoke GTSpotter
It does not seem to be mentioned in your announcement email either; I
found it here after going through threads talking about GTSpotter.
Nobody else asked for it, so I'm guessing it was
anything is doable. The barrier always is knowledge.
There is already a project to bring documentation and a specific kind of
documentation called Pillar which is what we use for updated PBE and Pharo
for the Enterprise books inside the GTInspector. Its a WIP.
On the side of GTSpotter you have a
Hello,
I am having a blast with GTSpotter - it’s the missing link for me, just one
step to ask a question from Pharo. Keeps the flow going!
Being new to the innards of Pharo, I’ve decided to try something.
I would love documentation in GTSpotter. For example, I am interested in how
packages are
19 matches
Mail list logo
