Hi, To me this discussion again raises the point of what I call the "default" case for development :). Lukas, the simplest thing that you can do at this moment is to introduce a "default" version (see those in the ConfigurationOfGlamour/Mondrian/Moose...). This is nothing but your order of packages. Afterwards, you just load that one. When someone wants to hardcode a version, you just spawn this version with the package versions you have in the image. Like this, you have best of both worlds: (1) lightweight management for development, and (2) controlled versioning for releases. Cheers, Doru On 8 Oct 2010, at 17:25, Lukas Renggli wrote:
Yeah, I agree, there is definitely a need for Metacello.
I suggest to make it easier to use, faster and more lightweight. Currently it is more the opposite.
I propose something along Gofer, but for Metacello (I believe somebody already did something like this?):
1. loading the latest stable version must be dead simple
Metacello new project: 'OB'; loadStable
2. loading the latest development version must be dead simple
Metacello new project: 'OB'; loadDevelopment
3. specifying what groups to load must be dead simple
Metacello new project: 'Seaside'; group: 'Tests'; group: 'Javascript'; load
4. loading should not require to additional infrastructure to be loaded into a Pharo image (I imagine a server that has all configurations preloaded and that returns Gofer scripts that can be executed in the target image)
Lukas
On 8 October 2010 17:15, Miguel Cobá <miguel.coba@gmail.com> wrote:
El vie, 08-10-2010 a las 09:56 -0400, Alexandre Bergel escribió:
ConfigurationOfOmnibrowser project load@*%$LatestCode
better in my opinion: ConfigurationOfOmnibrowser loadLastVersion
As a metathough, I think we need a unification of how Configuration are defined and used. We have loadDefault in Moose. I often do a ConfigurationOfXX project lastVersion load. You can directly load the baseline. I know this has been discussed many times. But we really need to come up with a simple and efficient way to use configuration.
I would also like to have ConfigurationOfXX forEachVersionsLoadAndDo: [:v | ... ], versionsSelect: [:v | ... ], ...
Alexandre
There is a long thread in the metacello mailing list where those topics are being discussed and Dale is right now working in the new code to support them. So if you want to be heard please propose those guidelines there so they are taken in account.
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com "One cannot do more than one can do."