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

Re: [Pharo-dev] additional Milestone label for applications

by StÃ©phane Ducasse

thanks! This is a good idea. On Oct 6, 2013, at 1:57 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> I think it should just be fine if we define a different workflow (and thus different labels) for external projects... >>> >>> >> The 'Area' field looks unused, having only a single option 'Misc'. Perhaps that could be 'Image' and 'External Project' or similar. Most of an external project's issues would also have an area of 'External 'Project', but sometimes it might be 'Image' if a change there is required to fix an issue reported on a project. Or maybe for external projects you have only a single option 'External Project' for Area. > > So we need to have 2 things > 1. a separate project for each external project that wants to report > 2. a separate Area for these external projects > > For instance, NativeBoost has both a stable version in the image and a development > version aside. So if a bug appears in the image we can set the Area to "Pharo Image" (the default). > However, if the bug concerns the development version we set the Area to something project > specific. > > I will try to update the tracker and the filters to reflect that...

Oct. 6, 2013

Re: [Pharo-dev] [ANN] Mustache templates

by Alexandre Bergel

Thanks! Nice work! Alexandre > On 4 Oct 2013, at 07:58, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 04.10.2013 um 12:32 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: >> >> What is a mustache template? > http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ > > Norbert > >> On 4 Oct 2013, at 03:56, Torsten Bergmann <astares(a)gmx.de> wrote: >> >>>> I like to announce my smalltalk port of mustache templates. >>> >>> Cool! >>> >>>> To load it do >>> >>> Consider making a copy into MetaRepoForPharo20 or MetaReporForPharo30 >>> if it is working in these versions. >>> >>> That way it is easily accessible via Config browser. >>> >>> Thx >>> T. >

Oct. 6, 2013

Re: [Pharo-dev] additional Milestone label for applications

by Camillo Bruni

>> I think it should just be fine if we define a different workflow (and thus different labels) for external projects... >> >> > The 'Area' field looks unused, having only a single option 'Misc'. Perhaps that could be 'Image' and 'External Project' or similar. Most of an external project's issues would also have an area of 'External 'Project', but sometimes it might be 'Image' if a change there is required to fix an issue reported on a project. Or maybe for external projects you have only a single option 'External Project' for Area. So we need to have 2 things 1. a separate project for each external project that wants to report 2. a separate Area for these external projects For instance, NativeBoost has both a stable version in the image and a development version aside. So if a bug appears in the image we can set the Area to "Pharo Image" (the default). However, if the bug concerns the development version we set the Area to something project specific. I will try to update the tracker and the filters to reflect that...

Oct. 5, 2013

Re: [Pharo-dev] [update 3.0] #30455

by Camillo Bruni

On 2013-10-06, at 00:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30455 > ----- > > 11790 add critic rule for keys do: -> keysDo: (and valuesDo:) > https://pharo.fogbugz.com/f/cases/11790 > > 11787 Trivial critic cleanup of CodeImport > https://pharo.fogbugz.com/f/cases/11787 > > 11793 Package Support on RBBrowserEnvironment > https://pharo.fogbugz.com/f/cases/11793 > > 11792 First simplistic file system tree inspector > https://pharo.fogbugz.com/f/cases/11792 > > > actually a FileReference tree inspector... lots of improvments possible > inspect > > FileSystem workingDirectory > > and select the FileReference Tree Inspector ha! nice :) actually we could reuse the file list here, no?

Oct. 5, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge

Oct. 5, 2013

[update 3.0] #30455

by Marcus Denker

30455 ----- 11790 add critic rule for keys do: -> keysDo: (and valuesDo:) https://pharo.fogbugz.com/f/cases/11790 11787 Trivial critic cleanup of CodeImport https://pharo.fogbugz.com/f/cases/11787 11793 Package Support on RBBrowserEnvironment https://pharo.fogbugz.com/f/cases/11793 11792 First simplistic file system tree inspector https://pharo.fogbugz.com/f/cases/11792 actually a FileReference tree inspector... lots of improvments possible inspect FileSystem workingDirectory and select the FileReference Tree Inspector Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.1… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Environment-Marcu… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDen… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusCommon-MarcusDenker.1… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-MarcusDenker.16… http://smalltalkhub.com/mc/Pharo/Pharo30/main/CodeImport-MarcusDenker.37.di…

Oct. 5, 2013

Re: [Pharo-dev] [update 3.0] #30448

by Benjamin

I will have a look asap :P Ben On Oct 5, 2013, at 10:12 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi Ben, > > Gofer new > smalltalkhubUser: 'PavelKrivanek' project: 'Periscope'; > package: 'Periscope'; > load. > > Nautilus pluginClasses add: {(Smalltalk at: #NautilusPeriscopePlugin). #none} . > > Very useful code: ;-) > > Periscope reset > > It still without experiments with own Morphic bindings, that will be > the next step :-) Feel free to commit any changes. > > Chees, > -- Pavel > > 2013/10/5 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: >> Can you point me where to load your code and how to end up in a situation >> where I can play with the spec ? :P >> >> Ben >> >> On Oct 4, 2013, at 11:11 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >> Damn, the last row of the last plugins fills all the window... >> >> -- Pavel >> >> 2013/10/4 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >> Thanks, this seems to work: >> >> defaultSpec >> >> | layout | >> layout := SpecLayout composed. >> self pluginClasses do: [ :c | >> layout add: {#model. #class. #pluginOf:. c. #defaultSpec} ]. >> >> ^ layout. >> >> >> plugin code on the instance side looks like this: >> >> defaultSpec >> >> ^ SpecLayout composed >> newRow:[: r | >> r add: #finderButtonModel; >> add: #browserButtonModel] >> height: 25. >> >> >> -- Pavel >> >> 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: >> >> Since you are doing some really edge use of Spec, >> it's not covered by Spec easily. >> >> But if on you model you have a method returning your pluginClasses, you >> could do maybe: >> >> | layout | >> layout := SpecLayout composed. >> self pluginClasses do: [ :c | >> layout add: {#model. pluginOf:. c} ] >> >> I am not sure it works, but it worth a try :P >> >> Ben >> >> On Oct 4, 2013, at 9:28 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >> This was the original code for the spec that embeds plugins. As you >> can see, it had to use ugly addMorph:. I do not think that I need to >> do something special. Has the current Spec a better way how to do >> that? >> >> defaultSpec >> >> | spec | >> spec := OrderedCollection with: #ContainerModel. >> spec addAll: {#changeTableLayout. >> #listDirection:. #topToBottom. >> #hResizing:. #spaceFill. >> #vResizing:. #spaceFill.}. >> self pluginClasses do: [:c | >> spec add: #addMorph:. >> spec add: {(self pluginOf: c) defaultSpec}]. >> ^ spec asArray. >> >> 2013/10/4 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >> In other words... I have a model that has some plugins. I need to >> generate a spec that embeds specs generated for each plugin. Models >> for this embedded specs must be the plugins, not the original model. >> >> -- Pavel >> >> 2013/10/4 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >> well, and the version with "SpecLayout composed" when I do not need >> direct fractions? >> >> ^ SpecLayout composed >> newRow:[: r | >> r add: #finderButtonModel] >> height: 25 >> >> How to send #finderButtonModel to different object than SpecInterpreter >> model? >> >> -- Pavel >> >> 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: >> >> ^{ #ContainerModel. >> >> #vShrinkWrap. >> >> #add:. {{self. #finderButtonModel}. >> >> #layout:. #(FrameLayout >> >> rightFraction: 0.125)}. >> >> #add:. {{self. #browserButtonModel}. >> >> #layout:. #(FrameLayout >> >> leftFraction: 0.125 >> rightFraction: 0.25)}} >> >> This should work, but looks strange though :P >> >> Ben >> >> On Oct 4, 2013, at 8:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >> Ben, >> >> how now should look code like this: >> >> defaultSpec >> >> ^{ #ComposableSpec. >> #vResizing:. #shrinkWrap. >> #add:. {{self. #finderButtonModel}. >> #layout:. #(FrameLayout >> rightFraction: 0.125)}. >> #add:. {{self. #browserButtonModel}. >> #layout:. #(FrameLayout >> leftFraction: 0.125 >> rightFraction: 0.25)}} >> >> -- Pavel >> >> 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: >> >> For Spec users: >> >> The change is mostly backward compatible :) >> 2 things really changed: >> - direct access to a model's widget is not returning what it used to return. >> This is done on purpose since >> it's very often a bad idea to directly access the widget. >> - some behaviour on trees are now only available after the tree build. This >> is because some properties >> have been moved on the adapter directly, which is reachable only after the >> model build. >> You can use `whenBuiltDo:` to add post-build actions. >> >> Enjoy this new Spec :P >> >> Ben >> >> On Oct 4, 2013, at 2:31 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> 30448 >> ----- >> >> 11740 Remove Morphic dependency from Spec >> https://pharo.fogbugz.com/f/cases/11740 >> >> A Huge change from Ben... >> >> Diff information: >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1292.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tabs-MarcusDenker.33.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.265… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-MarcusDenker.150.d… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tests-MarcusDenker.35.di… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-MorphicAdapters-MarcusDe… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-PolyWidgets-MarcusDenker… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Layout-MarcusDenker.58.d… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.1… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Examples-MarcusDenker.48… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.16… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.175.di… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Builder-MarcusDenker.43.… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Bindings-MarcusDenker.35… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-MarcusDen… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Adapters-MarcusDenker.3.… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-Tools-Spec-MarcusD… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/KeyChain-MarcusDenker.58.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-MarcusDenk… >> >> >> >> >> >> >> >> >> >

Oct. 5, 2013

Re: [Pharo-dev] [update 3.0] #30448

by Pavel Krivanek

Hi Ben, Gofer new smalltalkhubUser: 'PavelKrivanek' project: 'Periscope'; package: 'Periscope'; load. Nautilus pluginClasses add: {(Smalltalk at: #NautilusPeriscopePlugin). #none} . Very useful code: ;-) Periscope reset It still without experiments with own Morphic bindings, that will be the next step :-) Feel free to commit any changes. Chees, -- Pavel 2013/10/5 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > Can you point me where to load your code and how to end up in a situation > where I can play with the spec ? :P > > Ben > > On Oct 4, 2013, at 11:11 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > Damn, the last row of the last plugins fills all the window... > > -- Pavel > > 2013/10/4 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > Thanks, this seems to work: > > defaultSpec > > | layout | > layout := SpecLayout composed. > self pluginClasses do: [ :c | > layout add: {#model. #class. #pluginOf:. c. #defaultSpec} ]. > > ^ layout. > > > plugin code on the instance side looks like this: > > defaultSpec > > ^ SpecLayout composed > newRow:[: r | > r add: #finderButtonModel; > add: #browserButtonModel] > height: 25. > > > -- Pavel > > 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > > Since you are doing some really edge use of Spec, > it's not covered by Spec easily. > > But if on you model you have a method returning your pluginClasses, you > could do maybe: > > | layout | > layout := SpecLayout composed. > self pluginClasses do: [ :c | > layout add: {#model. pluginOf:. c} ] > > I am not sure it works, but it worth a try :P > > Ben > > On Oct 4, 2013, at 9:28 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > This was the original code for the spec that embeds plugins. As you > can see, it had to use ugly addMorph:. I do not think that I need to > do something special. Has the current Spec a better way how to do > that? > > defaultSpec > > | spec | > spec := OrderedCollection with: #ContainerModel. > spec addAll: {#changeTableLayout. > #listDirection:. #topToBottom. > #hResizing:. #spaceFill. > #vResizing:. #spaceFill.}. > self pluginClasses do: [:c | > spec add: #addMorph:. > spec add: {(self pluginOf: c) defaultSpec}]. > ^ spec asArray. > > 2013/10/4 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > In other words... I have a model that has some plugins. I need to > generate a spec that embeds specs generated for each plugin. Models > for this embedded specs must be the plugins, not the original model. > > -- Pavel > > 2013/10/4 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > well, and the version with "SpecLayout composed" when I do not need > direct fractions? > > ^ SpecLayout composed > newRow:[: r | > r add: #finderButtonModel] > height: 25 > > How to send #finderButtonModel to different object than SpecInterpreter > model? > > -- Pavel > > 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > > ^{ #ContainerModel. > > #vShrinkWrap. > > #add:. {{self. #finderButtonModel}. > > #layout:. #(FrameLayout > > rightFraction: 0.125)}. > > #add:. {{self. #browserButtonModel}. > > #layout:. #(FrameLayout > > leftFraction: 0.125 > rightFraction: 0.25)}} > > This should work, but looks strange though :P > > Ben > > On Oct 4, 2013, at 8:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Ben, > > how now should look code like this: > > defaultSpec > > ^{ #ComposableSpec. > #vResizing:. #shrinkWrap. > #add:. {{self. #finderButtonModel}. > #layout:. #(FrameLayout > rightFraction: 0.125)}. > #add:. {{self. #browserButtonModel}. > #layout:. #(FrameLayout > leftFraction: 0.125 > rightFraction: 0.25)}} > > -- Pavel > > 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > > For Spec users: > > The change is mostly backward compatible :) > 2 things really changed: > - direct access to a model's widget is not returning what it used to return. > This is done on purpose since > it's very often a bad idea to directly access the widget. > - some behaviour on trees are now only available after the tree build. This > is because some properties > have been moved on the adapter directly, which is reachable only after the > model build. > You can use `whenBuiltDo:` to add post-build actions. > > Enjoy this new Spec :P > > Ben > > On Oct 4, 2013, at 2:31 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 30448 > ----- > > 11740 Remove Morphic dependency from Spec > https://pharo.fogbugz.com/f/cases/11740 > > A Huge change from Ben... > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1292.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tabs-MarcusDenker.33.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.265… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-MarcusDenker.150.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tests-MarcusDenker.35.di… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-MorphicAdapters-MarcusDe… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-PolyWidgets-MarcusDenker… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Layout-MarcusDenker.58.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.1… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Examples-MarcusDenker.48… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.16… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.175.di… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Builder-MarcusDenker.43.… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Bindings-MarcusDenker.35… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-MarcusDen… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Adapters-MarcusDenker.3.… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-Tools-Spec-MarcusD… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/KeyChain-MarcusDenker.58.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-MarcusDenk… > > > > > > > > >

Oct. 5, 2013

Re: [Pharo-dev] additional Milestone label for applications

by btc＠openinworld.com

Oct. 5, 2013

Re: [Pharo-dev] add me to the PharoExtras/Gettext package please

by Camillo Bruni

ok found it :), you're in On 2013-10-05, at 18:22, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Which username? > > On 2013-10-05, at 18:14, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> The Configuration there doesn't reference the Seaside related packages or the Gemstone version so I'd like to upload a config that does. >> >> >> >> >> Thanks >> >> Paul >

Oct. 5, 2013