- Pharo-dev - lists.pharo.org

I get error when I push down method

by stepharo

I get various error when doing pushdown. Pushing methods from MethodWidget to its subclass is a good test case. on ======================================================== showInstance ^ self model showInstance and methodsIconsCache ^ MethodsIconsCache okToChange ^ self model okToChange. I get parseTree = nil computePoolsToMove | poolVariables searcher | poolVariables := self poolVariableNamesFor: fromClass. pools := Set new. searcher := RBParseTreeSearcher new. searcher matches: '`var' do: [:aNode :answer | | varName pool | varName := aNode name. (aNode whoDefines: varName) isNil ifTrue: [(poolVariables includes: varName) ifTrue: [pool := self whichPoolDefines: varName. pool notNil ifTrue: [pools add: pool]]]]. searcher executeTree: parseTree ======================================================== I also got a problem that I cannot reproduce but having to do that may be the change was not recorded and the Undo was wrapping soemthing wrong. This would be great if one of you try to remove the AbstractMethodWidget using refactorings to spot the problem Stef

Nov. 11, 2015

Re: [Pharo-dev] It looks like I broke the category menu...

by stepharo

Yes I'm doing it right now. Le 11/11/15 15:31, Ferlicot D. Cyril a Ã©crit : > Le 11/11/2015 15:16, stepharo a Ã©crit : >> Hi >> >> It looks like I broke the category menu... when I folded the >> CategoryWidget into its superclass. >> I will try to find why? >> >> Stef >> > Do you plan to do the same with Class, Methods, Package widgets? >

Nov. 11, 2015

Re: [Pharo-dev] It looks like I broke the category menu...

by Ferlicot D. Cyril

Le 11/11/2015 15:16, stepharo a Ã©crit : > Hi > > It looks like I broke the category menu... when I folded the > CategoryWidget into its superclass. > I will try to find why? > > Stef > Do you plan to do the same with Class, Methods, Package widgets? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Nov. 11, 2015

Re: [Pharo-dev] It looks like I broke the category menu...

by stepharo

Yes I already published a fix Thanks for the feedback Le 11/11/15 15:19, Nicolai Hess a Ã©crit : > > > 2015-11-11 15:16 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi > > It looks like I broke the category menu... when I folded the > CategoryWidget into its superclass. > I will try to find why? > > > class side method with menu/shortcut pragma! > > > Stef > >

Nov. 11, 2015

Re: [Pharo-dev] It looks like I broke the category menu...

by Nicolai Hess

2015-11-11 15:16 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi > > It looks like I broke the category menu... when I folded the > CategoryWidget into its superclass. > I will try to find why? > class side method with menu/shortcut pragma! > > Stef > >

Nov. 11, 2015

It looks like I broke the category menu...

by stepharo

Hi It looks like I broke the category menu... when I folded the CategoryWidget into its superclass. I will try to find why? Stef

Nov. 11, 2015

Re: [Pharo-dev] [Pharo-users] Changing playground and monticello shortcuts

by Tudor Girba

Hi, It was chosen a while ago that the Global shortcuts are checked first, before the local ones. The local ones propagate from bottom to top. The idea here was to guarantee global behavior, such as Shift+Enter for popping out things like Spotter. I was not happy about that, but that was the choice. Now, I think that the global keymap mechanism should be used sparingly, and I think that using it for Cmd+o is a bit too much. Cheers, Doru > On Nov 11, 2015, at 12:22 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > Ehm, or maybe fix event dispatch so it works properly? > It should always end up testing for event handling By the leaf morph at the given event position and work its way up if unhandled, not check top-down like the change to dispatchEvent:with: has ended up doing... > > Cheers, > Henry > >> On 11 Nov 2015, at 11:46 , Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> I actually think we should disable those shortcuts. >> >> The reason is that they âpollute" the global shortcut space: for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal. >> >> The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter >> >> Cheers, >> Doru >> >> >>> On Nov 11, 2015, at 10:49 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> >>> >>> 2015-11-11 10:45 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >>> Hi, >>> >>> currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. >>> However since it now opens Playground the shortcut is no longer appropriate. >>> >>> So can we change it to <cmd>+o+p? >>> (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.) >>> >>> cmd+o+m would be >>> ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows. >>> >>> >>> You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is). >>> >>> Peter >>> >> >> -- >> www.tudorgirba.com >> >> "We cannot reach the flow of things unless we let go." >> >> >> >> > -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Nov. 11, 2015

Re: [Pharo-dev] Some menu entries should not be in spotter

by Andrei Chis

We added all entries from the world menu to spotter. But indeed without a better ordering of results this can cause some issues. We can revert to a previous solution where we just show the items from the main and the tools menu. On Wed, Nov 11, 2015 at 1:03 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > I managed to start 'Software update' by typing Date in spotter. > There are probably a few more menu entries that should > not be so easily accessible? > > Stephan > > >

Nov. 11, 2015

Re: [Pharo-dev] Does anybody know if Sport is available in Pharo?

by stepharo

I would like to see what is needed and if we can improve Pharo libraries :) Le 10/11/15 21:39, Sven Van Caekenberghe a Ã©crit : > << Sport is a Smalltalk portability layer. Sport presents a consistent interface and implemented in a number of Smalltalk dialects. Smalltalk code written to the Sport interfaces can be run in any Smalltalk dialect without alteration. >> > > Anyway, that was the idea some years ago. It is somewhat comparable to Grease (used by Seaside). > >> On 10 Nov 2015, at 21:27, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> >> anyone care to explain what Sport is , the project description does not help. >> >> On Tue, Nov 10, 2015 at 8:33 PM stepharo <stepharo(a)free.fr> wrote: >> thanks! >> >> >> Le 10/11/15 10:03, Stephan Eggermont a Ã©crit : >>> On 10-11-15 08:00, stepharo wrote: >>>> Thanks >>> I assume you want it working in Pharo5? >>> There was no #'pharo5.x' >>> >>> Name: ConfigurationOfSPort2-StephanEggermont.16 >>> Author: StephanEggermont >>> Time: 10 November 2015, 10:01:56.039515 am >>> UUID: 0c712020-3d22-405b-9842-3106b6b9721f >>> Ancestors: ConfigurationOfSPort2-StephanEggermont.15 >>> >>> In-place pharo5 version added >>> >>> >>> >>> >> > >

Nov. 11, 2015

I love to see all the enhancements

by stepharo

Hi Pharoers I really love to see all the enhancements being pushed to Pharo. This is a great feeling. Thanks for all your contributions. We are building a really nice system. Stef

Nov. 11, 2015