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

Re: [Pharo-project] 'foo' asTime

by Johan Brichau

On 26 Aug 2010, at 04:47, Guillermo Polito wrote: > And now, because of fixing Integer>>readFrom:, 'foo' asTime throws an exception and we all are a bit happier :D. Indeed. thanks. And just to make sure that we keep being happy, I added some unit tests to verify that in the KernelTests package ;-) Johan

Aug. 26, 2010

Re: [Pharo-project] Hudson Question

by Sven Van Caekenberghe

Hey Lukas, On 26 Aug 2010, at 13:47, Lukas Renggli wrote: > And what is more, I will demonstrate that stuff at ESUG in the Agile Seaside session :-) Sadly I won't be attending, but I am sure we'll meet one day in person. I just went over the scripts and once again, this is really incredible stuff. You are really a very gifted developer. Everything you write is so beautiful, elegant and clean that it looks deceivingly simple. Seeing this kind of Smalltalk code is really a motivation for me! Thanks again for sharing all this so generously, Sven

Aug. 26, 2010

Re: [Pharo-project] Hudson Question

by Lukas Renggli

And what is more, I will demonstrate that stuff at ESUG in the Agile Seaside session :-) Lukas On 26 August 2010 13:47, Lukas Renggli <renggli(a)gmail.com> wrote: > Btw, the variable $DOWNLOAD is defined as a build parameter and > defaults to the nice Pharo URL > "http://pharo-project.org/pharo-download/stable-core". > > Lukas > > On 26 August 2010 13:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> Thanks a lot, Lukas ! >> >> On 26 Aug 2010, at 13:26, Lukas Renggli wrote: >> >>> Below the Hudson Build Configurations for the images you mentioned: >>> >>> === Pharo === >>> >>> mkdir -p "download" >>> curl --silent --location "$DOWNLOAD" > "download.zip" >>> >>> unzip -p "download.zip" "*/*.image" > "download/download.image" >>> unzip -p "download.zip" "*/*.changes" > "download/download.changes" >>> >>> build-resize.sh download 1280 800 >>> >>> build.sh -i download -s settings -s killtests -o pharo >>> build.sh -i download -s settings -s testrunner -s runalltests -o pharo-test >>> >>> rm -rf download >>> rm download.zip >>> >>> === Development === >>> >>> build.sh -i pharo -s omnibrowser -o omnibrowser >>> build.sh -i omnibrowser -s testrunner -s omnibrowser-tests -o omnibrowser-tests >>> >>> build-oneclick.sh -i omnibrowser -o Pharo-OneClick -n Pharo -t "Pharo >>> Development" -v 1.1 -c Pharo >>> >>> === Seaside 3.0 === >>> >>> build.sh -i omnibrowser -s seaside3 -s seaside3-komanche -s >>> seaside-design -o seaside3 >>> build.sh -i seaside3 -s testrunner -s seaside3-tests -o seaside3-tests >>> build.sh -i seaside3 -s seaside3-swazoo -o seaside3-swazoo >>> >>> build-oneclick.sh -i seaside3 -o Seaside-3.0-OneClick -n Seaside -t >>> Seaside -v 3.0 -c Seaside >>> >>> On 26 August 2010 12:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >>>> >>>> On 26 Aug 2010, at 12:08, Lukas Renggli wrote: >>>> >>>>>> If I click on a artifact, say Seaside 3.0, is it then somehow possible to see the actual build script that was used ? >>>>> >>>>> The build script deletes it after a successful build. Maybe the script >>>>> should be left there? >>>>> >>>>>> I know about your github builder repository, and I learned a lot from it, but the scripts their do not seem to match 100%, or do they ? >>>>> >>>>> Yeah, they should match 100%. >>>>> >>>>> However note that I don't build images from scratch all the time, but >>>>> they build on top of each other: >>>>> >>>>> Pharo --> Development --> Seaside 3 --> Magritte 2 --> Pier 2 >>>>> Â Â Â Â Â Â Â Â Â Â Â Â \--> Seaside 2 --> Magritte --> Pier >>>>> Â Â Â Â Â Â Â Â Â Â Â Â \--> PetitParser >>>>> Â Â Â Â Â Â Â Â Â Â Â Â ... >>>>> >>>>> Lukas >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> www.lukas-renggli.ch >>>> >>>> Well, I am looking at the scripts in the git repo. >>>> There seems to be no script for Pharo (I guess you download core and run the tests). >>>> There seems to be no script for Development. >>>> I guess that Seaside 3.0 is seaside3.st + seaside3-komanche.st, but I am not sure. >>>> >>>> I would like to try to build these myself (not that the ones from Hudson are bad, I just want to learn from this). >>>> >>>> Sven >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

Aug. 26, 2010

Re: [Pharo-project] Hudson Question

by Lukas Renggli

Btw, the variable $DOWNLOAD is defined as a build parameter and defaults to the nice Pharo URL "http://pharo-project.org/pharo-download/stable-core". Lukas On 26 August 2010 13:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Thanks a lot, Lukas ! > > On 26 Aug 2010, at 13:26, Lukas Renggli wrote: > >> Below the Hudson Build Configurations for the images you mentioned: >> >> === Pharo === >> >> mkdir -p "download" >> curl --silent --location "$DOWNLOAD" > "download.zip" >> >> unzip -p "download.zip" "*/*.image" > "download/download.image" >> unzip -p "download.zip" "*/*.changes" > "download/download.changes" >> >> build-resize.sh download 1280 800 >> >> build.sh -i download -s settings -s killtests -o pharo >> build.sh -i download -s settings -s testrunner -s runalltests -o pharo-test >> >> rm -rf download >> rm download.zip >> >> === Development === >> >> build.sh -i pharo -s omnibrowser -o omnibrowser >> build.sh -i omnibrowser -s testrunner -s omnibrowser-tests -o omnibrowser-tests >> >> build-oneclick.sh -i omnibrowser -o Pharo-OneClick -n Pharo -t "Pharo >> Development" -v 1.1 -c Pharo >> >> === Seaside 3.0 === >> >> build.sh -i omnibrowser -s seaside3 -s seaside3-komanche -s >> seaside-design -o seaside3 >> build.sh -i seaside3 -s testrunner -s seaside3-tests -o seaside3-tests >> build.sh -i seaside3 -s seaside3-swazoo -o seaside3-swazoo >> >> build-oneclick.sh -i seaside3 -o Seaside-3.0-OneClick -n Seaside -t >> Seaside -v 3.0 -c Seaside >> >> On 26 August 2010 12:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >>> >>> On 26 Aug 2010, at 12:08, Lukas Renggli wrote: >>> >>>>> If I click on a artifact, say Seaside 3.0, is it then somehow possible to see the actual build script that was used ? >>>> >>>> The build script deletes it after a successful build. Maybe the script >>>> should be left there? >>>> >>>>> I know about your github builder repository, and I learned a lot from it, but the scripts their do not seem to match 100%, or do they ? >>>> >>>> Yeah, they should match 100%. >>>> >>>> However note that I don't build images from scratch all the time, but >>>> they build on top of each other: >>>> >>>> Pharo --> Development --> Seaside 3 --> Magritte 2 --> Pier 2 >>>> Â Â Â Â Â Â Â Â Â Â Â Â \--> Seaside 2 --> Magritte --> Pier >>>> Â Â Â Â Â Â Â Â Â Â Â Â \--> PetitParser >>>> Â Â Â Â Â Â Â Â Â Â Â Â ... >>>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>> >>> Well, I am looking at the scripts in the git repo. >>> There seems to be no script for Pharo (I guess you download core and run the tests). >>> There seems to be no script for Development. >>> I guess that Seaside 3.0 is seaside3.st + seaside3-komanche.st, but I am not sure. >>> >>> I would like to try to build these myself (not that the ones from Hudson are bad, I just want to learn from this). >>> >>> Sven >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Aug. 26, 2010

[Pharo-project] hasInstanceVariableNamed: hasClassVariableNamed:

by StÃ©phane Ducasse

Hi guys is it me or we are missing some cool and simple methods like hasInstanceVariableNamed: hasClassVariableNamed: ? Stef

Aug. 26, 2010

Re: [Pharo-project] Hudson Question

by Sven Van Caekenberghe

Thanks a lot, Lukas ! On 26 Aug 2010, at 13:26, Lukas Renggli wrote: > Below the Hudson Build Configurations for the images you mentioned: > > === Pharo === > > mkdir -p "download" > curl --silent --location "$DOWNLOAD" > "download.zip" > > unzip -p "download.zip" "*/*.image" > "download/download.image" > unzip -p "download.zip" "*/*.changes" > "download/download.changes" > > build-resize.sh download 1280 800 > > build.sh -i download -s settings -s killtests -o pharo > build.sh -i download -s settings -s testrunner -s runalltests -o pharo-test > > rm -rf download > rm download.zip > > === Development === > > build.sh -i pharo -s omnibrowser -o omnibrowser > build.sh -i omnibrowser -s testrunner -s omnibrowser-tests -o omnibrowser-tests > > build-oneclick.sh -i omnibrowser -o Pharo-OneClick -n Pharo -t "Pharo > Development" -v 1.1 -c Pharo > > === Seaside 3.0 === > > build.sh -i omnibrowser -s seaside3 -s seaside3-komanche -s > seaside-design -o seaside3 > build.sh -i seaside3 -s testrunner -s seaside3-tests -o seaside3-tests > build.sh -i seaside3 -s seaside3-swazoo -o seaside3-swazoo > > build-oneclick.sh -i seaside3 -o Seaside-3.0-OneClick -n Seaside -t > Seaside -v 3.0 -c Seaside > > On 26 August 2010 12:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> >> On 26 Aug 2010, at 12:08, Lukas Renggli wrote: >> >>>> If I click on a artifact, say Seaside 3.0, is it then somehow possible to see the actual build script that was used ? >>> >>> The build script deletes it after a successful build. Maybe the script >>> should be left there? >>> >>>> I know about your github builder repository, and I learned a lot from it, but the scripts their do not seem to match 100%, or do they ? >>> >>> Yeah, they should match 100%. >>> >>> However note that I don't build images from scratch all the time, but >>> they build on top of each other: >>> >>> Pharo --> Development --> Seaside 3 --> Magritte 2 --> Pier 2 >>> \--> Seaside 2 --> Magritte --> Pier >>> \--> PetitParser >>> ... >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >> >> Well, I am looking at the scripts in the git repo. >> There seems to be no script for Pharo (I guess you download core and run the tests). >> There seems to be no script for Development. >> I guess that Seaside 3.0 is seaside3.st + seaside3-komanche.st, but I am not sure. >> >> I would like to try to build these myself (not that the ones from Hudson are bad, I just want to learn from this). >> >> Sven > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 26, 2010

Re: [Pharo-project] Why is Stack extending from LinkedList?

by Lukas Renggli

I wonder why there is the need for a stack class at all? OrderedCollection is the class designed to do Stacks and Queues efficiently and portably, see #addFirst:, #addLast:, #first, #last, #removeFirst, #removeLast. Lukas 2010/8/26 Bart Gauquie <bart.gauquie(a)gmail.com>: > Hi list, > > is there a specific reason Stack is extending from LinkedList, instead of > using a LinkedList internally? > To me, it seems that the protocol that LinkedList, SequenceableCollection, > ... provides is not the protocol you expect from a Stack? > > Any thoughts on this? > > Kind regards, > > Bart > > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The important thing > is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - Albert > Einstein > However beautiful the strategy, you should occasionally look at the results. > - Sir Winston Churchill > It's not enough that we do our best; sometimes we have to do what's > required. - Sir Winston Churchill > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Aug. 26, 2010

Re: [Pharo-project] Hudson Question

by Lukas Renggli

Below the Hudson Build Configurations for the images you mentioned: === Pharo === mkdir -p "download" curl --silent --location "$DOWNLOAD" > "download.zip" unzip -p "download.zip" "*/*.image" > "download/download.image" unzip -p "download.zip" "*/*.changes" > "download/download.changes" build-resize.sh download 1280 800 build.sh -i download -s settings -s killtests -o pharo build.sh -i download -s settings -s testrunner -s runalltests -o pharo-test rm -rf download rm download.zip === Development === build.sh -i pharo -s omnibrowser -o omnibrowser build.sh -i omnibrowser -s testrunner -s omnibrowser-tests -o omnibrowser-tests build-oneclick.sh -i omnibrowser -o Pharo-OneClick -n Pharo -t "Pharo Development" -v 1.1 -c Pharo === Seaside 3.0 === build.sh -i omnibrowser -s seaside3 -s seaside3-komanche -s seaside-design -o seaside3 build.sh -i seaside3 -s testrunner -s seaside3-tests -o seaside3-tests build.sh -i seaside3 -s seaside3-swazoo -o seaside3-swazoo build-oneclick.sh -i seaside3 -o Seaside-3.0-OneClick -n Seaside -t Seaside -v 3.0 -c Seaside On 26 August 2010 12:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 26 Aug 2010, at 12:08, Lukas Renggli wrote: > >>> If I click on a artifact, say Seaside 3.0, is it then somehow possible to see the actual build script that was used ? >> >> The build script deletes it after a successful build. Maybe the script >> should be left there? >> >>> I know about your github builder repository, and I learned a lot from it, but the scripts their do not seem to match 100%, or do they ? >> >> Yeah, they should match 100%. >> >> However note that I don't build images from scratch all the time, but >> they build on top of each other: >> >> Pharo --> Development --> Seaside 3 --> Magritte 2 --> Pier 2 >> Â Â Â Â Â Â Â Â Â Â Â Â \--> Seaside 2 --> Magritte --> Pier >> Â Â Â Â Â Â Â Â Â Â Â Â \--> PetitParser >> Â Â Â Â Â Â Â Â Â Â Â Â ... >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch > > Well, I am looking at the scripts in the git repo. > There seems to be no script for Pharo (I guess you download core and run the tests). > There seems to be no script for Development. > I guess that Seaside 3.0 is seaside3.st + seaside3-komanche.st, but I am not sure. > > I would like to try to build these myself (not that the ones from Hudson are bad, I just want to learn from this). > > Sven > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 26, 2010

Re: [Pharo-project] DNU after updating 1.2 core image

by Henrik Johansen

The old lines methods was part of Nicolas' effort to provide an api that handled all kinds of lineEndings though. I'd rather it be restored to the original: lines "Answer an array of lines composing this receiver without the line ending delimiters" ^Array new: (self size // 60 max: 16) streamContents: [:lines | self linesDo: [:aLine | lines nextPut: aLine]] Cheers, Henry Den 26.08.2010 12:48, skrev Marcus Denker: > > On Aug 26, 2010, at 5:45 AM, Guillermo Polito wrote: > >> When you right click over the category panel and the method category >> panel in the system browser. >> >> ByteString DNU lines >> >> > > If you add > > lines > ^self findTokens: String cr > > to String it works again... I guess that got somehow lost. > > I will add a bug tracker entry. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de <http://www.marcusdenker.de/> > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 26, 2010

Re: [Pharo-project] DNU after updating 1.2 core image

by Marcus Denker

On Aug 26, 2010, at 5:45 AM, Guillermo Polito wrote: > When you right click over the category panel and the method category panel in the system browser. > > ByteString DNU lines > > If you add lines ^self findTokens: String cr to String it works again... I guess that got somehow lost. I will add a bug tracker entry. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 26, 2010