Hi, First, I am happy already that different people see GTSpotter as suitable for different things: some want to search for tools more, some want to search for code, and I am hoping others want to search for something else.
This is great because it shows that GTSpotter can be quite versatile. We should find a reasonable default. I think we probably should favor the tools on top just because there are very few of them. However, you should also consider looking inside the code a bit. This tool is meant to be moldable quickly to your preference. All search extensions are found in the GT-SpotterExtensions-Core. This package contains now some 40 methods totaling only 287 lines of code. For example, the definition of the top classes search is found in: GTSpotter>>spotterForClassesFor: aStep <spotterOrder: 10> aStep listProcessor allCandidates: [ Smalltalk allClasses ]; title: 'Classes'; matchSubstring; itemIcon: #systemIcon; wantsToDisplayOnEmptyQuery: false The pragma number defines the position in the list (the lower it is, the more on top it is). So, if you want to have a different order, a simple solution would be delete the GT-SpotterExtensions-Core package and replace it with your own package in your image. Cheers, Doru On Wed, Dec 10, 2014 at 10:43 PM, kilon alios <[email protected]> wrote: > Why it has to be always about black and white ? > > Just put GTSpotter to the Pharo settings and let the user choose what is > best for him. > > > -- www.tudorgirba.com "Every thing has its own flow"
