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

[Pharo-project] A thought about Morphic and Seaside

by StÃ©phane Ducasse

Hello guys We were browsing code with marcus and I realized something quite funny about Morphic. Morphic is somehow close to seaside for the following point: There is a list that contains the children. In Seaside you have to return a list containing the children components too. Now this is really interesting to see that a lot of complexity in Morphic code comes from the fact that the programmers avoided to have an instance variable for an element to the pretext that the element was already in the submorphs list. Then you end up with code like label: aString | oldLabel m | (oldLabel := self findA: StringMorph) ifNotNil: [oldLabel delete]. m := StringMorph contents: aString font: TextStyle defaultFont. self extent: m extent + (borderWidth + 6). m position: self center - (m extent // 2). self addMorph: m. m lock label | s | s := ''. self allMorphsDo: [:m | (m isKindOf: StringMorph) ifTrue: [s := m contents]]. ^ s instead of label ^ label label: aString .... where you have to query the submorph of the right kind.... Marcus was mentioning to me that Morphic is a bit like applying GraphTraversal that the law of demeter guy loves so much. And we see the results, an ugly code all over the places. So I will certainly play a bit with this design difference to see what it makes. But I'm sure now it makes a big difference. stef

Aug. 17, 2008

Re: [Pharo-project] New update :)

by StÃ©phane Ducasse

Yes we are not yet running the tests before releasing.... On Aug 17, 2008, at 5:20 PM, Adrian Lienhard wrote: > Thanks for the new updates. > There are a few tests that fail. Some are from fixes and cleanups we > did (like the HTML removal); another is that there are again > undeclared vars. I can fix the tests in the coming days. Ok if you do an update use scp -p as mentioned in the class scriptloader comment to preserve the rights. > > > On Aug 15, 2008, at 18:33 , StÃ©phane Ducasse wrote: > >> There is a new update.... >> removing a lot of duplicated code and some fixes. >> >> We also set the preference not to server mode. > > Thats good. I haven't noticed that this was turned on at some point > (maybe inadvertently?). It should only be turned on for production > images as it slows down the GUI.

Aug. 17, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by StÃ©phane Ducasse

Ok I will fix the halt in regex. BTW it would be good to have a continuous test runner on pharo and not pharo-dev On Aug 17, 2008, at 3:59 PM, laurent laffont wrote: > I've made some scripts to automatically run the tests and generate > the reports. More details on > http://www.squeaksource.com/ContIntegration.html in the wiki. > > Briefly, you can automatically download an image archive, install > ContinuousIntegration package run the tests, generate the report and > publish it on a ftp server doing this: > > ncftpput ftp.foo.com www/reports -u me -p secret \ > `squeakci-get https://gforge.inria.fr/frs/download.php/5547/sq3.9.1-7075dev08.08.1.zip > ` > > If there's a tool to generate the pharo image automatically, then > there's not a lot of work remaining to have a basic continuous > integration server. > > However, these two problematic tests must be resolved > (MCPackageTest>>#testUnload {tests} > and RxPaserTest>>#testMatchesInwW) > > Laurent > > On Sun, Aug 17, 2008 at 2:01 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: > Ideally, generating a new report for each new commit in PharoInBox > and Pharo would be great... > > Cheers, > Alexandre > > > On 17 Aug 2008, at 13:23, laurent laffont wrote: > > Hello, > > I've generated a test report for pharo0.1-10050web08.08.1 image: http://www.adhocmusic.net/squeak/pharo0.1-10050web08.08.1.tests.html > > passed: 14475 failures: 44 errors: 83 > > I had to remove this test as it never ends: > MCPackageTest>>#testUnload {tests} > > There's also a halt in RxPaserTest>>#testMatchesInwW > > Is this report useful for you ? Which additional informations would > you like to see in it ? > > Regards, > > -- > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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

Aug. 17, 2008

Re: [Pharo-project] New update :)

by Adrian Lienhard

Thanks for the new updates. There are a few tests that fail. Some are from fixes and cleanups we did (like the HTML removal); another is that there are again undeclared vars. I can fix the tests in the coming days. On Aug 15, 2008, at 18:33 , StÃ©phane Ducasse wrote: > There is a new update.... > removing a lot of duplicated code and some fixes. > > We also set the preference not to server mode. Thats good. I haven't noticed that this was turned on at some point (maybe inadvertently?). It should only be turned on for production images as it slows down the GUI. Adrian

Aug. 17, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by laurent laffont

I've made some scripts to automatically run the tests and generate the reports. More details on http://www.squeaksource.com/ContIntegration.html in the wiki. Briefly, you can automatically download an image archive, install ContinuousIntegration package run the tests, generate the report and publish it on a ftp server doing this: ncftpput ftp.foo.com www/reports -u me -p secret \ `squeakci-get https://gforge.inria.fr/frs/download.php/5547/sq3.9.1-7075dev08.08.1.zip` If there's a tool to generate the pharo image automatically, then there's not a lot of work remaining to have a basic continuous integration server. However, these two problematic tests must be resolved (MCPackageTest>>#testUnload {tests} and RxPaserTest>>#testMatchesInwW) Laurent On Sun, Aug 17, 2008 at 2:01 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Ideally, generating a new report for each new commit in PharoInBox and > Pharo would be great... > > Cheers, > Alexandre > > > On 17 Aug 2008, at 13:23, laurent laffont wrote: > > Hello, >> >> I've generated a test report for pharo0.1-10050web08.08.1 image: >> http://www.adhocmusic.net/squeak/pharo0.1-10050web08.08.1.tests.html >> >> passed: 14475 failures: 44 errors: 83 >> >> I had to remove this test as it never ends: MCPackageTest>>#testUnload >> {tests} >> >> There's also a halt in RxPaserTest>>#testMatchesInwW >> >> Is this report useful for you ? Which additional informations would you >> like to see in it ? >> >> Regards, >> >> -- >> Laurent Laffont >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 17, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by Alexandre Bergel

Ideally, generating a new report for each new commit in PharoInBox and Pharo would be great... Cheers, Alexandre On 17 Aug 2008, at 13:23, laurent laffont wrote: > Hello, > > I've generated a test report for pharo0.1-10050web08.08.1 image: http://www.adhocmusic.net/squeak/pharo0.1-10050web08.08.1.tests.html > > passed: 14475 failures: 44 errors: 83 > > I had to remove this test as it never ends: > MCPackageTest>>#testUnload {tests} > > There's also a halt in RxPaserTest>>#testMatchesInwW > > Is this report useful for you ? Which additional informations would > you like to see in it ? > > Regards, > > -- > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 17, 2008

[Pharo-project] test report for pharo0.1-10050web08.08.1 image

by laurent laffont

Hello, I've generated a test report for pharo0.1-10050web08.08.1 image: http://www.adhocmusic.net/squeak/pharo0.1-10050web08.08.1.tests.html passed: 14475 failures: 44 errors: 83 I had to remove this test as it never ends: MCPackageTest>>#testUnload {tests} There's also a halt in RxPaserTest>>#testMatchesInwW Is this report useful for you ? Which additional informations would you like to see in it ? Regards, -- Laurent Laffont

Aug. 17, 2008

Re: [Pharo-project] automatic in stall

by StÃ©phane Ducasse

I have to change the loader to get the lastest config file, since this version loads an old installer. Stef On Aug 16, 2008, at 11:13 AM, Damien Cassou wrote: > It does not answer your question, but installing Installer is quite > easy on Pharo: > > ScriptLoader new installingInstaller > > On Wed, Aug 13, 2008 at 10:59 PM, Hilaire Fernandes > <hilaire(a)ofset.org> wrote: >> On a bare bone image (Without the class Installer), is it possible to >> install automatically Monticello package. >> >> On a -dev image I use to do: >> >> (Installer monticello http: 'http://www.squeaksource.com/repos' user: >> 'hlsf' password: 'xxx') >> install: 'paquage'. >> >> >> Hilaire >> -- >> http://blog.ofset.org/hilaire >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 17, 2008

Re: [Pharo-project] automatic in stall

by Damien Cassou

It does not answer your question, but installing Installer is quite easy on Pharo: ScriptLoader new installingInstaller On Wed, Aug 13, 2008 at 10:59 PM, Hilaire Fernandes <hilaire(a)ofset.org> wrote: > On a bare bone image (Without the class Installer), is it possible to > install automatically Monticello package. > > On a -dev image I use to do: > > (Installer monticello http: 'http://www.squeaksource.com/repos' user: > 'hlsf' password: 'xxx') > install: 'paquage'. > > > Hilaire > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Aug. 16, 2008

Re: {Spam?} [Pharo-project] [Update] 10055 + new release

by Bill Schwab

Ok, the profiler to the rescue. Instantiating some exception sub-classes should tell us whether there is anything to be gained from a factory of some sort. A quick look does not show much going on on instantiation, so it is probably fine to create the appropriate sub-instance and set any useful aspects, and to pass that to the ouch-block. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029 >>> m.rueger(a)acm.org 8/15/2008 3:48 PM >>> On Fri, Aug 15, 2008 at 8:51 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > I think the answer is probably to pass the *class* of the exception. > The default then simply sends the correct #signalWith: message with the > file name as an argument. Hmm, but the instance might hold additional information. Michael _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 15, 2008