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

[Pharo-project] save as...

by Norbert Hartl

Was there a discussion about "save asâ¦" should not increment the image file number? Any links to it or was it by accident. In my opinion I liked the difference between save = same file name, save asâ¦ = new automatical filename Norbert

April 30, 2013

Re: [Pharo-project] Where are your package configs for Pharo 2.0

by Sean P. DeNigris

EstebanLM wrote > we cannot make a process to discover the hidden configurations all over > the web, to then validate them and copy to the appropriate repo. Why not?! ;-P It wouldn't be the most outrageous and amazing thing we've ever done... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Where-are-your-package-configs-for-Pharo-2-0-tp468456… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 30, 2013

Re: [Pharo-project] Where are your package configs for Pharo 2.0

by Esteban Lorenzano

well, some human iteration will always be needed... we cannot make a process to discover the hidden configurations all over the web, to then validate them and copy to the appropriate repo. Esteban On Apr 30, 2013, at 2:05 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Maybe this shows that we really need the automated process we are looking/wishing since a long time :) > > > On Tue, Apr 30, 2013 at 8:03 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > I heard about RFB already working on Pharo 2.0 > I heard about Seaside 3.0.8 already work in Pharo 2.0 > I heard about SandstoneDB is now adopted for Pharo 2.0 > I heard about ... already work in Pharo 2.0 > ... > > So please: update your ConfigurationOfXXX and put working > configs with a #stable definition for Pharo 2.0 into the writable > > http://ss3.gemstone.com/ss/MetaRepoForPharo20 > > repo so they show up on Config Browser and can be > easily installed. > > Your packages and projects will never be visible if you hide > them on ss, ss3 or SmalltalkHub. > > Also I hope for a Seaside 3.1 config for Pharo 2.0 > which would really be a step forward ... > > Bye > T. > > > > > > -- > Mariano > http://marianopeck.wordpress.com

April 30, 2013

Re: [Pharo-project] FLClassNotFound on materialization

by Max Leske

http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.9/Documentation/… FLMaterializer newDefault migrateClassNamed: #Point toClass: Coordinate. HTH, Max On 30.04.2013, at 14:42, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > I wonder if this feature is already implemented? > > http://lists.gforge.inria.fr/pipermail/pharo-project/2011-November/056143.h… > > because I have a map of class renames but I don't know how to tell the materializer to serialize and re-materialize with updated names. > > I am using Fuel 1.8 in Pharo 1.4 (Fuel-MartinDias.685, FuelCompatibilityBeforePharo20-MartinDias.4) > > Cheers, > > HernÃ¡n > >

April 30, 2013

[Pharo-project] FLClassNotFound on materialization

by HernÃ¡n Morales Durand

I wonder if this feature is already implemented? http://lists.gforge.inria.fr/pipermail/pharo-project/2011-November/056143.h… because I have a map of class renames but I don't know how to tell the materializer to serialize and re-materialize with updated names. I am using Fuel 1.8 in Pharo 1.4 (Fuel-MartinDias.685, FuelCompatibilityBeforePharo20-MartinDias.4) Cheers, HernÃ¡n

April 30, 2013

[Pharo-project] Where are your package configs for Pharo 2.0

by Torsten Bergmann

>Maybe this shows that we really need the automated process we are >looking/wishing since a long time :) We dont have that now. So remember the Pharo idea: step by step. Typically: 1. You have to adopt/port a package for a new Pharo version (here 2.0) 2. adopt the config to load 3. verify that it is running Even with an automagically process (mostly for step 3) you will have to do some initial invest to get it rolling. So please: if you already ported/adopted a package for Pharo 2.0, just defined a #stable for Pharo 2.0 and put a copy of the config into the repo http://ss3.gemstone.com/ss/MetaRepoForPharo20 Note that there is a "Copy" button on your mcz browser which one can easily use from time to time if you know your config is working ;) Bye T.

April 30, 2013

[Pharo-project] dynamic spec contents

by Camillo Bruni

Clement and I are working on the new Inspectors/Debuggers and we would like yo dynamically change spec widgets on the fly. Is there an example of that somewhere?

April 30, 2013

Re: [Pharo-project] Where are your package configs for Pharo 2.0

by Mariano Martinez Peck

Maybe this shows that we really need the automated process we are looking/wishing since a long time :) On Tue, Apr 30, 2013 at 8:03 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > I heard about RFB already working on Pharo 2.0 > I heard about Seaside 3.0.8 already work in Pharo 2.0 > I heard about SandstoneDB is now adopted for Pharo 2.0 > I heard about ... already work in Pharo 2.0 > ... > > So please: update your ConfigurationOfXXX and put working > configs with a #stable definition for Pharo 2.0 into the writable > > http://ss3.gemstone.com/ss/MetaRepoForPharo20 > > repo so they show up on Config Browser and can be > easily installed. > > Your packages and projects will never be visible if you hide > them on ss, ss3 or SmalltalkHub. > > Also I hope for a Seaside 3.1 config for Pharo 2.0 > which would really be a step forward ... > > Bye > T. > > > -- Mariano http://marianopeck.wordpress.com

April 30, 2013

Re: [Pharo-project] about Pharo 3.0 :)

by Camille Teruel

On 30 avr. 2013, at 13:19, Marcus Denker wrote: > > On Apr 30, 2013, at 1:06 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> On 30 April 2013 07:50, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I thought that Pharo 20 got a lot of improvements but when I see Pharo 30, it feels like Pharo 30 is already a big step >> forward. This is really positive energy. When fernando will arrive we will move some efforts to Morphic >> so thanks you all for this cool feeling. >> >> Stef >> >> Yes, Opal opened doors for so many improvementsâ¦ > > We started to re-vive Reflectivity (Camille and me). > > http://scg.unibe.ch/research/reflectivity > > Status: Camille is implementing an AST transformer that takes an AST annotated with Meta Links to produce > a new AST. Me: Refactoring like mad the 3.0 and Opal with the goal to be able to add the Transformer > as a plugin to the compilation chain. > For now the AST transformer puts blocks everywhere because it's simpler. For example, if a node has the five possible links (before, instead, onSuccess, onError, after), it's expanded like this: [ <before link>. <instead link> ] onSuccess: [ <onSuccess link> ] onError: [ <onError link> ] ensure: [ <after link> ] It is far from being optimal but I think it will be fast enough for most use cases (one rarely needs more than one link per node). > Marcus. > > >

April 30, 2013

Re: [Pharo-project] about Pharo 3.0 :)

by Marcus Denker

On Apr 30, 2013, at 1:06 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > On 30 April 2013 07:50, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I thought that Pharo 20 got a lot of improvements but when I see Pharo 30, it feels like Pharo 30 is already a big step > forward. This is really positive energy. When fernando will arrive we will move some efforts to Morphic > so thanks you all for this cool feeling. > > Stef > > Yes, Opal opened doors for so many improvementsâ¦ We started to re-vive Reflectivity (Camille and me). http://scg.unibe.ch/research/reflectivity Status: Camille is implementing an AST transformer that takes an AST annotated with Meta Links to produce a new AST. Me: Refactoring like mad the 3.0 and Opal with the goal to be able to add the Transformer as a plugin to the compilation chain. Marcus.

April 30, 2013