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

Activity Diagram

by Serge Stinckwich

Dear all, with a colleague from Savoie University, we are looking for some Smalltalk code in order to model, execute and animate Activity Diagram. Any existing works ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 23, 2013

Re: [Pharo-dev] Instance-side extensions show on class-side of extending package, and vice-versa.

by Esteban Lorenzano

Hi, Sorry, but even if you are right Iâm not sure I will accept that now. Code freeze means code freeze: No enhancements, just bugfixes. So I donât know if your suggestion is appropriate or not, but in any case is not appropriate in this stage. Of course, if the agreement is that is a good addition, I will be happy to include it in pharo 4. Esteban On 23 Dec 2013, at 03:09, btc(a)openinworld.com wrote: > I'd like to survey community opinion on case [1] that I logged. I'll summarize discussion here for the ticket. > > Currently with Nautilus, when Package A is extended by Package B adding instance-method #m1 protocol *A to class C, > class C shows up (in grey) under Package A even when the <Class side> checkbox is checked. > My opinion is that class C should only show under Package A when looking at the instance-side, > and not show when looking at the class-side. What is your opinon... > > Q: Should an instance-side extension show up on the class-side of the extending package? (and vice-versa) > For more info, see 'Steps to reproduce' in [1] > > [1] https://pharo.fogbugz.com/f/cases/12178/Instance-side-extensions-show-on-cl… > > cheers -ben

Dec. 23, 2013

Re: [Pharo-dev] Problem with filetree

by Benjamin

I am :) Thanks for the pointer :) Issue reported here: https://github.com/dalehenrich/filetree/issues/119 Ben On 23 Dec 2013, at 12:58, Max Leske <maxleske(a)gmail.com> wrote: > Sounds like a bug... > Please open a bug report on https://github.com/dalehenrich/filetree? > > Cheers, > Max > > On 23.12.2013, at 12:41, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> Step to reproduce >> >> git clone https://github.com/BenjaminVanRyseghem/pharo-core.git >> >> And in Pharo evaluate >> >> >> | repo names | >> repo := MCFileTreeRepository new directory: '.' asFileReference. >> >> names := repo packageDescriptionsFromReadableFileNames. >> names do: [ : name || version | >> version := repo versionFromFileNamed: name first, '.package'. >> [ version load ] >> on: MCMergeOrLoadWarning >> do: [ :ex | ex load ] ] >> >> >> This will apply all the packages in your Pharo image >> >> Ben >> >> On 23 Dec 2013, at 12:35, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> Hello guys, >>> >>> I am playing a bit with filet tree, and it seems there is a little problem with escaping the selector #\ and #\\ >>> If you try to export Collection and to load it back, it seems that when #\ is exported in JSON, the key should be â\\â >>> to escape the selector, but itâs simply â\â >>> >>> And then, when you try to load it, the parser escape correctly, so the selector read is #â : â >>> Because of this, the package can not be loaded >>> >>> Is it a known bug ? >>> What is strange is that it happens only twice in all the Pharo packages >>> >>> Ben >>> >> >

Dec. 23, 2013

Re: [Pharo-dev] Problem with filetree

by Max Leske

Sounds like a bug... Please open a bug report on https://github.com/dalehenrich/filetree? Cheers, Max On 23.12.2013, at 12:41, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Step to reproduce > > git clone https://github.com/BenjaminVanRyseghem/pharo-core.git > > And in Pharo evaluate > > > | repo names | > repo := MCFileTreeRepository new directory: '.' asFileReference. > > names := repo packageDescriptionsFromReadableFileNames. > names do: [ : name || version | > version := repo versionFromFileNamed: name first, '.package'. > [ version load ] > on: MCMergeOrLoadWarning > do: [ :ex | ex load ] ] > > > This will apply all the packages in your Pharo image > > Ben > > On 23 Dec 2013, at 12:35, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> Hello guys, >> >> I am playing a bit with filet tree, and it seems there is a little problem with escaping the selector #\ and #\\ >> If you try to export Collection and to load it back, it seems that when #\ is exported in JSON, the key should be â\\â >> to escape the selector, but itâs simply â\â >> >> And then, when you try to load it, the parser escape correctly, so the selector read is #â : â >> Because of this, the package can not be loaded >> >> Is it a known bug ? >> What is strange is that it happens only twice in all the Pharo packages >> >> Ben >> >

Dec. 23, 2013

Re: [Pharo-dev] Problem with filetree

by Benjamin

Step to reproduce git clone https://github.com/BenjaminVanRyseghem/pharo-core.git And in Pharo evaluate | repo names | repo := MCFileTreeRepository new directory: '.' asFileReference. names := repo packageDescriptionsFromReadableFileNames. names do: [ : name || version | version := repo versionFromFileNamed: name first, '.package'. [ version load ] on: MCMergeOrLoadWarning do: [ :ex | ex load ] ] This will apply all the packages in your Pharo image Ben On 23 Dec 2013, at 12:35, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Hello guys, > > I am playing a bit with filet tree, and it seems there is a little problem with escaping the selector #\ and #\\ > If you try to export Collection and to load it back, it seems that when #\ is exported in JSON, the key should be â\\â > to escape the selector, but itâs simply â\â > > And then, when you try to load it, the parser escape correctly, so the selector read is #â : â > Because of this, the package can not be loaded > > Is it a known bug ? > What is strange is that it happens only twice in all the Pharo packages > > Ben >

Dec. 23, 2013

Problem with filetree

by Benjamin

Hello guys, I am playing a bit with filet tree, and it seems there is a little problem with escaping the selector #\ and #\\ If you try to export Collection and to load it back, it seems that when #\ is exported in JSON, the key should be â\\â to escape the selector, but itâs simply â\â And then, when you try to load it, the parser escape correctly, so the selector read is #â : â Because of this, the package can not be loaded Is it a known bug ? What is strange is that it happens only twice in all the Pharo packages Ben

Dec. 23, 2013

Instance-side extensions show on class-side of extending package, and vice-versa.

by btc＠openinworld.com

Dec. 23, 2013

Re: [Pharo-dev] WhatsUp from: 2013-12-16 until: 2013-12-31

by Tudor Girba

### Here's what I've been up to since the last WhatsUp: - Extended GTInspector significantly to support multiple use cases - Documented the GTInspector: http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ - Worked with Andrei on the GTDebugger ### What's next, until 2013-12-31 (*): - Work on convincing the Pharo world that these GT tools can imply a significant productivity boost :) - Continue working on the GTInspector to support snippets (pieces of code related to your objects) - Still need to translate the Moose book into Pillar :) -- www.tudorgirba.com "Every thing has its own flow"

Dec. 22, 2013

Re: [Pharo-dev] [OT] SqueakJS - SqueakVM running on JavaScript

by Sebastian Sastre

ha! fantastic On Dec 22, 2013, at 12:50 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Really cool - Bert wrote a SqueakVM running on top of JavaScript: > > > SqueakJS blog post: http://croquetweak.blogspot.de/2013/12/squeakjs-lively-squeak-vm.html > SqueakJS Lively access: http://lively-web.org/users/bert/squeak.html > > Running the mini.image (demo): http://bertfreudenberg.github.io/SqueakJS/demo/simple.html > > VM Project: https://github.com/bertfreudenberg/SqueakJS/ > VM Source code: https://github.com/bertfreudenberg/SqueakJS/blob/master/vm.js >

Dec. 22, 2013

[OT] SqueakJS - SqueakVM running on JavaScript

by Torsten Bergmann

Really cool - Bert wrote a SqueakVM running on top of JavaScript: SqueakJS blog post: http://croquetweak.blogspot.de/2013/12/squeakjs-lively-squeak-vm.html SqueakJS Lively access: http://lively-web.org/users/bert/squeak.html Running the mini.image (demo): http://bertfreudenberg.github.io/SqueakJS/demo/simple.html VM Project: https://github.com/bertfreudenberg/SqueakJS/ VM Source code: https://github.com/bertfreudenberg/SqueakJS/blob/master/vm.js

Dec. 22, 2013