Ahhhh... ok :) On 2010-01-08 09:48:17 -0300, Mariano Martinez Peck <marianopeck@gmail.com> said:
On Fri, Jan 8, 2010 at 1:12 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev?
No. For that we have the groups. The same ConfigurationOfPharo will be used for differents stuff:
ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoDev'
or
ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoWeb ' (if they came back)
or
ConfigurationOfPharo project version: 'xxx' load: 'SOMETHING' (if they came back)
Cheers
Mariano
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 "transform" 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 "structure" 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'= 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: 'MetacelloRepository&#= 39;;<br>=A0=A0=A0 package: 'ConfigurationOfShout';<br>=A0=A0=A0 loa= d.<br><br>((Smalltalk at: #ConfigurationOfShout) project version: '1.0&= #39;) load.<br> <br>And then, you can also for exaple do:=A0 <br><br> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load= : 'Core'=A0 <br>this doesn't install the tests. <br><br>Or for = example:=A0 (ConfigurationOfOmniBrowser project version: '1.0') loa= d: 'Dev'<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
<br><br><div class=3D"gmail_quote">On Fri, Jan 8, 2010 at 1:12 PM, Esteban = Lorenzano <span dir=3D"ltr"><<a href=3D"mailto:estebanlm@gmail.com">este= banlm@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" = style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8= ex; padding-left: 1ex;"> btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev?<br> <br></blockquote><div><br>No. For that we have the groups. The same Configu= rationOfPharo will be used for differents stuff:<br><br>ConfigurationOfPhar= o project version: 'xxx' load: 'StandardPharoDev'<br><br> or<br><br>ConfigurationOfPharo project version: 'xxx' load: 'St= andardPharoWeb '=A0=A0 (if they came back)<br><br>or <br><br>Configurat= ionOfPharo project version: 'xxx' load: 'SOMETHING'=A0 (if = they came back)<br>
<br>Cheers<br><br>Mariano<br> <br>=A0</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px so= lid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck<br> <div><div></div><div class=3D"h5"><<a href=3D"mailto:marianopeck@gmail.c= om">marianopeck@gmail.com</a>> said:<br> <br> ><br> ><br> > (Sorry for the long email)<br> ><br> > Yes, after a couple of weeks, I have written most of the needed Metace= llo<br> > configurations for the Dev images 1.0. Forget 1.1 for a while. Now we = are<br> > able to:<br> ><br> > 1) Load stable version of packages<br> > 2) Manage the dependencies automatically<br> > 3) Each developer can create its custom PharoDev image<br> > 4) Flexibility to load the packages you want<br> > 5) Choose the browser for example: OB or O2<br> > 6) Choose to load the tests or not<br> > 7) Load each package in a PharoCore image without having to install an= ything<br> > else (all the dependencies should be managed automatically)<br> > 8) You can take a PharoCore image and "transform" it to a De= v image, or even<br> > web.<br> > 9) Others...<br> ><br> > This is not completed yet. There are some things that we are discussin= g with<br> > 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 Configuration classes<br> > b) The dependencies<br> > c) =A0the groups,<br> ><br> > In summary, most of the "structure" and static information. = However, I am<br> > not sure which version to load of each package. I will probable take c= are of<br> > building the Dev images, but I won't:<br> ><br> > - Merge anything. It will not be my task to merge OB, or RB or whateve= r.<br> > - Check every version of each package before doing a release to see if= it is<br> > stable or not.<br> ><br> > So...what I REALLY (actually, WE) need is that each developer, each<br=
> maintainer of the packages that we load of a PharoDev image, help us t= o<br> > create the stable versions. To create a new version for the Metacello<= br> > configuration is VERY easy, The hard part is already done. You just ha= ve to<br> > create a method and say which versions (except you create or eliminate= <br> > packages or dependencies). If you read the code, you will probably<br> > understand it. However, you can read the Metacello tutorial (no more t= han<br> > one hour), or ask me or even more in the Metacello mailing list.<br> > So...PLEASE, I need the help of the maintainers to create the versions= . So<br> > far, I created the first version (1.0) with the latest version. But th= e idea<br> > is that then you create 1.1.1 or 1.2 or whatever you consider.<br> ><br> > All the configurations can be found in<br> > <a href=3D"http://www.squeaksource.com/MetacelloRepository" target=3D"= _blank">http://www.squeaksource.com/MetacelloRepository</a><br> ><br> > So far, I created: =A0ConfigurationOfNewInspector, ConfigurationOfOCom= pletion,<br> > ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras,<br> > ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,<br> > ConfigurationOfShout , and......ConfigurationOfPharo!!!<br> ><br> > To install them, just download that package and evaluate the load. Exa= mple:<br> ><br> > Gofer new<br> > =A0 =A0 squeaksource: 'MetacelloRepository';<br> > =A0 =A0 package: 'ConfigurationOfShout';<br> > =A0 =A0 load.<br> ><br> > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0')= load.<br> ><br> > And then, you can also for exaple do:<br> ><br> > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0')= load: 'Core'<br> ><br> > this doesn't install the tests.<br> ><br> > Or for example: =A0(ConfigurationOfOmniBrowser project version: '1= .0') load:<br> > 'Dev'<br> ><br> > etc...<br> ><br> > So, you can load any project and with the group you want. All of that = can be<br> > (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 c= ode,<br> > load the different groups and give me feedback on the dependencies or<= br> > whatever.<br> ><br> > I really wait your feedback.<br> ><br> > Mariano<br> ><br> > ps: =A0I will release soon the first dev image using this :)<br> ><br> ><br> </div></div>> (Sorry for the long email)<br><br>Yes, after a= couple of weeks, I have writ=3D<br> > ten most of the needed Metacello configurations for the Dev images 1.0= . For=3D<br> > get 1.1 for a while. Now we are able to:<br><br>1) Load st= able version of p=3D<br> > ackages<br><br> > 2) Manage the dependencies automatically<br>3) Each developer ca= n create it=3D<br> > s custom PharoDev image<br><br> > 4) Flexibility to load the packages you want<br>5) Choose the br= owser for e=3D<br> > xample: OB or O2<br>6) Choose to load the tests or not<br>= 7) Load each pack=3D<br> > age in a PharoCore image without having to install anything else (all = the d=3D<br> > ependencies should be managed automatically)<br><br> ><br> > 8) You can take a PharoCore image and "transform" it= to a Dev ima=3D<br> > ge, or even web. <br>9) Others...<br><br>This is not= completed yet. There a=3D<br> <div class=3D"im">> re some things that we are discussing with Dale, but= they are ok as a first=3D<br> </div>> =A0step. I rather go step by step. <br><br> > <br>What I did is to create all the infrastructure:<br><= ;br>a) The Configura=3D<br> > tion classes<br>b) The dependencies <br><br> > c)=3DA0 the groups,<br><br>In summary, most of the &qu= ot;structure" and =3D<br> > static information. However, I am not sure which version to load of ea= ch pa=3D<br> > ckage. I will probable take care of building the Dev images, but I won= '=3D<br> > t:<br><br> ><br> > <br>- Merge anything. It will not be my task to merge OB, or RB = or whatever=3D<br> > .<br>- Check every version of each package before doing a releas= e to see if=3D<br> > =A0it is stable or not.<br><br>So...what I REALLY (actuall= y, WE) need is that=3D<br> <div class=3D"im">> =A0each developer, each maintainer of the packages t= hat we load of a PharoDev=3D<br> > =A0image, help us to create the stable versions. To create a new versi= on for =3D<br> </div>> the Metacello configuration is VERY easy, The hard part is alrea= dy done. Yo=3D<br> <div class=3D"im">> u just have to create a method and say which version= s (except you create or=3D<br> </div>> =A0eliminate packages or dependencies). If you read the code, yo= u will probab=3D<br> > ly understand it. However, you can read the Metacello tutorial (no mor= e tha=3D<br> > n one hour), or ask me or even more in the Metacello mailing list. So.= ..PLE=3D<br> > ASE, I need the help of the maintainers to create the versions. So far= , I c=3D<br> > reated the first version (1.0) with the latest version. But the idea i= s tha=3D<br> > t then you create 1.1.1 or 1.2 or whatever you consider.<br><br> > <br>All the configurations can be found in <a href=3D3D"= <a href=3D"http://www.squeaksour" target=3D"_blank">http://www.squeaksour</= a>=3D<br> > <a href=3D"http://ce.com/MetacelloRepository" target=3D"_blank">ce.com= /MetacelloRepository</a>"><a href=3D"http://www.squeaksource.com/Me= tacelloRepository=3D" target=3D"_blank">http://www.squeaksource.com/Metacel= loRepository=3D</a><br>
> </a><br><br>So far, I created:=3DA0 ConfigurationOfN= ewInspector, Configuratio=3D<br> > nOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphi= cExtr=3D<br> > as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, Conf= igura=3D<br> > tionOfShout , and......ConfigurationOfPharo!!!<br><br> > <br>To install them, just download that package and evaluate the= load. Exam=3D<br> > ple:<br><br>Gofer new<br>=3DA0=3DA0=3DA0 squeaksourc= e: 'MetacelloRepository&#=3D<br> > 39;;<br>=3DA0=3DA0=3DA0 package: 'ConfigurationOfShout&a= mp;#39;;<br>=3DA0=3DA0=3DA0 loa=3D<br> > d.<br><br>((Smalltalk at: #ConfigurationOfShout) project v= ersion: '1.0&=3D<br> > #39;) load.<br><br> > <br>And then, you can also for exaple do:=3DA0 <br><br&= gt;<br> > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0&a= mp;#39;) load=3D<br> > : 'Core'=3DA0 <br>this doesn't install t= he tests. <br><br>Or for =3D<br> > example:=3DA0 (ConfigurationOfOmniBrowser project version: '1.= 0') loa=3D<br> > d: 'Dev'<br><br> > <br>etc...<br><br>So, you can load any project and w= ith the group you want.=3D<br> <div class=3D"im">> =A0All of that can be (or should be hahahaha) perfec= tly loaded in a 1.0 Core =3D<br> </div>> image.<br><br>What I would really appreciate is if e= ach maintainer can look=3D<br> > =A0at the code, load the different groups and give me feedback on the = depende=3D<br> > ncies or whatever.<br><br> > <br>I really wait your feedback. <br><br>Mariano<= br><br>ps:=3DA0 I will relea=3D<br> > se soon the first dev image using this :)<br><br> > <br><br> <div><div></div><div class=3D"h5">><br> ><br> ><br> ><br> > _______________________________________________<br> > Pharo-project mailing list<br> > <a href=3D"mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@l=
ists.gforge.inria.fr</a><br> >
<a href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo= -project" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/li= stinfo/pharo-project</a><br> <br> <br> <br> <br> _______________________________________________<br> Pharo-project mailing list<br> <a href=3D"mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.=
gforge.inria.fr</a><br> <a
href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-proj= ect" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinf= o/pharo-project</a><br> </div></div></blockquote></div><br>
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project