February 2013 - Pharo-users

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) is "Use old style keys" under Nautilus group Esteban On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> which most places? > > e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. > > Norbert > >> the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. >> >> Esteban >> >> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >>> Is there a way change that? >>> > > >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Norbert Hartl

Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > which most places? e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. Norbert > the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. > > Esteban > > On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >> Is there a way change that? >>

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

which most places? the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. Esteban On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. > Is there a way change that? > > Norbert

Feb. 19, 2013

Pharo 2 and old shortcuts

by Norbert Hartl

For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. Is there a way change that? Norbert

Feb. 19, 2013

Pharo By Example 2 Book - Assembled Files in PDF form.

by phil＠highoctane.be

Hi all, I struggled with the fact that the PBE2 book was in tex format and not all chapters were together in a single PDF. So, I ran the scripts in order to get a version with all the parts put together. This should be made into a Jenkins job I think so that we can have the PBE2 and other books in PDF form for easier dissemination. Here is the current assembly: https://www.dropbox.com/s/t8pesgxsovy61k5/PBE2-Assembled-20130213.pdf 412 pages of Pharo explanations. How lovely! Enjoy, Phil

Feb. 19, 2013

Re: [Pharo-users] Spec - openWithSpecLayout: vs. openWithSpec:

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > Maybe a refactor here is needed (the first one should maybe use the second > one) Okay, I opened an issue for 3.0 - Issue 7537: [Cleanup]: openWithSpecLayout: vs. openWithSpec: -- View this message in context: http://forum.world.st/Spec-openWithSpecLayout-vs-openWithSpec-tp4670560p467… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 19, 2013

Re: [Pharo-users] Spec: why is there an initialize in ClassMethodBrowser and none in MethodBrowser example?

by Benjamin

If you have questions, I will be glad to answer :) Ben On Feb 19, 2013, at 12:24 AM, phil(a)highoctane.be wrote: > Thanks. > > Still, when I do not have the initialize in the ClassMethodBrowser, > the thing doesn't work as the models aren't initialized properly. > > I'll check again. I am trying to recreate the example from scratch to > understand how all of this works. > > Regards, > Phil > > 2013/2/19 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >> The initialise method should not exists anymore. >> >> Probably the rest of an old refactoring. >> >> The "right" way is to use initialize for initialising your inst var (other >> than sub widgets), >> initializeWidgets for initialising sub widgets (instantiate them, set them, >> etc) and >> initializePresenter to specify the interactions between sub widgets. >> >> Thanks for the report :) >> >> Ben >> >> On Feb 18, 2013, at 9:53 PM, phil(a)highoctane.be wrote: >> >> MethodBrowser works without that initialize (and uses >> initializeWidgets for the instantiation) where ClassMethodBrowser >> requires one (doesnt work without as models are nil). >> >> ClassMethodBrowser>>initialize >> "Initialization code for ClassMethodBrowser" >> >> super initialize. >> >> listModel := self instantiate: ListComposableModel. >> methodModel := self instantiate: MethodBrowser. >> >> self focusOrder >> add: listModel; >> add: methodModel. >> >> listModel whenSelectedItemChanged: [:selection | >> selection >> ifNotNil: [:class | >> methodModel methods: (class methodDict values sort: [:a :b | a >> selector < b selector]). >> methodModel listModel resetSelection ]]. >> >> methodModel wrapWith: [:method | method selector ]. >> >> And >> >> ClassMethodBrowser>>initializeWidgets >> >> self instantiateModels: #( >> listModel ListComposableModel >> methodModel MethodBrowser ). >> >> self focusOrder >> add: listModel; >> add: methodModel. >> >> methodModel displayBlock: [:method | method selector ]. >> >> has the instantiateModels. >> >> There seems to be a double instantiation in here... >> >> What is the right way to proceed? The Spec Report of June 2012 and the >> Spec tex thing in the SCM aren't right, so I wonder what the right way >> to do things is. >> >> TIA >> >> Phil >> >> >

Feb. 18, 2013

Re: [Pharo-users] Spec: why is there an initialize in ClassMethodBrowser and none in MethodBrowser example?

by phil＠highoctane.be

Thanks. Still, when I do not have the initialize in the ClassMethodBrowser, the thing doesn't work as the models aren't initialized properly. I'll check again. I am trying to recreate the example from scratch to understand how all of this works. Regards, Phil 2013/2/19 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > The initialise method should not exists anymore. > > Probably the rest of an old refactoring. > > The "right" way is to use initialize for initialising your inst var (other > than sub widgets), > initializeWidgets for initialising sub widgets (instantiate them, set them, > etc) and > initializePresenter to specify the interactions between sub widgets. > > Thanks for the report :) > > Ben > > On Feb 18, 2013, at 9:53 PM, phil(a)highoctane.be wrote: > > MethodBrowser works without that initialize (and uses > initializeWidgets for the instantiation) where ClassMethodBrowser > requires one (doesnt work without as models are nil). > > ClassMethodBrowser>>initialize > "Initialization code for ClassMethodBrowser" > > super initialize. > > listModel := self instantiate: ListComposableModel. > methodModel := self instantiate: MethodBrowser. > > self focusOrder > add: listModel; > add: methodModel. > > listModel whenSelectedItemChanged: [:selection | > selection > ifNotNil: [:class | > methodModel methods: (class methodDict values sort: [:a :b | a > selector < b selector]). > methodModel listModel resetSelection ]]. > > methodModel wrapWith: [:method | method selector ]. > > And > > ClassMethodBrowser>>initializeWidgets > > self instantiateModels: #( > listModel ListComposableModel > methodModel MethodBrowser ). > > self focusOrder > add: listModel; > add: methodModel. > > methodModel displayBlock: [:method | method selector ]. > > has the instantiateModels. > > There seems to be a double instantiation in here... > > What is the right way to proceed? The Spec Report of June 2012 and the > Spec tex thing in the SCM aren't right, so I wonder what the right way > to do things is. > > TIA > > Phil > >

Feb. 18, 2013

Re: [Pharo-users] Exception signaling and processes

by Norbert Hartl

Am 18.02.2013 um 23:38 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > An established connection can always disappear for any number of reasons. Just clean up and start over. One extra note. I think that is exactly what I'm trying to achieve. In order to cleanup you have to know when or you do it all the time. As I don't get a notice when the connection is no longer valid I try at certain moments to check the validity of the server socket. At that moment I like to have the chance to see it, clean up and start over. Norbert

Feb. 18, 2013

Re: [Pharo-users] Spec - openWithSpecLayout: vs. openWithSpec:

by Benjamin

opwnWithSpec: takes a selector as argument (the method which produce the SpecLayout instance when openWithSpecLayout: take the SpecLayout instance directly Maybe a refactor here is needed (the first one should maybe use the second one) Ben On Feb 18, 2013, at 11:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > What's the difference? > > > > -- > View this message in context: http://forum.world.st/Spec-openWithSpecLayout-vs-openWithSpec-tp4670560.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Feb. 18, 2013