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

Re: [Pharo-project] Sunit Extensions breaking the TestRunner

by StÃ©phane Ducasse

no problem you are right. I can imagine that this is raging seeing us reinventing the wheel. Stef PS: jannik told me that he will report the problems he has with Installer On Nov 10, 2008, at 7:57 PM, Keith Hodges wrote: > I apologize for my previous emails being somewhat brash. I admit > that am > not in the best of spirits having been hit by a firework (no lasting > damage done). > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 10, 2008

Re: [Pharo-project] SUnit extensions and icons OB support

by StÃ©phane Ducasse

Seems like a good idea with a classVariables holding a dict class -> result. Stef On Nov 10, 2008, at 8:26 PM, Alexandre Bergel wrote: > Yes, this is what I intended to do by having the result in the > TestRunner itself. > > Alexandre > > On 10 Nov 2008, at 16:13, StÃ©phane Ducasse wrote: > >> We run all the tests before publishing so this is clearly not >> possible to dirty all the packages. >> >> I think that you should distinguish two cases: >> - you run the tests - but the package should not get dirty else it >> will be totally unmanageable. >> The Browser should keep the data in its model. >> >> - you run the tests and you want to keep the test results so that >> you could >> understand when you load the package back if you made progress. >> >> >> >>> >>> >>>> Yes, this is the case. When you run the test, the result are >>>> stored into the class that has been run. >>>> Maybe we could store them in a location outside the package. But >>>> test results will not be persistent. >>> >>> Yes and no. The package becomes dirty only if the test results >>> change - ie if a test goes from failure to pass for example. >>> >>>> >>>> >>>> Alexandre >>>> >>>> On 10 Nov 2008, at 14:40, StÃ©phane Ducasse wrote: >>>> >>>>> what would be nice if that the packages do not get dirty because >>>>> the tests run. >>>>> I do not know if this is the case but this is important. >>>>> >>>>> On Nov 10, 2008, at 4:58 PM, Alexandre Bergel wrote: >>>>> >>>>>> I have seen this. We should continue this discussion offline, >>>>>> then propose a robust and stable version to the pharo community. >>>>>> >>>>>> Cheers, >>>>>> Alexandre >>>>>> >>>>>> >>>>>> On 10 Nov 2008, at 12:53, Simon Denier wrote: >>>>>> >>>>>>> >>>>>>> On 10 nov. 08, at 11:07, David RÃ¶thlisberger wrote: >>>>>>> >>>>>>>> >>>>>>>>> So let me know when I can load again and integrate your >>>>>>>>> extension. >>>>>>>> >>>>>>>> Could you please check with SUnit-DavidRoethlisberger.42 in http://www.squeaksource.com/Pharo >>>>>>>> and execute ScriptLoader class >> loadOB? >>>>>>> >>>>>>> It is not enough >>>>>>> >>>>>>> Starting from a fresh 10144 image, loading OB with >>>>>>> scriptloader, then your latest commit for sunit, I do get the >>>>>>> icons in the browser, but cant update their state: not lastRun >>>>>>> method is generated and it fails when I try to save the >>>>>>> results in the TestRunner. Best guess: the code generating >>>>>>> lastRun on the class side is lost. >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Then after it would be great to have a button to run the >>>>>>>>> tests and >>>>>>>> >>>>>>>> yes, we should have something like that in the browser. >>>>>>>> >>>>>>>> David >>>>>>>> >>>>>>>> >>>>>>>>>> Hi Stef, >>>>>>>>>> >>>>>>>>>> as you as the SUnit extensions are integrated, you just >>>>>>>>>> need to load OB. Any OB load method in ScriptLoader can be >>>>>>>>>> used for this as this extension is also in the stable OB >>>>>>>>>> version now. >>>>>>>>>> >>>>>>>>>> David >>>>>>>>>> >>>>>>>>>>> can you tell me what I should do to get the icons showing >>>>>>>>>>> the status of tests in your browser? >>>>>>>>>>> I should harvest the Sunit extensions and then? >>>>>>>>>>> Stef >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Simon >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> 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 >>>> >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

Nov. 10, 2008

Re: [Pharo-project] New pharo-dev based on latest version

by StÃ©phane Ducasse

igor with upatde 10144 I cannot reproduce the first bug > - open world menu System->About. Now instead of clicking Ok, try drag > the window. Leads to DNU when you release a mouse button. Do you see it on 10144 or only pharo-dev? > > > - a submenu gradient in OB (maybe not only in OB) is sporadically > loses its colors: > when you first open a context menu, and first open a submenu in it, > all is drawn ok. But then try hover over different menu items to force > hiding/showing submenus, you will notice that newly opened submenus > start losing gradient background, until finally background becomes > completely white. > > 2008/11/10 Damien Cassou <damien.cassou(a)gmail.com>: >> http://gforge.inria.fr/frs/download.php/10931/pharo0.1-10142dev08.11.2.zip >> >> always available at: http://code.google.com/p/pharo/wiki/Downloads?tm=2 >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 10, 2008

[Pharo-project] Re: [squeak-dev] ANN Rio now supports ftp

by Keith Hodges

Rio has now been refactored so as to be cleaner and to avoid any such tricks as doesNotUnderstand: best regards Keith > *News:* > > Rio has finally made it to (roughly) where it was planned to be all along. > File manipulations that work locally should now also work remotely. > > e.g. > > dir := 'ftp://squeak:viewpoints@squeak.warwick.st/test/test/test' > asRio mkpath. > file := dir / 'hello.txt' contents: 'hello world'. > > next := file rename nextVersion. > next name. { hello.1.txt } > next fileSize. {11} > > next copyTo: 'local.txt' > > *Limitations:* > > Although you can obtain read or writeStreams directly into the remote > file, it is not random access (yet?) > therefore you cant currently write directly to the write stream of a > remote gzip file (which you can do locally) > > *More Info:* > > http://wiki.squeak.org/squeak/5929 > > cheers > > Keith > ------------------------------------------------------------------------ > > >

Nov. 10, 2008

Re: [Pharo-project] SUnit extensions and icons OB support

by Keith Hodges

Alexandre Bergel wrote: > Yes, this is what I intended to do by having the result in the > TestRunner itself. > > Alexandre But there is more than one TestRunner. Keith

Nov. 10, 2008

Re: [Pharo-project] SUnit extensions and icons OB support

by Keith Hodges

Alexandre Bergel wrote: > Yes, this is the case. When you run the test, the result are stored > into the class that has been run. > Maybe we could store them in a location outside the package. But test > results will not be persistent. > > > Alexandre Do you mean, perhaps store them in a class variable, perhaps in a specialized version of TestResult? In Installer ss project: 'Testing'; install: 'SUnit'. there is a class TestResultTimed, which is used by the test runners to time tests, measure their use of the network and Store the results of the last run, so that you can sort, or tag them etc. Keith

Nov. 10, 2008

Re: [Pharo-project] SUnit extensions and icons OB support

by Alexandre Bergel

Yes, this is what I intended to do by having the result in the TestRunner itself. Alexandre On 10 Nov 2008, at 16:13, StÃ©phane Ducasse wrote: > We run all the tests before publishing so this is clearly not > possible to dirty all the packages. > > I think that you should distinguish two cases: > - you run the tests - but the package should not get dirty else it > will be totally unmanageable. > The Browser should keep the data in its model. > > - you run the tests and you want to keep the test results so that > you could > understand when you load the package back if you made progress. > > > >> >> >>> Yes, this is the case. When you run the test, the result are >>> stored into the class that has been run. >>> Maybe we could store them in a location outside the package. But >>> test results will not be persistent. >> >> Yes and no. The package becomes dirty only if the test results >> change - ie if a test goes from failure to pass for example. >> >>> >>> >>> Alexandre >>> >>> On 10 Nov 2008, at 14:40, StÃ©phane Ducasse wrote: >>> >>>> what would be nice if that the packages do not get dirty because >>>> the tests run. >>>> I do not know if this is the case but this is important. >>>> >>>> On Nov 10, 2008, at 4:58 PM, Alexandre Bergel wrote: >>>> >>>>> I have seen this. We should continue this discussion offline, >>>>> then propose a robust and stable version to the pharo community. >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> >>>>> On 10 Nov 2008, at 12:53, Simon Denier wrote: >>>>> >>>>>> >>>>>> On 10 nov. 08, at 11:07, David RÃ¶thlisberger wrote: >>>>>> >>>>>>> >>>>>>>> So let me know when I can load again and integrate your >>>>>>>> extension. >>>>>>> >>>>>>> Could you please check with SUnit-DavidRoethlisberger.42 in http://www.squeaksource.com/Pharo >>>>>>> and execute ScriptLoader class >> loadOB? >>>>>> >>>>>> It is not enough >>>>>> >>>>>> Starting from a fresh 10144 image, loading OB with >>>>>> scriptloader, then your latest commit for sunit, I do get the >>>>>> icons in the browser, but cant update their state: not lastRun >>>>>> method is generated and it fails when I try to save the results >>>>>> in the TestRunner. Best guess: the code generating lastRun on >>>>>> the class side is lost. >>>>>> >>>>>>> >>>>>>> >>>>>>>> Then after it would be great to have a button to run the >>>>>>>> tests and >>>>>>> >>>>>>> yes, we should have something like that in the browser. >>>>>>> >>>>>>> David >>>>>>> >>>>>>> >>>>>>>>> Hi Stef, >>>>>>>>> >>>>>>>>> as you as the SUnit extensions are integrated, you just need >>>>>>>>> to load OB. Any OB load method in ScriptLoader can be used >>>>>>>>> for this as this extension is also in the stable OB version >>>>>>>>> now. >>>>>>>>> >>>>>>>>> David >>>>>>>>> >>>>>>>>>> can you tell me what I should do to get the icons showing >>>>>>>>>> the status of tests in your browser? >>>>>>>>>> I should harvest the Sunit extensions and then? >>>>>>>>>> Stef >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> -- >>>>>> Simon >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> 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 >>> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 10, 2008

Re: [Pharo-project] Sunit Extensions breaking the TestRunner

by Alexandre Bergel

>> The solution for SUnit is for those who are interested in improving >> SUnit to actually TALK to others who have been already doing the >> same, >> and to collaborate on one such SUnit-improved rather than 10 >> separate ones! > > True. Alex told me that he will have a look at your extensions. > So he will I'm sure. Yes, I will have a look at it. But nothing Rome was not made in one day... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 10, 2008

Re: [Pharo-project] Sunit Extensions breaking the TestRunner

by StÃ©phane Ducasse

>>>>>> >> > As an alternative users A and B can club together and make a package > called C-extras, which avoids the problem of overrides clashing. > > This is exactly the situation we have with Seaside, package > maintainers > refusing to add even simple accessors, so... Seaside28Jetsam was > created > as "Seaside-Extras". > > This is exactly the role of the Kernel-Extensions package (not that it > includes many overrides). Several have turned their noses up at > Kernel-Extensions because it includes things that they dont > necessarily > like, keith may I say that this is not productive to bash us systematically. We did a report on Kernel Extensions and we will certainly harvest some of the extensions. Now if nobody beside me look at it, then it will end up on my long stack and so far I'm quite busy. > but in the process you are pooring scorn on a social process of > collecting all extensions in a managed place where collisions can be > avoided. > > Taking this on board... a package developer could recognise that > perhaps > they haven't got it all right and recognise a need to harness and > guide > such extras. Thus encouraging users of their package to collaborate in > order to make the extras well documented and worthy of inclusion into > future releases of the main package. > > Presently, the culture of "overrides are evil" is maintained because > of > the danger of clashes as Igor explained. But they dont have to be evil > if they are managed in a social collaborative process which avoids > such > collisions, i.e. Seaside28Jetsam, and KernelExtensions. Those who > write > the packages can pronounce the doctrine of "overrides are evil", > because > they are not forced to use them, however those of us who want to > actually. Overrides are still something that we should avoid as much as possible. > The solution for SUnit is for those who are interested in improving > SUnit to actually TALK to others who have been already doing the same, > and to collaborate on one such SUnit-improved rather than 10 > separate ones! True. Alex told me that he will have a look at your extensions. So he will I'm sure. Stef > > > regards > > Keith > > > > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 10, 2008

Re: [Pharo-project] SUnit extensions and icons OB support

by StÃ©phane Ducasse

We run all the tests before publishing so this is clearly not possible to dirty all the packages. I think that you should distinguish two cases: - you run the tests - but the package should not get dirty else it will be totally unmanageable. The Browser should keep the data in its model. - you run the tests and you want to keep the test results so that you could understand when you load the package back if you made progress. > > >> Yes, this is the case. When you run the test, the result are stored >> into the class that has been run. >> Maybe we could store them in a location outside the package. But >> test results will not be persistent. > > Yes and no. The package becomes dirty only if the test results > change - ie if a test goes from failure to pass for example. > >> >> >> Alexandre >> >> On 10 Nov 2008, at 14:40, StÃ©phane Ducasse wrote: >> >>> what would be nice if that the packages do not get dirty because >>> the tests run. >>> I do not know if this is the case but this is important. >>> >>> On Nov 10, 2008, at 4:58 PM, Alexandre Bergel wrote: >>> >>>> I have seen this. We should continue this discussion offline, >>>> then propose a robust and stable version to the pharo community. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> On 10 Nov 2008, at 12:53, Simon Denier wrote: >>>> >>>>> >>>>> On 10 nov. 08, at 11:07, David RÃ¶thlisberger wrote: >>>>> >>>>>> >>>>>>> So let me know when I can load again and integrate your >>>>>>> extension. >>>>>> >>>>>> Could you please check with SUnit-DavidRoethlisberger.42 in http://www.squeaksource.com/Pharo >>>>>> and execute ScriptLoader class >> loadOB? >>>>> >>>>> It is not enough >>>>> >>>>> Starting from a fresh 10144 image, loading OB with scriptloader, >>>>> then your latest commit for sunit, I do get the icons in the >>>>> browser, but cant update their state: not lastRun method is >>>>> generated and it fails when I try to save the results in the >>>>> TestRunner. Best guess: the code generating lastRun on the class >>>>> side is lost. >>>>> >>>>>> >>>>>> >>>>>>> Then after it would be great to have a button to run the tests >>>>>>> and >>>>>> >>>>>> yes, we should have something like that in the browser. >>>>>> >>>>>> David >>>>>> >>>>>> >>>>>>>> Hi Stef, >>>>>>>> >>>>>>>> as you as the SUnit extensions are integrated, you just need >>>>>>>> to load OB. Any OB load method in ScriptLoader can be used >>>>>>>> for this as this extension is also in the stable OB version >>>>>>>> now. >>>>>>>> >>>>>>>> David >>>>>>>> >>>>>>>>> can you tell me what I should do to get the icons showing >>>>>>>>> the status of tests in your browser? >>>>>>>>> I should harvest the Sunit extensions and then? >>>>>>>>> Stef >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> -- >>>>> Simon >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> 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 >> > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 10, 2008