btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev?

On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck

<marianopeck@gmail.com> said:

>
>
> (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 :)
>
>

> (Sorry for the long email)<br><br>Yes, after a couple of weeks, I have writ=
> ten most of the needed Metacello configurations for the Dev images 1.0. For=
> get 1.1 for a while. Now we are able to:<br><br>1) Load stable version of p=
> ackages<br>
> 2) Manage the dependencies automatically<br>3) Each developer can create it=
> s custom PharoDev image<br>
> 4) Flexibility to load the packages you want<br>5) Choose the browser for e=
> xample: OB or O2<br>6) Choose to load the tests or not<br>7) Load each pack=
> age in a PharoCore image without having to install anything else (all the d=
> ependencies should be managed automatically)<br>
>
> 8) You can take a PharoCore image and &quot;transform&quot; it to a Dev ima=
> ge, or even web. <br>9) Others...<br><br>This is not completed yet. There a=

> re some things that we are discussing with Dale, but they are ok as a first=

> �step. I rather go step by step. <br>
> <br>What I did is to create all the infrastructure:<br><br>a) The Configura=
> tion classes<br>b) The dependencies <br>
> c)=A0 the groups,<br><br>In summary, most of the &quot;structure&quot; and =
> static information. However, I am not sure which version to load of each pa=
> ckage. I will probable take care of building the Dev images, but I won&#39;=
> t:<br>
>
> <br>- Merge anything. It will not be my task to merge OB, or RB or whatever=
> .<br>- Check every version of each package before doing a release to see if=
> �it is stable or not.<br><br>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. Yo=

> u 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 probab=
> ly understand it. However, you can read the Metacello tutorial (no more tha=
> n one hour), or ask me or even more in the Metacello mailing list. So...PLE=
> ASE, I need the help of the maintainers to create the versions. So far, I c=
> reated the first version (1.0) with the latest version. But the idea is tha=
> t then you create 1.1.1 or 1.2 or whatever you consider.<br>
> <br>All the configurations can be found in <a href=3D"http://www.squeaksour=
> ce.com/MetacelloRepository">http://www.squeaksource.com/MetacelloRepository=
> </a><br><br>So far, I created:=A0 ConfigurationOfNewInspector, Configuratio=
> nOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtr=
> as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, Configura=
> tionOfShout , and......ConfigurationOfPharo!!!<br>
> <br>To install them, just download that package and evaluate the load. Exam=
> ple:<br><br>Gofer new<br>=A0=A0=A0 squeaksource: &#39;MetacelloRepository&#=
> 39;;<br>=A0=A0=A0 package: &#39;ConfigurationOfShout&#39;;<br>=A0=A0=A0 loa=
> d.<br><br>((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&=
> #39;) load.<br>
> <br>And then, you can also for exaple do:=A0 <br><br>
> ((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&#39;) load=
> : &#39;Core&#39;=A0 <br>this doesn&#39;t install the tests. <br><br>Or for =
> example:=A0 (ConfigurationOfOmniBrowser project version: &#39;1.0&#39;) loa=
> d: &#39;Dev&#39;<br>
> <br>etc...<br><br>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.<br><br>What I would really appreciate is if each maintainer can look=
> �at the code, load the different groups and give me feedback on the depende=
> ncies or whatever.<br>
> <br>I really wait your feedback. <br><br>Mariano<br><br>ps:=A0 I will relea=
> se soon the first dev image using this :)<br>
> <br>

>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project




_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project