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

Re: [Pharo-project] Issues Tagged 1.2 on the BugTracker

by StÃ©phane Ducasse

Thanks marcus. So what is the process do we declare 1.2 beta? Stef On Oct 31, 2010, at 9:17 AM, Marcus Denker wrote: > 37 out of 387: > > http://code.google.com/p/pharo/issues/list?cursor=2858 > > ... not all are showstoppers. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Oct. 31, 2010

Re: [Pharo-project] [OffTopoc] Symbol understands value: nice hehehehehhe

by StÃ©phane Ducasse

+1 especially when this is specific to a given system > I like the idea of using fooValue: instead of value:. > > On 10/30/10 14:15 , Tudor Girba wrote: >> We use this pattern in Mondrian scripts, Glamour scripts, and in Moose scripts for navigating models. >> >> However, we are most of the times doing it with other Symbol selectors. For example: >> - in Mondrian, we use moValue: >> - in Glamour, we use glamourValue: >> >> Using dedicated extensions enable us to control the kinds of semantics we want in the scripting. For example, the glamourValue: is different from moValue:. >> >> Cheers, >> Doru >> >> >> On 30 Oct 2010, at 22:56, Andres Valloud wrote: >> >>> Mariano, >>> >>> On 10/30/10 13:14 , Mariano Martinez Peck wrote: >>> >>>> 100% agree. It was just funny for me, how could I do that, just >>>> implementing Synbol>> value: >>>> Just something curious and funny. Not to really use it. >>> >>> I agree with this, polymorphism is awesome. For instance, something I did with Assessments was to make objects polymorphic with classes. This device allows Assessments to run SUnit tests without needing to touch any of the test case classes (you can just create pseudo-classes that pretend to be the classes you need but can't have). And you get to implement #new on the instance side :). >>> >>> Andres. >>> >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> . >> >

Oct. 31, 2010

[Pharo-project] how to load magritte in seaside 3.0?

by stephane ducasse

Hi I want to load magritte with Seaside 3.0 and I followed http://book.pharo-project.org/book/PharoTools/Magritte/ Magritte2 For Pharo With Seaside 3 Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagritte'; load. (ConfigurationOfMagritte2 project version: '2.0.5') load but I does not load. Stef

Oct. 31, 2010

Re: [Pharo-project] Changes not working since update

by Marcus Denker

On Oct 31, 2010, at 9:21 AM, Marcus Denker wrote: > > > I checked: yes, one needs to open the changesorter once to get any > changes recorded. > > This is a bug... maybe some #initialize call is missing in the cleanup code? http://code.google.com/p/pharo/issues/detail?id=3189 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 31, 2010

Re: [Pharo-project] Changes not working since update

by Marcus Denker

On Oct 31, 2010, at 2:47 AM, Igor Stasenko wrote: > after updating pharo core image (Update #12220), > the list of changes is just one: 'Unnamed', Yes, that comes from the #releaseCleanup cleaning the changesets. > also, it was empty once i tried to check what changes i did to image, > after some coding. > Once i created a new changeset, and changed few things, these changes > recorded properly in new changeset I checked: yes, one needs to open the changesorter once to get any changes recorded. This is a bug... maybe some #initialize call is missing in the cleanup code? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 31, 2010

[Pharo-project] Issues Tagged 1.2 on the BugTracker

by Marcus Denker

37 out of 387: http://code.google.com/p/pharo/issues/list?cursor=2858 ... not all are showstoppers. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 31, 2010

[Pharo-project] Changes not working since update

by Igor Stasenko

after updating pharo core image (Update #12220), the list of changes is just one: 'Unnamed', also, it was empty once i tried to check what changes i did to image, after some coding. Once i created a new changeset, and changed few things, these changes recorded properly in new changeset -- Best regards, Igor Stasenko AKA sig.

Oct. 31, 2010

Re: [Pharo-project] [OffTopoc] Symbol understands value: nice hehehehehhe

by Andres Valloud

I like the idea of using fooValue: instead of value:. On 10/30/10 14:15 , Tudor Girba wrote: > We use this pattern in Mondrian scripts, Glamour scripts, and in Moose scripts for navigating models. > > However, we are most of the times doing it with other Symbol selectors. For example: > - in Mondrian, we use moValue: > - in Glamour, we use glamourValue: > > Using dedicated extensions enable us to control the kinds of semantics we want in the scripting. For example, the glamourValue: is different from moValue:. > > Cheers, > Doru > > > On 30 Oct 2010, at 22:56, Andres Valloud wrote: > >> Mariano, >> >> On 10/30/10 13:14 , Mariano Martinez Peck wrote: >> >>> 100% agree. It was just funny for me, how could I do that, just >>> implementing Synbol>> value: >>> Just something curious and funny. Not to really use it. >> >> I agree with this, polymorphism is awesome. For instance, something I did with Assessments was to make objects polymorphic with classes. This device allows Assessments to run SUnit tests without needing to touch any of the test case classes (you can just create pseudo-classes that pretend to be the classes you need but can't have). And you get to implement #new on the instance side :). >> >> Andres. >> > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > > . >

Oct. 30, 2010

Re: [Pharo-project] [OffTopoc] Symbol understands value: nice hehehehehhe

by Tudor Girba

We use this pattern in Mondrian scripts, Glamour scripts, and in Moose scripts for navigating models. However, we are most of the times doing it with other Symbol selectors. For example: - in Mondrian, we use moValue: - in Glamour, we use glamourValue: Using dedicated extensions enable us to control the kinds of semantics we want in the scripting. For example, the glamourValue: is different from moValue:. Cheers, Doru On 30 Oct 2010, at 22:56, Andres Valloud wrote: > Mariano, > > On 10/30/10 13:14 , Mariano Martinez Peck wrote: > >> 100% agree. It was just funny for me, how could I do that, just >> implementing Synbol >> value: >> Just something curious and funny. Not to really use it. > > I agree with this, polymorphism is awesome. For instance, something I did with Assessments was to make objects polymorphic with classes. This device allows Assessments to run SUnit tests without needing to touch any of the test case classes (you can just create pseudo-classes that pretend to be the classes you need but can't have). And you get to implement #new on the instance side :). > > Andres. > -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Oct. 30, 2010

Re: [Pharo-project] [OffTopoc] Symbol understands value: nice hehehehehhe

by Andres Valloud

Mariano, On 10/30/10 13:14 , Mariano Martinez Peck wrote: > 100% agree. It was just funny for me, how could I do that, just > implementing Synbol >> value: > Just something curious and funny. Not to really use it. I agree with this, polymorphism is awesome. For instance, something I did with Assessments was to make objects polymorphic with classes. This device allows Assessments to run SUnit tests without needing to touch any of the test case classes (you can just create pseudo-classes that pretend to be the classes you need but can't have). And you get to implement #new on the instance side :). Andres.

Oct. 30, 2010