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

Re: [Pharo-project] [Metacello] Re: [ANN] Metacello configurations for Pharo.

by Dale Henrichs

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 10:28 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Jan 7, 2010, at 10:13 PM, Mariano Martinez Peck wrote: > > > > > > > On Thu, Jan 7, 2010 at 10:04 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > Hi Mariano, > > > > There is something not clear to me. How do you envision the > > squeaksource project 'Metacello Repository'. For Omnibrowser, should > > the configuration be in the ob repository, or being kept in 'Metacello > > Repository'? > > > > Thanks for asking Alex. No, they are kept in MetacelloRepository. Think > in metacello repository as a catalog where you can find all the software > that are manage with metacello. Even each metacello configuration can be > used in Squeak, Pharo, Gemstone or any other Smalltalk that supports > Monticello. > > So, every Metacello configuration, should be there. If you are familiar > with Debian/Ubuntu, it is something like the Universe with the apt-get or if > you know Maven (from Java world), it is like the Ibiblio repository. > > yes but let us that only public and working one could be published there. > > I didn't understand you stef. > > > > Next week I will work on OB with David. I really like his browser, but > > there are many bugs still... > > > > I guess you are talking about 02. Yes, I also like it, but it is not > working properly right now. We decided to exclude it temporaly until it > doesn't affects OB and until it can be perfactl loaded in a PharoCore image > withput anything about OB. Sorry, that was a decision taken with the board. > It is just for a moment. We rather to break only O2 users but not both. If > you want, you can take the next PharoDev image and install O2 by yourself. > > > > Please, to discuss OB versus O2 use another thread :) > > > > Cheers > > > > Mariano > > > > > > Cheers, > > Alexandre > > > > > > On 7 Jan 2010, at 17:54, Mariano Martinez Peck wrote: > > > > > (Sorry for the long email) > > > > > > Yes, after a couple of weeks, I have written most of the needed > > > Metacello configurations for the Dev images 1.0. Forget 1.1 for a > > > while. Now we are able to: > > > > > > 1) Load stable version of packages > > > 2) Manage the dependencies automatically > > > 3) Each developer can create its custom PharoDev image > > > 4) Flexibility to load the packages you want > > > 5) Choose the browser for example: OB or O2 > > > 6) Choose to load the tests or not > > > 7) Load each package in a PharoCore image without having to install > > > anything else (all the dependencies should be managed automatically) > > > 8) You can take a PharoCore image and "transform" it to a Dev image, > > > or even web. > > > 9) Others... > > > > > > This is not completed yet. There are some things that we are > > > discussing with Dale, but they are ok as a first step. I rather go > > > step by step. > > > > > > What I did is to create all the infrastructure: > > > > > > a) The Configuration classes > > > b) The dependencies > > > c) the groups, > > > > > > In summary, most of the "structure" and static information. However, > > > I am not sure which version to load of each package. I will probable > > > take care of building the Dev images, but I won't: > > > > > > - Merge anything. It will not be my task to merge OB, or RB or > > > whatever. > > > - Check every version of each package before doing a release to see > > > if it is stable or not. > > > > > > So...what I REALLY (actually, WE) need is that each developer, each > > > maintainer of the packages that we load of a PharoDev image, help us > > > to create the stable versions. To create a new version for the > > > Metacello configuration is VERY easy, The hard part is already done. > > > You just have to create a method and say which versions (except you > > > create or eliminate packages or dependencies). If you read the code, > > > you will probably understand it. However, you can read the Metacello > > > tutorial (no more than one hour), or ask me or even more in the > > > Metacello mailing list. So...PLEASE, I need the help of the > > > maintainers to create the versions. So far, I created the first > > > version (1.0) with the latest version. But the idea is that then you > > > create 1.1.1 or 1.2 or whatever you consider. > > > > > > All the configurations can be found in > http://www.squeaksource.com/MetacelloRepository > > > > > > So far, I created: ConfigurationOfNewInspector, > > > ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, > > > ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, > > > ConfigurationOfRefactoringBrowser, ConfigurationOfShout , > > > and......ConfigurationOfPharo!!! > > > > > > To install them, just download that package and evaluate the load. > > > Example: > > > > > > Gofer new > > > squeaksource: 'MetacelloRepository'; > > > package: 'ConfigurationOfShout'; > > > load. > > > > > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. > > > > > > And then, you can also for exaple do: > > > > > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: > > > 'Core' > > > this doesn't install the tests. > > > > > > Or for example: (ConfigurationOfOmniBrowser project version: '1.0') > > > load: 'Dev' > > > > > > etc... > > > > > > So, you can load any project and with the group you want. All of > > > that can be (or should be hahahaha) perfectly loaded in a 1.0 Core > > > image. > > > > > > What I would really appreciate is if each maintainer can look at the > > > code, load the different groups and give me feedback on the > > > dependencies or whatever. > > > > > > I really wait your feedback. > > > > > > Mariano > > > > > > ps: I will release soon the first dev image using this :) > > > > > > _______________________________________________ > > > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 7, 2010

Re: [Pharo-project] Screencast in mac?

by merlyn＠stonehenge.com

>>>>> "Johan" == Johan Fabry <jfabry(a)dcc.uchile.cl> writes: Johan> hot on the tail of Stans mail: I want to do some screencasts on a mac, Johan> maybe without audio. Good experiences anyone? Very happy with ScreenFlow, which not only captures full screen at full speed (without ever missing a frame), also has a great video editing suite built in, and can handle nice HD videos for Vimeo and Youtube HD. Yeah, it's $100 but worth it. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 10:33 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > A minor comment: > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfPharo'; > > load. > > > > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0- > > rc2.10505') load. > > > I find this incantation quite ugly. > > This is what we have so far. > Why not something like: > Gofer load: 'ConfigurationOfPharo' version: '1.0-rc2.10505'. > Gofer loadLastVersionOf: 'ConfigurationOfPharo'. > > Because right now is the only way. If MetacelloConfigurations has acceptance, then we can even create a mehod in Gofer like this: Gofer new metacelloRepository: 'ConfigurationOfPharo'; package: 'Slime'; load. > Even better: > Gofer load: 'Pharo' version: '1.0-rc2.10505'. > Gofer loadLastVersionOf: 'Pharo'. > > For example, I find the expression quite unintuitive: > Gofer new squeaksource: 'Mondrian'; package: > 'ConfigurationOfMondrian'; load. (Smalltalk at: > #ConfigurationOfMondrian) perform: #loadDefault. > > I always need to lookup the mondrian website. > Gofer loadLastVersionOf: 'Mondrian' > would be perfect (assuming that ConfigurationOfMondrian) is in > MetacelloRepository > > Yes, I agree. But don't worry. Esteban Lorenzano is working exatly in that. You will be able to do: Loader load: 'Pharo' version: '1.0' and wala!! (Esteban, correct me if I am wrong). However, this is yet in development and we are not even sure if this architecture will be the choosen one. We are just trying to see what we can doo. > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

Jan. 7, 2010

Re: [Pharo-project] [ANN] Icons for Mac users

by Alexandre Bergel

Thanks Torsten. This is really nice to see people with a good aesthetic feeling. I use your icons. Cheers, Alexandre On 7 Jan 2010, at 18:26, Mariano Martinez Peck wrote: > > > On Thu, Jan 7, 2010 at 10:23 PM, Torsten Bergmann <astares(a)gmx.de> > wrote: > >I don't know who did the icons. > > That was me - I used Samuel's logos as a base. > > I once created them for page 15 (figure 1.1.) of the > pharo-by-example book where image, source, etc. files > are introduced and made them available via gforge to Oscar > Nierstrasz for inclusion in the book. > > Unfortunately he decided he wanted to have the windows icons, > so I made a screenshot of the (IMHO more ugly) win icons > which are now included as figure 1.1 in the book. > > Thanks for the conversion, at least they are used now. > > > Thanks Torsten. I really like them :) > > Bye > T. > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Alexandre Bergel

> excellent! > Alex may be this is necessary to see how we can migrate some part of > his browser on top of OB. Yup! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] Screencast in mac?

by Ken G. Brown

In OS X 10.6.2 at least, version 10.0 of Quicktime Player has File/New Screen Recording Ken G. Brown At 10:27 PM +0100 1/7/10, pharo-project-request(a)lists.gforge.inria.fr apparently wrote: >Date: Thu, 7 Jan 2010 18:22:26 -0300 >From: Johan Fabry <jfabry(a)dcc.uchile.cl> >Subject: [Pharo-project] Screencast in mac? >To: pharo-project(a)lists.gforge.inria.fr >Message-ID: <79875CC9-EE56-489E-A53D-6832CE09EDCF(a)dcc.uchile.cl> >Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > >Hi all, > >hot on the tail of Stans mail: I want to do some screencasts on a mac, >maybe without audio. Good experiences anyone? > >-- >Johan Fabry >jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry >PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Alexandre Bergel

A minor comment: > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0- > rc2.10505') load. I find this incantation quite ugly. Why not something like: Gofer load: 'ConfigurationOfPharo' version: '1.0-rc2.10505'. Gofer loadLastVersionOf: 'ConfigurationOfPharo'. Even better: Gofer load: 'Pharo' version: '1.0-rc2.10505'. Gofer loadLastVersionOf: 'Pharo'. For example, I find the expression quite unintuitive: Gofer new squeaksource: 'Mondrian'; package: 'ConfigurationOfMondrian'; load. (Smalltalk at: #ConfigurationOfMondrian) perform: #loadDefault. I always need to lookup the mondrian website. Gofer loadLastVersionOf: 'Mondrian' would be perfect (assuming that ConfigurationOfMondrian) is in MetacelloRepository Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by StÃ©phane Ducasse

On Jan 7, 2010, at 10:13 PM, Mariano Martinez Peck wrote: > > > On Thu, Jan 7, 2010 at 10:04 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > Hi Mariano, > > There is something not clear to me. How do you envision the > squeaksource project 'Metacello Repository'. For Omnibrowser, should > the configuration be in the ob repository, or being kept in 'Metacello > Repository'? > > Thanks for asking Alex. No, they are kept in MetacelloRepository. Think in metacello repository as a catalog where you can find all the software that are manage with metacello. Even each metacello configuration can be used in Squeak, Pharo, Gemstone or any other Smalltalk that supports Monticello. > So, every Metacello configuration, should be there. If you are familiar with Debian/Ubuntu, it is something like the Universe with the apt-get or if you know Maven (from Java world), it is like the Ibiblio repository. yes but let us that only public and working one could be published there. > > Next week I will work on OB with David. I really like his browser, but > there are many bugs still... > > I guess you are talking about 02. Yes, I also like it, but it is not working properly right now. We decided to exclude it temporaly until it doesn't affects OB and until it can be perfactl loaded in a PharoCore image withput anything about OB. Sorry, that was a decision taken with the board. It is just for a moment. We rather to break only O2 users but not both. If you want, you can take the next PharoDev image and install O2 by yourself. > > Please, to discuss OB versus O2 use another thread :) > > Cheers > > Mariano > > > Cheers, > Alexandre > > > On 7 Jan 2010, at 17:54, Mariano Martinez Peck wrote: > > > (Sorry for the long email) > > > > Yes, after a couple of weeks, I have written most of the needed > > Metacello configurations for the Dev images 1.0. Forget 1.1 for a > > while. Now we are able to: > > > > 1) Load stable version of packages > > 2) Manage the dependencies automatically > > 3) Each developer can create its custom PharoDev image > > 4) Flexibility to load the packages you want > > 5) Choose the browser for example: OB or O2 > > 6) Choose to load the tests or not > > 7) Load each package in a PharoCore image without having to install > > anything else (all the dependencies should be managed automatically) > > 8) You can take a PharoCore image and "transform" it to a Dev image, > > or even web. > > 9) Others... > > > > This is not completed yet. There are some things that we are > > discussing with Dale, but they are ok as a first step. I rather go > > step by step. > > > > What I did is to create all the infrastructure: > > > > a) The Configuration classes > > b) The dependencies > > c) the groups, > > > > In summary, most of the "structure" and static information. However, > > I am not sure which version to load of each package. I will probable > > take care of building the Dev images, but I won't: > > > > - Merge anything. It will not be my task to merge OB, or RB or > > whatever. > > - Check every version of each package before doing a release to see > > if it is stable or not. > > > > So...what I REALLY (actually, WE) need is that each developer, each > > maintainer of the packages that we load of a PharoDev image, help us > > to create the stable versions. To create a new version for the > > Metacello configuration is VERY easy, The hard part is already done. > > You just have to create a method and say which versions (except you > > create or eliminate packages or dependencies). If you read the code, > > you will probably understand it. However, you can read the Metacello > > tutorial (no more than one hour), or ask me or even more in the > > Metacello mailing list. So...PLEASE, I need the help of the > > maintainers to create the versions. So far, I created the first > > version (1.0) with the latest version. But the idea is that then you > > create 1.1.1 or 1.2 or whatever you consider. > > > > All the configurations can be found in http://www.squeaksource.com/MetacelloRepository > > > > So far, I created: ConfigurationOfNewInspector, > > ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, > > ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, > > ConfigurationOfRefactoringBrowser, ConfigurationOfShout , > > and......ConfigurationOfPharo!!! > > > > To install them, just download that package and evaluate the load. > > Example: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfShout'; > > load. > > > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. > > > > And then, you can also for exaple do: > > > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: > > 'Core' > > this doesn't install the tests. > > > > Or for example: (ConfigurationOfOmniBrowser project version: '1.0') > > load: 'Dev' > > > > etc... > > > > So, you can load any project and with the group you want. All of > > that can be (or should be hahahaha) perfectly loaded in a 1.0 Core > > image. > > > > What I would really appreciate is if each maintainer can look at the > > code, load the different groups and give me feedback on the > > dependencies or whatever. > > > > I really wait your feedback. > > > > Mariano > > > > ps: I will release soon the first dev image using this :) > > > > _______________________________________________ > > 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

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by StÃ©phane Ducasse

On Jan 7, 2010, at 10:04 PM, Alexandre Bergel wrote: > Hi Mariano, > > There is something not clear to me. How do you envision the > squeaksource project 'Metacello Repository'. For Omnibrowser, should > the configuration be in the ob repository, or being kept in 'Metacello > Repository'? what you can see is the following I code in my projects and publish config for me when I decide that one is ok for other to use then I copy it in Metacello Repository > Next week I will work on OB with David. I really like his browser, but > there are many bugs still... excellent! Alex may be this is necessary to see how we can migrate some part of his browser on top of OB. > > Cheers, > Alexandre > > > On 7 Jan 2010, at 17:54, Mariano Martinez Peck wrote: > >> (Sorry for the long email) >> >> Yes, after a couple of weeks, I have written most of the needed >> Metacello configurations for the Dev images 1.0. Forget 1.1 for a >> while. Now we are able to: >> >> 1) Load stable version of packages >> 2) Manage the dependencies automatically >> 3) Each developer can create its custom PharoDev image >> 4) Flexibility to load the packages you want >> 5) Choose the browser for example: OB or O2 >> 6) Choose to load the tests or not >> 7) Load each package in a PharoCore image without having to install >> anything else (all the dependencies should be managed automatically) >> 8) You can take a PharoCore image and "transform" it to a Dev image, >> or even web. >> 9) Others... >> >> This is not completed yet. There are some things that we are >> discussing with Dale, but they are ok as a first step. I rather go >> step by step. >> >> What I did is to create all the infrastructure: >> >> a) The Configuration classes >> b) The dependencies >> c) the groups, >> >> In summary, most of the "structure" and static information. However, >> I am not sure which version to load of each package. I will probable >> take care of building the Dev images, but I won't: >> >> - Merge anything. It will not be my task to merge OB, or RB or >> whatever. >> - Check every version of each package before doing a release to see >> if it is stable or not. >> >> So...what I REALLY (actually, WE) need is that each developer, each >> maintainer of the packages that we load of a PharoDev image, help us >> to create the stable versions. To create a new version for the >> Metacello configuration is VERY easy, The hard part is already done. >> You just have to create a method and say which versions (except you >> create or eliminate packages or dependencies). If you read the code, >> you will probably understand it. However, you can read the Metacello >> tutorial (no more than one hour), or ask me or even more in the >> Metacello mailing list. So...PLEASE, I need the help of the >> maintainers to create the versions. So far, I created the first >> version (1.0) with the latest version. But the idea is that then you >> create 1.1.1 or 1.2 or whatever you consider. >> >> All the configurations can be found in http://www.squeaksource.com/MetacelloRepository >> >> So far, I created: ConfigurationOfNewInspector, >> ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, >> ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, >> ConfigurationOfRefactoringBrowser, ConfigurationOfShout , >> and......ConfigurationOfPharo!!! >> >> To install them, just download that package and evaluate the load. >> Example: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfShout'; >> load. >> >> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. >> >> And then, you can also for exaple do: >> >> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: >> 'Core' >> this doesn't install the tests. >> >> Or for example: (ConfigurationOfOmniBrowser project version: '1.0') >> load: 'Dev' >> >> etc... >> >> So, you can load any project and with the group you want. All of >> that can be (or should be hahahaha) perfectly loaded in a 1.0 Core >> image. >> >> What I would really appreciate is if each maintainer can look at the >> code, load the different groups and give me feedback on the >> dependencies or whatever. >> >> I really wait your feedback. >> >> Mariano >> >> ps: I will release soon the first dev image using this :) >> >> _______________________________________________ >> 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

Jan. 7, 2010