- Pharo-dev - lists.pharo.org

Is GTSpotter theme-aware ?

by Sven Van Caekenberghe

Is GTSpotter theme-aware ? It does not seem to use the Dark Theme: Sven

Dec. 10, 2014

Find message name /implementors in Spotter

by Nicolai Hess

Currently, spotter finds only messages with the exact name. for example: addStep finds no implementors althought the method addStep: exists. suggestion for spotterImplementorsFor: spotterImplementorsFor: aStep <spotterOrder: 30> | processor | processor := aStep listProcessor. processor title: 'Implementors'; filter: [ :originalQuery :stream | | aCollection query | aCollection := OrderedCollection new. query := originalQuery trimBoth. SystemNavigation default allBehaviorsDo: [:class | class selectorsDo:[:selector | (selector includesSubstring: query) ifTrue: [ | method | method := class>>selector. aCollection add: method. aCollection size > 5 ifFalse: [ stream addObject: method inProcessor: processor ]]]]. aCollection ]. ^ processor

Dec. 10, 2014

Re: [Pharo-dev] Spotter feedback

by kilon alios

This tool is too awesome cant thank you enough guys. I was looking into implementing something like this , I see a lot of potential inside this tool to finally unify the whole GUI of pharo and all tools. Now I can base my work on this :) On Wed, Dec 10, 2014 at 5:27 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi Stef, > > It's not a bug it's a "feature" :) > Actually history is not fully implemented - nice presentation of the item > is not done yet, but we are working. > > Cheers, > Alex > On Dec 10, 2014 4:19 PM, "stepharo" <stepharo(a)free.fr> wrote: > >> cooooooooooooooooooooool >> >> Now when I select a menu (by scrolling down) I get that in my history. >> >> Stef >> >> >> >> >

Dec. 10, 2014

Re: [Pharo-dev] About launching tools with Spotter

by Aliaksei Syrel

Hi, Such search behaviour needs more complicated inner logic and could make building of custom search processors expensive. But you are right, spotter needs some more sophisticated filtering logic. Cheers, Alex On Dec 10, 2014 4:22 PM, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: > you have to type "monticello bââ¦ which is of course not good :) > > application matches should be shown immediately, for monticello the âmâ > should be enough if we want people to use themâ¦. otherwise, it will be a > lot easier to fall back to the world menu. > > Esteban > > > On 10 Dec 2014, at 16:17, stepharo <stepharo(a)free.fr> wrote: > > > > Doru > > > > how can I launch a MC browser with Spotter. > > How can I access menu items from the search (because some I do not see > them). > > > > I mean when I type Monticello..... it does not work well > > May be having some shortcut > > MC > > or the key binding of the menu > > > > > > Stef > > > > >

Dec. 10, 2014

Re: [Pharo-dev] Spotter feedback

by Aliaksei Syrel

Hi Stef, It's not a bug it's a "feature" :) Actually history is not fully implemented - nice presentation of the item is not done yet, but we are working. Cheers, Alex On Dec 10, 2014 4:19 PM, "stepharo" <stepharo(a)free.fr> wrote: > cooooooooooooooooooooool > > Now when I select a menu (by scrolling down) I get that in my history. > > Stef > > > >

Dec. 10, 2014

Re: [Pharo-dev] About launching tools with Spotter

by Esteban Lorenzano

you have to type "monticello bââ¦ which is of course not good :) application matches should be shown immediately, for monticello the âmâ should be enough if we want people to use themâ¦. otherwise, it will be a lot easier to fall back to the world menu. Esteban > On 10 Dec 2014, at 16:17, stepharo <stepharo(a)free.fr> wrote: > > Doru > > how can I launch a MC browser with Spotter. > How can I access menu items from the search (because some I do not see them). > > I mean when I type Monticello..... it does not work well > May be having some shortcut > MC > or the key binding of the menu > > > Stef >

Dec. 10, 2014

Spotter feedback

by stepharo

cooooooooooooooooooooool Now when I select a menu (by scrolling down) I get that in my history. Stef

Dec. 10, 2014

About launching tools with Spotter

by stepharo

Doru how can I launch a MC browser with Spotter. How can I access menu items from the search (because some I do not see them). I mean when I type Monticello..... it does not work well May be having some shortcut MC or the key binding of the menu Stef

Dec. 10, 2014

Re: [Pharo-dev] Short AltBrowser end-user test

by Esteban Lorenzano

> On 10 Dec 2014, at 10:57, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi All, > > I setup a small experiment for a group of students, when teaching them a lab about process networks programming with Pharo and Roassal. Students were some used to Smalltalk (VisualWorks), some with no knowledge of Smalltalk, level is M2. > > I changed the default Browser to AltBrowser instead of PackageTreeNautilus. I gave no explanation about how to use it. Students had a four hours lab, and are supposed to hand out a package with a few methods containing scripts. I showed them how to save a pre-existing package. > > - There was no question at all about the browser. And when asked, they felt there was no need for explanations on it. > > - They are not using it the way I expected (and the way I designed it for). They were using it like an 'eclipse' type of IDE (a single, very large window showing both the list of examples and the place they were working on). I donât know why are you so surprisedâ¦ eclipse is what they know, so obviously they will use it like it :P Esteban > > I'll probably try again in a different setup starting January. With non-smalltalkers. > > Thierry > >

Dec. 10, 2014

Re: [Pharo-dev] Short AltBrowser end-user test

by stepharo

:) > Hi All, > > I setup a small experiment for a group of students, when teaching them > a lab about process networks programming with Pharo and Roassal. > Students were some used to Smalltalk (VisualWorks), some with no > knowledge of Smalltalk, level is M2. > > I changed the default Browser to AltBrowser instead of > PackageTreeNautilus. I gave no explanation about how to use it. > Students had a four hours lab, and are supposed to hand out a package > with a few methods containing scripts. I showed them how to save a > pre-existing package. > > - There was no question at all about the browser. And when asked, they > felt there was no need for explanations on it. > > - They are not using it the way I expected (and the way I designed it > for). They were using it like an 'eclipse' type of IDE (a single, very > large window showing both the list of examples and the place they were > working on). > > I'll probably try again in a different setup starting January. With > non-smalltalkers. > > Thierry > >

Dec. 10, 2014