December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Is GTSpotter theme-aware ?

by Tudor Girba

It is. Read my mail :). Doru On Wed, Dec 10, 2014 at 4:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > it doesnât need to be made for every theme around, just âtheme awareâ, > which means do not use hardcoded values but the ones defined in the themes. > > Esteban > > On 10 Dec 2014, at 16:47, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi, > > For now testing Spotter for every existing theme is not on the first place > in our TODO list. But Spotter uses themer mechanism, so anyone can > customize it :) > > Cheers, > Alex > On Dec 10, 2014 4:42 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: > >> Is GTSpotter theme-aware ? >> >> It does not seem to use the Dark Theme: >> >> <Screen Shot 2014-12-10 at 16.40.23.png> >> >> Sven >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 10, 2014

Re: [Pharo-dev] Is GTSpotter theme-aware ?

by Esteban Lorenzano

it doesnât need to be made for every theme around, just âtheme awareâ, which means do not use hardcoded values but the ones defined in the themes. Esteban > On 10 Dec 2014, at 16:47, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi, > > For now testing Spotter for every existing theme is not on the first place in our TODO list. But Spotter uses themer mechanism, so anyone can customize it :) > > Cheers, > Alex > > On Dec 10, 2014 4:42 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > Is GTSpotter theme-aware ? > > It does not seem to use the Dark Theme: > > <Screen Shot 2014-12-10 at 16.40.23.png> > > Sven

Dec. 10, 2014

Re: [Pharo-dev] Is GTSpotter theme-aware ?

by Tudor Girba

It was made to be themeable, but there is only one theme implemented. In fact, this is the first tool that is based completely on the pattern I described previously: http://www.humane-assessment.com/blog/a-pharo-refactoring-story-adding-them… The theming is done in GTSpotterWidgetThemer. To contextualize it for the DarkTheme one would need to: - Subclass GTSpotterWidgetThemer - Override UITheme>>spotterWidgetThemer ^ GTSpotterWidgetThemer new Like this, UITheme becomes a composite of concrete independent themer objects and can be more manageable. Doru On Wed, Dec 10, 2014 at 4:41 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Is GTSpotter theme-aware ? > > It does not seem to use the Dark Theme: > > > Sven > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 10, 2014

Re: [Pharo-dev] Is GTSpotter theme-aware ?

by Aliaksei Syrel

Hi, For now testing Spotter for every existing theme is not on the first place in our TODO list. But Spotter uses themer mechanism, so anyone can customize it :) Cheers, Alex On Dec 10, 2014 4:42 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: > Is GTSpotter theme-aware ? > > It does not seem to use the Dark Theme: > > > Sven >

Dec. 10, 2014

Re: [Pharo-dev] Find message name /implementors in Spotter

by Tudor Girba

Yes. I was too lazy. It's committed now. Thanks, Doru On Wed, Dec 10, 2014 at 4:39 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 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 > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 10, 2014

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