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

Re: [Pharo-dev] WhatsUp from: 2013-07-15 until: 2013-07-31

by StÃ©phane Ducasse

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - working on Pharo Catalog - migrating chapters to Gutenberg > ### What's next, until 2013-07-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - releasing Pharo Catalog - working Log > > (*) we'll be expecting results by then ;) >

July 15, 2013

Re: [Pharo-dev] New Wiki page on Fogbugz

by StÃ©phane Ducasse

do you have the videos of the demo you did on dynamic aspects? Stef On Jul 15, 2013, at 10:06 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Hi guys :) > > I just created a public wiki page on Fogbugz gathering links to Spec Documentation > > Here is the link https://pharo.fogbugz.com/default.asp?W67 > > I hope it will be useful :) > > Ben

July 15, 2013

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

by Camillo Bruni

On 2013-07-15, at 10:34, Camille Teruel <camille.teruel(a)gmail.com> wrote: > On 13 juil. 2013, at 14:44, Camillo Bruni wrote: > >> If you put all methods from ClassDescriptions in traits and move them on >> Class and Metaclass there is no need for ClassDescription. > > Except for "instanceVariables" and "organization" ivs of ClassDescription. > Were you thinking about stateful traits? You're right I forgot about these two. But yeah, stateful traits can easily help here ;) Actually #instanceVariables becomes obsolete with layouts present, no? Then the only thing left is organization

July 15, 2013

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

by Sebastian Tleye

Or moving those instance variables to their subclasses (Class and Metaclass) 2013/7/15 Camille Teruel <camille.teruel(a)gmail.com> > > On 13 juil. 2013, at 14:44, Camillo Bruni wrote: > > > If you put all methods from ClassDescriptions in traits and move them on > > Class and Metaclass there is no need for ClassDescription. > > Except for "instanceVariables" and "organization" ivs of ClassDescription. > Were you thinking about stateful traits? > > > If previously you want something that inherited from ClassDescription you > > can simply include the traits now. > > > > In the case of a Behavior subclass nothing changes. > > > > > On 2013-07-13, at 14:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> Why can't we keep ClassDescription. > >> Then in addition Behavior is a nice class to have to build strange > stuff. > >> > >> Stef > >> > >> On Jul 12, 2013, at 7:22 AM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > >> > >>> On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano < > estebanlm(a)gmail.com> wrote: > >>>> 11151 More changes needed to trait/classes polymorphism > >>>> https://pharo.fogbugz.com/f/cases/11151/ > >>> > >>> > >>> That's huge. Soon, we will be able to remove thr ClassDescription and > >>> Behavior classes. It makes sense because they are useless in the > >>> presence of traits. But do people want it? > >>> > >>> -- > >>> Damien Cassou > >>> http://damiencassou.seasidehosting.st > >>> > >>> "Success is the ability to go from one failure to another without > >>> losing enthusiasm." > >>> Winston Churchill > >>> > >> > >> > > > > > > >

July 15, 2013

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

by Camille Teruel

On 13 juil. 2013, at 14:44, Camillo Bruni wrote: > If you put all methods from ClassDescriptions in traits and move them on > Class and Metaclass there is no need for ClassDescription. Except for "instanceVariables" and "organization" ivs of ClassDescription. Were you thinking about stateful traits? > If previously you want something that inherited from ClassDescription you > can simply include the traits now. > > In the case of a Behavior subclass nothing changes. > > On 2013-07-13, at 14:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Why can't we keep ClassDescription. >> Then in addition Behavior is a nice class to have to build strange stuff. >> >> Stef >> >> On Jul 12, 2013, at 7:22 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> >>> On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> 11151 More changes needed to trait/classes polymorphism >>>> https://pharo.fogbugz.com/f/cases/11151/ >>> >>> >>> That's huge. Soon, we will be able to remove thr ClassDescription and >>> Behavior classes. It makes sense because they are useless in the >>> presence of traits. But do people want it? >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >> >> > >

July 15, 2013

New Wiki page on Fogbugz

by Benjamin

Hi guys :) I just created a public wiki page on Fogbugz gathering links to Spec Documentation Here is the link https://pharo.fogbugz.com/default.asp?W67 I hope it will be useful :) Ben

July 15, 2013

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

by Sebastian Tleye

After all my changes you will only love them :) 2013/7/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > I imagine that quite well :) but my love/hate relationship with trait > always bugs me :) > > > On Jul 13, 2013, at 2:44 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > If you put all methods from ClassDescriptions in traits and move them on > > Class and Metaclass there is no need for ClassDescription. > > > > If previously you want something that inherited from ClassDescription you > > can simply include the traits now. > > > > In the case of a Behavior subclass nothing changes. > > > > On 2013-07-13, at 14:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> Why can't we keep ClassDescription. > >> Then in addition Behavior is a nice class to have to build strange > stuff. > >> > >> Stef > >> > >> On Jul 12, 2013, at 7:22 AM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > >> > >>> On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano < > estebanlm(a)gmail.com> wrote: > >>>> 11151 More changes needed to trait/classes polymorphism > >>>> https://pharo.fogbugz.com/f/cases/11151/ > >>> > >>> > >>> That's huge. Soon, we will be able to remove thr ClassDescription and > >>> Behavior classes. It makes sense because they are useless in the > >>> presence of traits. But do people want it? > >>> > >>> -- > >>> Damien Cassou > >>> http://damiencassou.seasidehosting.st > >>> > >>> "Success is the ability to go from one failure to another without > >>> losing enthusiasm." > >>> Winston Churchill > >>> > >> > >> > > > > > > >

July 15, 2013

Re: [Pharo-dev] WhatsUp from: 2013-07-15 until: 2013-07-31

by Damien Cassou

### Here's what I've been up to since the last WhatsUp: release of PharoLauncher (http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher) block chapter for Deep Into Pharo (https://ci.inria.fr/pharo-contribution/job/DeepIntoPharo/) + update glamour and petit parser chapters Pharo tutorial at Montpellier, France ### What's next, until 2013-07-31 (*): -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 15, 2013

Re: [Pharo-dev] Can't open image file without write access

by Damien Cassou

On Sun, Jul 14, 2013 at 9:45 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > are you sure this is image file, not .changes? both are read-only. I will check how to deactivate the startup and shudown scripts as Camillo suggested. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 15, 2013

Re: [Pharo-dev] opal bug with the old debugger

by ClÃ©ment Bera

Hi, Actually I saw the bug, tried in the new debugger, it worked. So I didn't fix it because the new debugger will be integrated before the release. 2013/7/14 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > Hi, > > Executing '1 haba' in a workspace and then choosing create method from the > pre debug window leads to this > exception: UndefinedObject(Object)>>doesNotUnderstand: #methodOrBlockNode > > If instead I choose to debug, select the top context of the stack and the > press the 'Creare method' button a different exception is > thrown: UndefinedObject(Object)>>doesNotUnderstand: #debugHighlightRange > > In both cases the method is created. > > So known or unknown issue? > Also it doesn't seem to happen with the new debugger. Not sure why :) > > Andrei >

July 15, 2013