December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] pharo images - Win32 Installer

by Mariano Martinez Peck

On Tue, Dec 29, 2009 at 4:22 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > setup_pharo1.0-10502-rc1dev09.12.2.exe and > setup_pharo1.1-11112-alphadev09.12.2.exe > > are up on the downl Thanks! this is really cool. Maybe it would be a good idea to rename setup_pharo1.1-11112-alphadev09.12.2.exe to setup_pharo1.1-11112-UNSTABLEdev09.12.2.exe We have been discussing this and we want to be sure people understand that 1.1 is unstable and very yet in development. THanks! Mariano oad page > > 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 >

Dec. 29, 2009

[Pharo-project] pharo images - Win32 Installer

by Torsten Bergmann

setup_pharo1.0-10502-rc1dev09.12.2.exe and setup_pharo1.1-11112-alphadev09.12.2.exe are up on the download page Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Dec. 29, 2009

Re: [Pharo-project] My idea of Metacello configurations for Pharo

by StÃ©phane Ducasse

sound great! Thanks for pushing that. I think that this is the vision we have in mind and discuss during the sprint at Lille. I think that having a loader/map for any project is the way to go. Ideally a person should write its own configuration file and publish it to his own repo and also to the MetacelloRepository. so you are making 1.1 more credible because it was in the roadmap :) Stef On Dec 29, 2009, at 3:11 PM, Mariano Martinez Peck wrote: > Hi folks. I just wanted to write down my ideas of the Metacello configurations for our Pharo Images. The idea is to use Metacello to manage the dependencies and version of the packages, have a history of the releases and be more modular. You will be able to take a core image and easily load what you want. We will have a ConfigurationOfPharo and that's what you will probably use. However, this conf depends and delegates to another configurations (the conf of each package). So, the first step is to make each little conf to work, and then, we focus in the pharo one. > > So....lists of points: > > 1) I have been writing several configurations so far. One configuration per external project that is loaded in Pharo Dev images. Examples: Shout, OCompletion, RefactoringBrowser, OmniBroswer, O2, etc.. > The idea is to implement and be sure each of this conf is working before doing the ConfigurationOfPharo. > > 2) All configurations will be published here: http://www.squeaksource.com/MetacelloRepository > This repository is like the ibiblio for maven, or the Universe for the apt-get, or similar. In a near future we will have tools that work with this (Esteban Lorenzano is working in Loader for example). > > 3) Each configuration must be PERFECTLY loaded in a Pharo Core image without doing or installing nothing. To do this, I have to declare properly the dependencies. > This mean, that you will be able to take a core image load the ConfigurationOfShout for exameple, or OCompletion and you will be able to load it. Metacello will take care of all the dependencies. > You will also be able to install part of the project and not all (for example, only core or core + tests, or whatever). > > 4) I started with the Dev packages. We will do this test first to see if Metacello really help us in our project. If this goes well, then, in a second step, we will take care about the Web images. > > 5) I started with the 1.0 Dev packages. 1.1 is unestable and several external packages even don't load in it. So, will do 1.1 in a second step. > > 6) As there were no versions of Metacello in all the external projects, I started with 1.0 in ALL. Shout 1.0, OCompletion 1.0, RB 1.0, etc. This has nothing to do with Pharo 1.0. They are just the version number. And after this is released, we really need PLEASE, that the maintainers of those packages also creates the following versions for them. > > 7) I took as a base, the versions of the 10496 image. I have been using this image since in was release, 12 hours a day, and seems to be very stable to me. I mean, the version 1.0 of ConfigurationOfPharo will be like the 10496 image. When everything is done and working, create a new image will be very easy. > > 8) We need some features from Metacello which are in the todo list. So, we will have to wait a bit for them. > > OK, that's all. What do you think? > > Soon I will send an email for the configurations of all projects and will ask for help and feedback from their developers. > > Cheers, > > Mariano > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 29, 2009

Re: [Pharo-project] Assumptions (was Re: akuhn/SUnit, christmas edition :)

by Julian Fitzell

On Tue, Dec 29, 2009 at 2:13 AM, Adrian Kuhn <akuhn(a)iam.unibe.ch> wrote: >> On Dec 29, 2009, at 7:21 AM, Julian Fitzell wrote: >> >> > Then, having said that, #assume: sounds a bit like the test should >> > assume the statement is true and then carry on running with that >> > assumption. Maybe #expect: would be more descriptive? Or >> > #precondition: ? Not sure... >> >> StÃ©phane Ducasse <stephane.ducasse@...> writes: >> >> yes expect: seems better. > > Hmm, that sound to me as if the test should fail when the expectations is > Â not met, whereas in fact it is skipped unless the condition is true. > > What about something like #skipUnless: ? Sure... I think #expect: could be interpreted either way; #skipUnless: pretty unambiguous. Julian

Dec. 29, 2009

[Pharo-project] My idea of Metacello configurations for Pharo

by Mariano Martinez Peck

Hi folks. I just wanted to write down my ideas of the Metacello configurations for our Pharo Images. The idea is to use Metacello to manage the dependencies and version of the packages, have a history of the releases and be more modular. You will be able to take a core image and easily load what you want. We will have a ConfigurationOfPharo and that's what you will probably use. However, this conf depends and delegates to another configurations (the conf of each package). So, the first step is to make each little conf to work, and then, we focus in the pharo one. So....lists of points: 1) I have been writing several configurations so far. One configuration per external project that is loaded in Pharo Dev images. Examples: Shout, OCompletion, RefactoringBrowser, OmniBroswer, O2, etc.. The idea is to implement and be sure each of this conf is working before doing the ConfigurationOfPharo. 2) All configurations will be published here: http://www.squeaksource.com/MetacelloRepository This repository is like the ibiblio for maven, or the Universe for the apt-get, or similar. In a near future we will have tools that work with this (Esteban Lorenzano is working in Loader for example). 3) Each configuration must be PERFECTLY loaded in a Pharo Core image without doing or installing nothing. To do this, I have to declare properly the dependencies. This mean, that you will be able to take a core image load the ConfigurationOfShout for exameple, or OCompletion and you will be able to load it. Metacello will take care of all the dependencies. You will also be able to install part of the project and not all (for example, only core or core + tests, or whatever). 4) I started with the Dev packages. We will do this test first to see if Metacello really help us in our project. If this goes well, then, in a second step, we will take care about the Web images. 5) I started with the 1.0 Dev packages. 1.1 is unestable and several external packages even don't load in it. So, will do 1.1 in a second step. 6) As there were no versions of Metacello in all the external projects, I started with 1.0 in ALL. Shout 1.0, OCompletion 1.0, RB 1.0, etc. This has nothing to do with Pharo 1.0. They are just the version number. And after this is released, we really need PLEASE, that the maintainers of those packages also creates the following versions for them. 7) I took as a base, the versions of the 10496 image. I have been using this image since in was release, 12 hours a day, and seems to be very stable to me. I mean, the version 1.0 of ConfigurationOfPharo will be like the 10496 image. When everything is done and working, create a new image will be very easy. 8) We need some features from Metacello which are in the todo list. So, we will have to wait a bit for them. OK, that's all. What do you think? Soon I will send an email for the configurations of all projects and will ask for help and feedback from their developers. Cheers, Mariano

Dec. 29, 2009

Re: [Pharo-project] Assumptions (was Re: akuhn/SUnit, christmas edition :)

by StÃ©phane Ducasse

yes much much better to me. On Dec 29, 2009, at 11:13 AM, Adrian Kuhn wrote: >> On Dec 29, 2009, at 7:21 AM, Julian Fitzell wrote: >> >>> Then, having said that, #assume: sounds a bit like the test should >>> assume the statement is true and then carry on running with that >>> assumption. Maybe #expect: would be more descriptive? Or >>> #precondition: ? Not sure... >> >> StÃ©phane Ducasse <stephane.ducasse@...> writes: >> >> yes expect: seems better. > > Hmm, that sound to me as if the test should fail when the expectations is > not met, whereas in fact it is skipped unless the condition is true. > > What about something like #skipUnless: ? > > --AA > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 29, 2009

Re: [Pharo-project] How to execute code before and after a package is load?

by Mariano Martinez Peck

On Tue, Dec 29, 2009 at 11:08 AM, Adrian Kuhn <akuhn(a)iam.unibe.ch> wrote: > StÃ©phane Ducasse <stephane.ducasse@...> writes: > > > I **never** used scripts. I have no idea what they are (even if I guess) > and > > more important the door that they open into a space that we do not > control is > > dangerous. > > They are pre- and postload code snippets. If you add 4 missing methods on > package info you get them in monticello (but sometimes they seem not to > execute when loading a package, so I gave up at that point...) > > > In metacello there is a preload and postload if I remember. > > How do I use metacello, any documentation / tutorial available? > http://code.google.com/p/metacello/wiki/Tutorial I would recommend the "Image-based Tutorial". If you want more examples you can check the http://www.squeaksource.com/MetacelloRepository Yes, Metacello does support post and pre doits but the problem is that it is only at package level, not project. Dale is aware of this and already put in his todo list to have pre a post scripts for a whole project. A simple hack is to put the post script to the last package. Cheers Mariano > > cheers, > AA > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 29, 2009

Re: [Pharo-project] Tests of OmniBrowser

by Lukas Renggli

> you should send an email to lukas and david when you report a bug in OB or related > Apparently the mail on code.google.com/p/pharo does not reach lukas when you add it to the form. It does now, I think. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 29, 2009

Re: [Pharo-project] Assumptions (was Re: akuhn/SUnit, christmas edition :)

by Adrian Kuhn

> On Dec 29, 2009, at 7:21 AM, Julian Fitzell wrote: > > > Then, having said that, #assume: sounds a bit like the test should > > assume the statement is true and then carry on running with that > > assumption. Maybe #expect: would be more descriptive? Or > > #precondition: ? Not sure... > > StÃ©phane Ducasse <stephane.ducasse@...> writes: > > yes expect: seems better. Hmm, that sound to me as if the test should fail when the expectations is not met, whereas in fact it is skipped unless the condition is true. What about something like #skipUnless: ? --AA

Dec. 29, 2009

Re: [Pharo-project] New class factory for tests (and other use cases)

by StÃ©phane Ducasse

:) cool bezalht :) Stef On Dec 29, 2009, at 11:05 AM, Adrian Kuhn wrote: > StÃ©phane Ducasse <stephane.ducasse@...> writes: > >> class := ClassFactory newSubclass: Point with: [ :f | >> f metaSide compile: 'somePoint ^ self x: 2 y: 3'. >> f compile: '+ arg ^ self x + arg x ..... 3' ]. >> ]. > > Looks nicer, gekauft :) > > --AA > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 29, 2009