November 2013 - Pharo-dev - lists.pharo.org

[update 3.0] #30565

by StÃ©phane Ducasse

30565 ----- - Issue: 12146 Settings: Replace references to FileDirectory https://pharo.fogbugz.com/f/cases/12146/Settings-Replace-references-to-File… - Issue 12140 Filing out a tag is broken https://pharo.fogbugz.com/f/cases/12140/Filing-out-a-tag-is-broken - 12138 Finding a class is kind of broken https://pharo.fogbugz.com/f/cases/12138/Finding-a-class-is-kind-of-broken Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-StephaneDucasse.1356.di… http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Settings-StephaneDucas… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Settings-Monticello-StephaneD… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-StephaneDuc…

Nov. 12, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30565 Home: https://github.com/pharo-project/pharo-core

Nov. 12, 2013

[pharo-project/pharo-core] 170c9f: 30565

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 170c9fa725fb394589d6c621a9c57a0b3d16fa7b https://github.com/pharo-project/pharo-core/commit/170c9fa725fb394589d6c621… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-12 (Tue, 12 Nov 2013) Changed paths: M Polymorph-Widgets.package/ListDialogWindow.class/instance/actions/ok.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script221.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30565.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Settings-Monticello.package/MCSystemSettings.class/class/settings/monticelloSettingsOn_.st A System-Settings.package/SettingDeclaration.class/instance/user interface/inputWidgetForDirectory.st M Tools.package/AbstractTool.class/instance/package/fileOutPackages_.st Log Message: ----------- 30565 - Issue: 12146 Settings: Replace references to FileDirectory https://pharo.fogbugz.com/f/cases/12146/Settings-Replace-references-to-File… - Issue 12140 Filing out a tag is broken https://pharo.fogbugz.com/f/cases/12140/Filing-out-a-tag-is-broken - 12138 Finding a class is kind of broken https://pharo.fogbugz.com/f/cases/12138/Finding-a-class-is-kind-of-broken http://files.pharo.org/image/30/30565.zip

Nov. 12, 2013

Re: [Pharo-dev] petit parser repository

by Stephan Eggermont

Just try with .44

Nov. 12, 2013

Re: [Pharo-dev] petit parser repository

by Stephan Eggermont

Snapshotcello doesnât remember groups version17snapshot: spec "generated by Snapshotcello" <version: '1.7-snapshot'> spec for: #common do: [ self populateSpec: spec with: self snapshot1. spec group: 'Core' with: #( 'PetitParser' 'PetitAnalyzer' ). spec group: 'Tests' with: #( 'PetitTests' 'PetitAnalyzer' ) ] version18snapshot: spec "generated by Snapshotcello" <version: '1.8-snapshot'> spec for: #common do: [ self populateSpec: spec with: self snapshot2 ] I suspect adding the last two lines of version17snapshot: might be helpful. Stephan

Nov. 12, 2013

Re: [Pharo-dev] Spec new release :)

by Esteban Lorenzano

biut that method can be written: aMenu addGroup: (MenuGroupModel new addItem: (MenuItemModel new name: 'Browse Full'; action: [ self browseSelectedObject ]; shortcut: $b command mac | $b alt win | $b alt unix); addItem: (MenuItem new name: 'Browse Class'; action: [ self browseSelectedObjectClass ])). and you do not have to declare variables for that (and is a lot better than using a block, IMO). On Nov 12, 2013, at 9:36 AM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > One can just use an object too. > > Itâs just that otherwise, it pollutes a bit the method with tons of inst vars > (and then you forget to use them :P) > > Ben > > On 12 Nov 2013, at 13:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On Nov 12, 2013, at 4:22 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> It is not necessary better, but it saves you from having hundreds of temp vars :) >>> >>> Ben >>> >>> On 12 Nov 2013, at 01:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>>> >>>>> Example: >>>>> aMenu addGroup: [ :aGroup | >>>>> aGroup addItem: [ :anItem | >>>>> anItem name: 'Browse Full'; >>>>> action: [ self browseSelectedObject ]; >>>>> shortcut: $b command mac | $b alt win | $b alt unix ]. >>>>> aGroup addItem: [ :anItem | >>>>> anItem name: 'Browse Class'; >>>>> action: [ self browseSelectedObjectClass ] ] ]. >>>>> >>>> >>>> I do not see the value of passing block to add element to groups >>>> why not the normal way i.e. passing an object. I do not get why executing >>>> a block with an object is better? >> >> he, I thought the same :) >> >>>> >>>> Stef >>>> >>> >> >

Nov. 12, 2013

Re: [Pharo-dev] Spec new release :)

by StÃ©phane Ducasse

I'm working on the changeSorter menus because they do not work anymore. And we will see what we can learn from there. Stef On Nov 12, 2013, at 1:49 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Example: >> aMenu addGroup: [ :aGroup | >> aGroup addItem: [ :anItem | >> anItem name: 'Browse Full'; >> action: [ self browseSelectedObject ]; >> shortcut: $b command mac | $b alt win | $b alt unix ]. >> aGroup addItem: [ :anItem | >> anItem name: 'Browse Class'; >> action: [ self browseSelectedObjectClass ] ] ]. >> > > I do not see the value of passing block to add element to groups > why not the normal way i.e. passing an object. I do not get why executing > a block with an object is better? > > Stef >

Nov. 12, 2013

Re: [Pharo-dev] Coming back from holidays next week...

by StÃ©phane Ducasse

On Nov 12, 2013, at 1:12 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > dammit! ;) then I have to do some night shifts :P > > I think we will be busy enough with all the pending bugs in the imageâ¦ yes this is why we tried to do during the sprints of yesterday > > On 2013-11-12, at 13:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> ... and I do not want to scare anyone, but the first TODO I have in my list is "Freeze Pharo3 development, move from Alpha to Beta". >> That means: no new stuff, just stabilization... so if you have some cool thing that you want to see in next major release, push it now! >> >> Esteban >> >> >

Nov. 12, 2013

Re: [Pharo-dev] Spec new release :)

by Benjamin

One can just use an object too. Itâs just that otherwise, it pollutes a bit the method with tons of inst vars (and then you forget to use them :P) Ben On 12 Nov 2013, at 13:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Nov 12, 2013, at 4:22 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> It is not necessary better, but it saves you from having hundreds of temp vars :) >> >> Ben >> >> On 12 Nov 2013, at 01:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>>> >>>> Example: >>>> aMenu addGroup: [ :aGroup | >>>> aGroup addItem: [ :anItem | >>>> anItem name: 'Browse Full'; >>>> action: [ self browseSelectedObject ]; >>>> shortcut: $b command mac | $b alt win | $b alt unix ]. >>>> aGroup addItem: [ :anItem | >>>> anItem name: 'Browse Class'; >>>> action: [ self browseSelectedObjectClass ] ] ]. >>>> >>> >>> I do not see the value of passing block to add element to groups >>> why not the normal way i.e. passing an object. I do not get why executing >>> a block with an object is better? > > he, I thought the same :) > >>> >>> Stef >>> >> >

Nov. 12, 2013

Re: [Pharo-dev] help needed with fixing the SpecDebugger

by StÃ©phane Ducasse

On Nov 12, 2013, at 1:27 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-11-12, at 09:50, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> Camillo we should have a look together. >> >> Are you at work today ? > > yes I will come in the afternoon, but I think I have very little time this week. > I have to push some phd organization things firstâ¦ Yes pleeeeeeeeaasssssssssssse

Nov. 12, 2013