March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo 1.2 and test failures

by Otto Behrens

> I think there is no magic here. If you want daily build images, then you > have 2 options: > > 1) Always use ALL last version of everything > 2) Use last metacello version. Someone needs to update each configuration. > > 3) copy a fixed set of mczs to a repository and use the baseline > I thought that all mczs are copied to a let's say pharo 1.2 repository. In > this case you don't need metacello versions because it loads the newest > version which is always true. Well, it is always true if integrating fixes > means that the changed package is put into that specific repository. But it > doesn't seem to be like that so I have to read it again :) If the packages > are taken from their own repositories than I don't see another way than to > nail the version in the metacello config and update as soon as a package is > updated. A tool like the browser will ease this step. > Norbert +1 for option 3) This also helps when a repository is down.

March 11, 2011

[Pharo-project] how I am supposed to load Spy?

by Mariano Martinez Peck

ConfigurationOfSpy load gives me 'No version found for ''default'' of ConfigurationOfMemoryMonitor' I tried both, from Spy and MetacelloRepository. thanks mariano

March 11, 2011

Re: [Pharo-project] Issue 3136 in pharo: Explicit ordering of submorphs, when computing the new layout

by pharo＠googlecode.com

Updates: Status: Invalid Comment #4 on issue 3136 by marcus.d...(a)gmail.com: Explicit ordering of submorphs, when computing the new layout http://code.google.com/p/pharo/issues/detail?id=3136 (No comment was entered for this change.)

March 11, 2011

Re: [Pharo-project] Issue 3136 in pharo: Explicit ordering of submorphs, when computing the new layout

by pharo＠googlecode.com

Comment #3 on issue 3136 by fernando...(a)gmail.com: Explicit ordering of submorphs, when computing the new layout http://code.google.com/p/pharo/issues/detail?id=3136 Please close this issue, since the ordering is already handled by the morphic layers.

March 11, 2011

Re: [Pharo-project] [COTDC] 29 - EventSensorConstants

by StÃ©phane Ducasse

:) Yes I have a plan for you :) >>> This is a constants, used by EventSensor to identify various event >>> types and theirs contents. >>> NOTE: A constant values should be kept in sync with VM-side, which are >>> defined in sq.h header file. >>> >> >> IE I am more "InputEventConstants" than "EventSensorConstants" really. (All are related to the events passed from the vm themselves, not the sensor) >> >> Funnily enough, EventSensorConstants (MouseButtonBit 2r0010, correct preswap), MouseEvent (#blueButtonPressed mask: 2r0001, correct postswap, if swapped), and the InputEventSensor (#blueButtonPressed mask: 2r0111, ie, ANY of the buttons pressed) all disagree on what the blue button bit is actually supposed to be. :P >> > > yeah.. so, who is brave enough and have time to rewrite/improve event > system? Ask Stephane. He has a plan for you :) > >> Cheers, >> Henry >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

March 11, 2011

Re: [Pharo-project] petitparser

by Tudor Girba

Hi Noury, On 11 Mar 2011, at 06:48, Noury Bouraqadi wrote: > Hi Doru, > > Thanx for your great tutorial! For those who had not the chance to attend, I believe that the video will be available some time in the future. Thanks :) > Talks were recorded indeed. > > Doru, could organize a hands on session this afternoon on Glamour. Is that a question? :) But, yes, I would be ready to do one. Cheers, Doru > Noury > On 11 mars 2011, at 00:16, Tudor Girba wrote: > >> Hi, >> >> The slides I used for today's tutorial on PetitParser can be found here: >> http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… >> >> Cheers, >> Doru >> >> >> >> On 10 Mar 2011, at 12:39, Tudor Girba wrote: >> >>> Hi, >>> >>> To participate in the PetitParser tutorial to take place this afternoon at the Deep into Smalltalk school, you should: >>> - find one or two partners to code with, and >>> - download the latest Moose image containing PetitParser: >>> http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Value is always contextual." >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "What is more important: To be happy, or to make happy?" >> >> > > Noury Bouraqadi > http://car.mines-douai.fr/noury > -- > -6th National Conference on > âControl Architecture of Robotsâ > 24-25 may 2011, Grenoble area, France > http://car2011.inrialpes.fr/ > > -19th ESUG International Smalltalk Conference > 22-26 August 2011, Edinburgh, UK > http://www.esug.org/Conferences/2011 > > -19Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ11) > http://www.univ-valenciennes.fr/congres/jfsma2011/ > 17-19 Octobre 2011, Valenciennes, France > > > > > -- www.tudorgirba.com "Obvious things are difficult to teach."

March 11, 2011

Re: [Pharo-project] petitparser

by Noury Bouraqadi

Hi Doru, Thanx for your great tutorial! For those who had not the chance to attend, I believe that the video will be available some time in the future. Talks were recorded indeed. Doru, could organize a hands on session this afternoon on Glamour. Noury On 11 mars 2011, at 00:16, Tudor Girba wrote: > Hi, > > The slides I used for today's tutorial on PetitParser can be found here: > http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… > > Cheers, > Doru > > > > On 10 Mar 2011, at 12:39, Tudor Girba wrote: > >> Hi, >> >> To participate in the PetitParser tutorial to take place this afternoon at the Deep into Smalltalk school, you should: >> - find one or two partners to code with, and >> - download the latest Moose image containing PetitParser: >> http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Value is always contextual." >> >> >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > Noury Bouraqadi http://car.mines-douai.fr/noury -- -6th National Conference on âControl Architecture of Robotsâ 24-25 may 2011, Grenoble area, France http://car2011.inrialpes.fr/ -19th ESUG International Smalltalk Conference 22-26 August 2011, Edinburgh, UK http://www.esug.org/Conferences/2011 -19Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ11) http://www.univ-valenciennes.fr/congres/jfsma2011/ 17-19 Octobre 2011, Valenciennes, France

March 11, 2011

Re: [Pharo-project] [COTDC] 29 - EventSensorConstants

by Igor Stasenko

On 11 March 2011 00:11, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On Mar 10, 2011, at 10:48 52PM, Igor Stasenko wrote: > >> This is a constants, used by EventSensor to identify various event >> types and theirs contents. >> NOTE: A constant values should be kept in sync with VM-side, which are >> defined in sq.h header file. >> > > IE I am more "InputEventConstants" than "EventSensorConstants" really. (All are related to the events passed from the vm themselves, not the sensor) > > Funnily enough, EventSensorConstants Â (MouseButtonBit Â 2r0010, correct preswap), MouseEvent (#blueButtonPressed mask: 2r0001, correct postswap, if swapped), and the InputEventSensor (#blueButtonPressed mask: 2r0111, ie, ANY of the buttons pressed) all disagree on what the blue button bit is actually supposed to be. :P > yeah.. so, who is brave enough and have time to rewrite/improve event system? Ask Stephane. He has a plan for you :) > Cheers, > Henry > -- Best regards, Igor Stasenko AKA sig.

March 10, 2011

[Pharo-project] [ANN] Cog issue tracker

by Igor Stasenko

Hello everyone. Without much debate we just created it at [1]. Now there is a separate place for filing issues for Cog VM. I think Cog deserves separate issue tracker, because currently all reports and problems are mainly buried in vm-dev mailing list, and it is hard to tell what is status of one or another issue, which we lately discovered. And such approach definitely won't scale. So, it was a main reason for making this move. Lets help Eliot (and others who involved in development) make activities to be more organized and visible. I'd like to stress that there is nothing inside code.google in particular, which could make its issue tracker serve our needs well. It will work well only if we, as community, organize ourselves and pay attention to collect and put important information there, make it easily accessible, structured and so on.. [1] http://code.google.com/p/cog/ -- Best regards, Igor Stasenko AKA sig.

March 10, 2011

Re: [Pharo-project] petitparser

by Tudor Girba

Hi, The slides I used for today's tutorial on PetitParser can be found here: http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… Cheers, Doru On 10 Mar 2011, at 12:39, Tudor Girba wrote: > Hi, > > To participate in the PetitParser tutorial to take place this afternoon at the Deep into Smalltalk school, you should: > - find one or two partners to code with, and > - download the latest Moose image containing PetitParser: > http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Value is always contextual." > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

March 10, 2011