May 2014 - Pharo-dev - lists.pharo.org

Pharo in Rasbian ?

by Alexandre Bergel

Hi! A friend of mine recently bought a Raspberry pi and installed Rasbian, a Debian-like OS for Raspberry. Squeak and Scratch are installed per default. There is room to fill here... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 20, 2014

Re: [Pharo-dev] Mustache

by Norbert Hartl

I tried that already. But as with most hipster projects nobody feels responsible anymore. I contacted the original author but I he has nothing to do anymore with it. I tried to track it down (because besides a cool ascii art picture there is no contact data on the site) und even found I guy I know from berlin but he didnât respond. So I decided I have better things to do then to run after people which donât care about their projectâ¦ Norbert Am 20.05.2014 um 15:06 schrieb Torsten Bergmann <astares(a)gmx.de>: > Hi Norbert, > > http://mustache.github.io/ does not mention the port for Pharo Smalltalk. > > Maybe you should contact them to add a link to > http://smalltalkhub.com/#!/~NorbertHartl/Mustache. > > Such links can help getting more visibility. > > Thx > T.

May 20, 2014

Re: [Pharo-dev] compiling Pillar files locally (for LaserGame book)

by Stephan Eggermont

And of course there is no need to have a lower number of screenshots now you can generate them from the image. Stephan

May 20, 2014

Mustache

by Torsten Bergmann

Hi Norbert, http://mustache.github.io/ does not mention the port for Pharo Smalltalk. Maybe you should contact them to add a link to http://smalltalkhub.com/#!/~NorbertHartl/Mustache. Such links can help getting more visibility. Thx T.

May 20, 2014

Re: [Pharo-dev] Versionner is even Coooler

by Christophe Demarey

Le 20 mai 2014 Ã 14:28, Ben Coman a Ã©crit : > Christophe Demarey wrote: >> >> Thanks a lot for all your nice words. >> You were right, there are other contributors to Versionner: first author Alexandre Bergel, then Juan Pablo Sandoval but also a lot of feedbacks from users (a mention to Sean for that) essential for such a tool. >> >> Le 20 mai 2014 Ã 10:10, kilon alios a Ã©crit : >> >> >>> can someone explain "save to development" ? >>> >> >> When you do structural changes* in your configuration, it is done "in memory". To keep theses changes, you need to save them in the configuration. It is always done in the development version (the only version you can edit is the development version) that is backed by a baseline. >> If you need to do structural changes, use "Save to development" to flush your changes. If you only need to generate a new version with packages numbers updated, then use the "release version" button. >> >> * structural change: basically a change made to a baseline: addition/removal of a package / project group, edition of requirements or includes directives. >> >> >> If it is not clear, don't hesitate to ask more explanation. >> >> Best regards, >> Christophe. > > So would "Save to baseline" mean the same as "Save to development"? Kind of. The idea is to hide the baseline complexity from the user point of view. The user only see releases (numbered version) and the development version where changes are possible. 'Save to baseline' is not clear about the baseline that will be used to save. In fact, development points to the latest baseline and creates new one if needed (ex: baseline used by a release that you need to edit).

May 20, 2014

Re: [Pharo-dev] Versionner is even Coooler

by Ben Coman

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Goubier Thierry

Le 20/05/2014 13:22, Tudor Girba a Ã©crit : > Yes, of course I know about tags. But, they are not used so prominently > just yet. For example, take the AST packages: > - AST-Core > - AST-Interpreter-Core > - AST-Interpreter-Extension > - AST-Interpreter-Test > - AST-Tests-Core > > Of these, AST-Core does have tags, but the rest are not explicitly > related to the AST concept. By using string magic in this case all of > these would appear close together. > > That is why I used strings instead of tags. We probably have a few versions of code doing packages classifications based on prefix floating around :) It works fairly well. I do have some code which also scans catalogKeywords in configurations to improve the classification. Thierry -- 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

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Tudor Girba

Yes, of course I know about tags. But, they are not used so prominently just yet. For example, take the AST packages: - AST-Core - AST-Interpreter-Core - AST-Interpreter-Extension - AST-Interpreter-Test - AST-Tests-Core Of these, AST-Core does have tags, but the rest are not explicitly related to the AST concept. By using string magic in this case all of these would appear close together. That is why I used strings instead of tags. Cheers, Doru On Tue, May 20, 2014 at 11:13 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: > Hi Doru. > > Thank you for explanation. On question. We have a construct called âtagâ > on the package level, so we can reason about the parts of the package on > object level. Do we really need to go into string parsing? > > Uko > > On 18 May 2014, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I was asked several times for how the visualization from the Pharo 3.0 > announcement was created. I now put together a blog post to explain it: > http://www.humane-assessment.com/blog/communicating-changes-in-pharo-3-0 > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

May 20, 2014

Re: [Pharo-dev] Versionner is even Coooler

by kilon alios

thank you its clear. On Tue, May 20, 2014 at 11:46 AM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Thanks a lot for all your nice words. > You were right, there are other contributors to Versionner: first author > Alexandre Bergel, then Juan Pablo Sandoval but also a lot of feedbacks from > users (a mention to Sean for that) essential for such a tool. > > Le 20 mai 2014 Ã 10:10, kilon alios a Ã©crit : > > > can someone explain "save to development" ? > > When you do structural changes* in your configuration, it is done "in > memory". To keep theses changes, you need to save them in the > configuration. It is always done in the development version (the only > version you can edit is the development version) that is backed by a > baseline. > If you need to do structural changes, use "Save to development" to flush > your changes. If you only need to generate a new version with packages > numbers updated, then use the "release version" button. > > * structural change: basically a change made to a baseline: > addition/removal of a package / project group, edition of requirements or > includes directives. > > > If it is not clear, don't hesitate to ask more explanation. > > Best regards, > Christophe.

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Yuriy Tymchuk

Hi Doru. Thank you for explanation. On question. We have a construct called âtagâ on the package level, so we can reason about the parts of the package on object level. Do we really need to go into string parsing? Uko On 18 May 2014, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I was asked several times for how the visualization from the Pharo 3.0 announcement was created. I now put together a blog post to explain it: > http://www.humane-assessment.com/blog/communicating-changes-in-pharo-3-0 > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow"

May 20, 2014