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 <tu...@tudorgirba.com> wrote: > I am not sure I understand the question. A duplication of what? > > Doru > > On Fri, Jan 9, 2015 at 3:48 PM, Damien Pollet > <damien.pollet+ph...@gmail.com> wrote: >> >> 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 <tu...@tudorgirba.com> wrote: >> > 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 still too complicated and we need to simplify it. >> > >> > Cheers, >> > Doru >> > >> > >> > >> > On Fri, Jan 9, 2015 at 2:19 PM, Damien Pollet >> > <damien.pollet+ph...@gmail.com> wrote: >> >> >> >> 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. >> >> >> >> On 24 December 2014 at 02:36, Offray Vladimir Luna Cárdenas >> >> <off...@riseup.net> wrote: >> >> > 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, >> >> > tables, >> >> > etc) >> >> > and when there is noting there, raising no error and keeping the >> >> > state >> >> > of >> >> > the visualization (in the table resulting from inspecting >> >> > KMRepository >> >> > default closing the error brings you back to the table, with my >> >> > outliner, >> >> > the tree gets empty). >> >> > >> >> > Just trying to make the connection... surely I'm loosing something. >> >> > >> >> > Cheers, >> >> > >> >> > Offray >> >> > >> >> > El 13/12/14 a las 04:23, Edward Povazan escribió: >> >> > >> >> >> 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/AppCode). >> >> >> >> >> >> -Ed >> >> >> >> >> >> On Dec 11, 2014, at 8:59 AM, Johan Fabry <jfa...@dcc.uchile.cl> >> >> >> wrote: >> >> >> >> >> >>> >> >> >>> 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 >> >> >>> :-( >> >> >>> Maybe have the standard image have a second workspace open that >> >> >>> lists >> >> >>> useful >> >> >>> tools and their shortcuts? Plus put new tools and their shortcuts >> >> >>> prominent >> >> >>> in the release notes for each new release? (cause us old timers >> >> >>> don’t >> >> >>> look >> >> >>> at those workspaces anymore ;-) ). >> >> >>> >> >> >>>> On Dec 11, 2014, at 13:25, Damien Pollet >> >> >>>> <damien.pollet+ph...@gmail.com> >> >> >>>> wrote: >> >> >>>> >> >> >>>>> 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 well-known before >> >> >>>> and >> >> >>>> I'm the only one who failed to get addicted to whatever the >> >> >>>> shortcut >> >> >>>> was doing before? How do we make discoverable affordances for such >> >> >>>> behaviors in the image? >> >> >>>> >> >> >>>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> ---> Save our in-boxes! http://emailcharter.org <--- >> >> >>> >> >> >>> Johan Fabry - http://pleiad.cl/~jfabry >> >> >>> PLEIAD lab - Computer Science Department (DCC) - University of >> >> >>> Chile >> >> >>> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> > >> >> > >> >> >> > >> > >> > >> > -- >> > www.tudorgirba.com >> > >> > "Every thing has its own flow" >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"
