- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] There are still lots of Delay>>wait Processes

by Igor Stasenko

On 18 June 2013 14:43, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > You may not be the only one, but you probably are the only whose job is to > address Pharo issues :) > Toucher! :) Yes, i should look again at Delays. > Ben > > On Jun 18, 2013, at 11:17 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > On 18 June 2013 11:11, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Once igor finishes the TxModel and Athens it was planned to address the > Delay problem. > > > I don't think i am the only one who capable to fix it. :) > > Something broken in restoring Delay(s) after image restart (they > hanging for too far in the future). > That's my impression. > From other side, i do not see why Cookie should use [ Delay forEons wait] > fork. > Instead, i would just replace implementation with code which checks > the time before giving answer > of cookie value. > So, if you won't use cookie value in heavy numerical-crunchy > calculations, this is completely fine. > > Stef > > > > > > -- > Best regards, > Igor Stasenko. > > -- Best regards, Igor Stasenko.

June 18, 2013

on:do: for shortcuts?

by StÃ©phane Ducasse

Hi guillermo I thought that we decided to change and not use on: do: for shortCuts (I'm happy that we change because for me it took me a while to understand that the key was not an exception. Could we deprecate on:do: on KMDispatcher? What is the replacement? onKey: do: initializeShortcuts "initialize the inspector' shortcuts with the dictionary defined in self shortCuts" self shortCuts keysAndValuesDo: [ :key :value | list on: key do: value ] => initializeShortcuts "initialize the inspector' shortcuts with the dictionary defined in self shortCuts" self shortCuts keysAndValuesDo: [ :key :value | list onHold: key do: value ] Stef

June 18, 2013

Re: [Pharo-dev] how to define menu in spec

by Goubier Thierry

Le 18/06/2013 15:34, StÃ©phane Ducasse a Ã©crit : > is > > buildShortcut: > * > * > *standard?* No. Lack of infrastructure for that :) Spec has some of the relevant bits and could automatize this a bit. KMDispatcher still doesn't work totally as I would like. > *is it invoked automatically?* Yes. GUI model, when selected object changes, call an updateKeymap method which calls a https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… on the selected object in the GUI. Thierry > * > *Stef* > * > * > On Jun 18, 2013, at 1:48 PM, Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> wrote: > >> Hi StÃ©phane, >> >> look into the AltBrowser code. You'll find commands that are both >> shortcuts and menu items (subclasses of AltCommand). >> >> https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… >> >> https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… >> >> And it's more or less lifted from the OmniBrowser code, by the way. >> >> (Kind of convenient to link to st code from github) >> >> Thierry >> >> Le 18/06/2013 13:34, StÃ©phane Ducasse a Ã©crit : >>> Hi ben >>> >>> I want to define some menu for my logging Tool UI. And I was >>> wondering how >>> >>> - define menu >>> - avoid duplication with shortcut >>> >>> I looked at the EyeInspector but it is not clear to me. Do you have a >>> better example I could read? >>> >>> Stef >>> >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 18, 2013

Re: [Pharo-dev] Object>>#if:then:else:

by kilon

ifEvaluatesToTrueUsing sounds like an overkill to me and unnecessary , its common convention in all popular languages than an if always needs to evaluate to true to execute and if it evaluates to false then "else" handles it. -- View this message in context: http://forum.world.st/Pharo-dev-Object-if-then-else-tp4693871p4693945.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 18, 2013

Re: [Pharo-dev] Also "create method" in traits

by Sebastian Tleye

Done :) You can download the fix and not suffer anymore :P 2013/6/18 Camillo Bruni <camillobruni(a)gmail.com> > yes please :) > > https://pharo.fogbugz.com/default.asp?10951 > > On 2013-06-18, at 14:59, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 18 juin 2013, at 14:56, Martin Dias wrote: > > > >> Hi > >> > >> I informally reported this "feature requirement" today to Sebastian, > >> but I wanted to post it to all. > >> > >> When the debugger is shown after a MNU, the developer can press the > >> button "Create method". A list of the superclasses is shown to the > >> developer, so he/she can choose in which class crate the method. In > >> addition to superclasses, it would be nice to show the traits that the > >> classes use, since developer might want to create the method there. > >> > >> Cheers, > >> MartÃn > >> > > > > +1 > > >

June 18, 2013

Re: [Pharo-dev] how to define menu in spec

by StÃ©phane Ducasse

ok I will try to find my way but yes it would be good to offer an infrastructure to avoid that everybody reinvent the wheel Stef On Jun 18, 2013, at 2:49 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > For menus, there is nothing spec related here (yet). > If you use pragmas, for defining your menus/shortcuts, there is (or was) a specific registration class supporting made for defining both in one. > It was never adopted, so I do not know where to find it again, sorry > > > Ben > > On Jun 18, 2013, at 1:48 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Hi StÃ©phane, >> >> look into the AltBrowser code. You'll find commands that are both shortcuts and menu items (subclasses of AltCommand). >> >> https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… >> >> https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… >> >> And it's more or less lifted from the OmniBrowser code, by the way. >> >> (Kind of convenient to link to st code from github) >> >> Thierry >> >> Le 18/06/2013 13:34, StÃ©phane Ducasse a Ã©crit : >>> Hi ben >>> >>> I want to define some menu for my logging Tool UI. And I was wondering how >>> >>> - define menu >>> - avoid duplication with shortcut >>> >>> I looked at the EyeInspector but it is not clear to me. Do you have a >>> better example I could read? >>> >>> Stef >>> >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> >

June 18, 2013

Re: [Pharo-dev] how to define menu in spec

by StÃ©phane Ducasse

is buildShortcut: standard? is it invoked automatically? Stef On Jun 18, 2013, at 1:48 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi StÃ©phane, > > look into the AltBrowser code. You'll find commands that are both shortcuts and menu items (subclasses of AltCommand). > > https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… > > https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… > > And it's more or less lifted from the OmniBrowser code, by the way. > > (Kind of convenient to link to st code from github) > > Thierry > > Le 18/06/2013 13:34, StÃ©phane Ducasse a Ã©crit : >> Hi ben >> >> I want to define some menu for my logging Tool UI. And I was wondering how >> >> - define menu >> - avoid duplication with shortcut >> >> I looked at the EyeInspector but it is not clear to me. Do you have a >> better example I could read? >> >> Stef >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

June 18, 2013

[ANN]: Pharo x.5

by DeNigris Sean

Are you both impatient and conservative (and apparently confused) like me? I want to use the stable release of Pharo with the best new features of the alpha version. Also, do you ever think of cool enhancements to the IDE that for whatever reason have not made it into the release? Well, I've been collecting these things into ConfigurationOfPharoSpd. There are many little parts, which you can load with: Gofer it squeaksource3: 'PharoSpd'; package: 'ConfigurationOfPharoSpd'; load. (Smalltalk at: #ConfigurationOfPharoSpd) load. Here is a screenshot of its little browser showing the issues which have been addressed (gray means the issue is not applicable to the current image version, green means the fix has been applied): There are also a bunch of little IDE enhancements. This one is one of my favorites. Instead of sprinkling method comments like "self open" in every class-side unary method, there are Nautilus menu items to send them (and optionally inspect the result): Or you can add a boilerplate ComposableModel to a package: And some extension methods I find myself using often, like: * String>>surroundedByDoubleQuotes * DateAndTime>>printUS, which returns a string like '6/18/2013 @ 9:20 am' * ZnNetworkingUtils>>isPortAvailable: (doesn't take ip6 into account) Anyway, enjoy! Feedback welcome...

June 18, 2013

Re: [Pharo-dev] Also "create method" in traits

by Camillo Bruni

yes please :) https://pharo.fogbugz.com/default.asp?10951 On 2013-06-18, at 14:59, Camille Teruel <camille.teruel(a)gmail.com> wrote: > On 18 juin 2013, at 14:56, Martin Dias wrote: > >> Hi >> >> I informally reported this "feature requirement" today to Sebastian, >> but I wanted to post it to all. >> >> When the debugger is shown after a MNU, the developer can press the >> button "Create method". A list of the superclasses is shown to the >> developer, so he/she can choose in which class crate the method. In >> addition to superclasses, it would be nice to show the traits that the >> classes use, since developer might want to create the method there. >> >> Cheers, >> MartÃn >> > > +1

June 18, 2013

Re: [Pharo-dev] Also "create method" in traits

by Camille Teruel

On 18 juin 2013, at 14:56, Martin Dias wrote: > Hi > > I informally reported this "feature requirement" today to Sebastian, > but I wanted to post it to all. > > When the debugger is shown after a MNU, the developer can press the > button "Create method". A list of the superclasses is shown to the > developer, so he/she can choose in which class crate the method. In > addition to superclasses, it would be nice to show the traits that the > classes use, since developer might want to create the method there. > > Cheers, > MartÃn > +1

June 18, 2013