[Pharo-project] [ANN] Metacello configurations for Pharo.
(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 :)
On Thu, Jan 7, 2010 at 9:54 PM, Mariano Martinez Peck <marianopeck@gmail.com
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 :)
Excellent work Mariano! Dale ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | On Thu, Jan 7, 2010 at 9:54 PM, Mariano Martinez Peck | <marianopeck@gmail.com | > 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 :) | > | >
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'? Next week I will work on OB with David. I really like his browser, but there are many bugs still... 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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Thu, Jan 7, 2010 at 10:04 PM, Alexandre Bergel <alexandre@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.
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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Jan 7, 2010, at 10:13 PM, Mariano Martinez Peck wrote:
On Thu, Jan 7, 2010 at 10:04 PM, Alexandre Bergel <alexandre@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@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@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
On Thu, Jan 7, 2010 at 10:28 PM, Stéphane Ducasse <stephane.ducasse@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@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@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@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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi, if you can give me a script to load the stable (blessed?) version of ConfigurationOfPharo I will try and add it to the interim build server. Also it would be ideal to have conditional logic such that the image knows if such an 'update' is present or not. That way the server goes to sleep otherwise. we would then have an update stream of sorts for Pharo. cheers, Mike
On Thu, Jan 7, 2010 at 10:11 PM, Michael Roberts <mike@mjr104.co.uk> wrote:
Hi,
if you can give me a script to load the stable (blessed?) version of ConfigurationOfPharo I will try and add it to the interim build server.
Sure. Take the latest PharoCore 10505 image and evaluate Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0-rc2.10505') load. With that you create a the standard Dev image for the moment. I invite you to see the method ConfigurationOfPharo >> baseline10rc2: At the end, you can see the groups I defined: group: 'default' with: #('DevImageStandardOB'); group: 'Pharo Extras' with: #('PharoSound' 'PharoMorphicExtras' 'ArchiveViewer'); group: 'Dev Tools' with: #('RoelTyper' 'NewInspector' 'Shout' 'OCompletion'); group: 'Dev Tools Tests' with: #('Shout Tests' 'OCompletion Tests'); group: 'Dev Tools OB' with: #('Dev Tools' 'OB Dev'); group: 'Dev Tools OB Tests' with: #('Dev Tools Tests' 'OB Dev Tests'); group: 'DevImageStandardOBWithoutTests' with: #('Dev Tools OB' 'Pharo Extras' 'ImageForDevelopers-pharo'); group: 'DevImageStandardOB' with: #('Dev Tools OB Tests' 'DevImageStandardOBWithoutTests'); The group is what you put after the load: If you just send the message load, it takes the default. However, you can evaluate something like this: ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0-rc2.10505') load: 'Dev Tools' or even: ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0-rc2.10505') load: #('Dev Tools' 'Pharo Extras' ) Of course these groups were just my ideas, but we can create as much as we need. Cheers Mariano
Also it would be ideal to have conditional logic such that the image knows if such an 'update' is present or not. That way the server goes to sleep otherwise. we would then have an update stream of sorts for Pharo.
cheers, Mike
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Thu, Jan 7, 2010 at 10:33 PM, Alexandre Bergel <alexandre@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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).
Excellent!
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.
Yes, I perfectly guessed this. alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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.
yep, that's true. Currently I'm alpha-testing it and writing some tests and documentation, but now you can do things like: Loader new list. "Lists all available projects, scanning all repositories" Loader new search: 'Blah'. "Looks for project Blah scanning all repositories. 'Blah' can be a segment, not just a full name" Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah." Loader new load: 'Blah' version: '1.0'. "Load '1.0' version of ConfigurationOfBlah." Loader new managed. "Answers a list of current managed projects." Loader new update. "Updates configurations for all managed projects." Loader new update: 'Blah'. "Updates ConfigurationOfBlah." Loader new upgrade. "Upgrades all managed project to a newest version (if present)". Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest version (if present)". You can specify permanent repositories by executing: Loader repository: 'http://myownrepo/project'. Loader repository: 'http://myownrepo/project' username: 'myself' password: 'secret'. (this acts as adding universes to apt-get of debian) And you can use "temporal" repositories: Loader new repository: 'http://myownrepo/project'; load: 'Blah'. This repostories are dropped after use it, but any managed project keeps it for future managing. I hope this will solve all the loading issues. In the future, you could do just: Loader new load: 'Pharo'. and get a full PharoDev image :) Cheers, Esteban
Loader new load: 'Pharo'. and get a full PharoDev image :)
Wonderful! -- Miguel Cobá http://miguel.leugim.com.mx
Esteban, this is excellent!! It would be cool to have Loader new infoAbout: 'ProjectName' Alexandre On 7 Jan 2010, at 20:45, Esteban Lorenzano wrote:
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.
yep, that's true. Currently I'm alpha-testing it and writing some tests and documentation, but now you can do things like:
Loader new list. "Lists all available projects, scanning all repositories" Loader new search: 'Blah'. "Looks for project Blah scanning all repositories. 'Blah' can be a segment, not just a full name" Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah." Loader new load: 'Blah' version: '1.0'. "Load '1.0' version of ConfigurationOfBlah." Loader new managed. "Answers a list of current managed projects." Loader new update. "Updates configurations for all managed projects." Loader new update: 'Blah'. "Updates ConfigurationOfBlah." Loader new upgrade. "Upgrades all managed project to a newest version (if present)". Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest version (if present)".
You can specify permanent repositories by executing:
Loader repository: 'http://myownrepo/project'. Loader repository: 'http://myownrepo/project' username: 'myself' password: 'secret'.
(this acts as adding universes to apt-get of debian)
And you can use "temporal" repositories: Loader new repository: 'http://myownrepo/project'; load: 'Blah'.
This repostories are dropped after use it, but any managed project keeps it for future managing.
I hope this will solve all the loading issues. In the future, you could do just:
Loader new load: 'Pharo'. and get a full PharoDev image :)
Cheers, Esteban
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
A description that could be obtained from the last commit comment for example. Or/and the squeaksource description. Cheers, Alexandre On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote:
Hi, And what info do you think it should answer?
On 2010-01-08 09:39:31 -0300, Alexandre Bergel <alexandre@bergel.eu> said:
Esteban, this is excellent!! It would be cool to have
Loader new infoAbout:
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
ok, I'll try something like this: Loader new descriptionOf: 'Blah'. "Answers the #description metacello tag for current version" Loader new descriptionOf: 'Blah' version: '1.0'. "Answers the #description metacello tag for 1.0 version" do you think this is enough? cheers, Esteban On 2010-01-08 10:26:06 -0300, Alexandre Bergel <alexandre@bergel.eu> said:
A description that could be obtained from the last commit comment for example. Or/and the squeaksource description.
Cheers, Alexandre
On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote:
Hi, And what info do you think it should answer?
On 2010-01-08 09:39:31 -0300, Alexandre Bergel <alexandre@bergel.eu> said:
Esteban, this is excellent!! It would be cool to have
Loader new infoAbout:
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Loader new descriptionOf: 'Blah'. "Answers the #description metacello tag for current version" Loader new descriptionOf: 'Blah' version: '1.0'. "Answers the #description metacello tag for 1.0 version"
do you think this is enough?
I do not feel so, but this is a good start. You had an excellent initiative. Cheers, Alexandre
On 2010-01-08 10:26:06 -0300, Alexandre Bergel <alexandre@bergel.eu> said:
A description that could be obtained from the last commit comment for example. Or/and the squeaksource description.
Cheers, Alexandre
On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote:
Hi, And what info do you think it should answer?
On 2010-01-08 09:39:31 -0300, Alexandre Bergel <alexandre@bergel.eu> said:
Esteban, this is excellent!! It would be cool to have
Loader new infoAbout:
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Esteban
From a vocabulary point of view could loader be an extension of Gofer? Because we have Gofer, metacello, and keeping the list to the minimum would be cool.
Gofer configuration list GoferConfigurationLoader list ?? Stef
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.
yep, that's true. Currently I'm alpha-testing it and writing some tests and documentation, but now you can do things like:
Loader new list. "Lists all available projects, scanning all repositories" Loader new search: 'Blah'. "Looks for project Blah scanning all repositories. 'Blah' can be a segment, not just a full name" Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah." Loader new load: 'Blah' version: '1.0'. "Load '1.0' version of ConfigurationOfBlah." Loader new managed. "Answers a list of current managed projects." Loader new update. "Updates configurations for all managed projects." Loader new update: 'Blah'. "Updates ConfigurationOfBlah." Loader new upgrade. "Upgrades all managed project to a newest version (if present)". Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest version (if present)".
You can specify permanent repositories by executing:
Loader repository: 'http://myownrepo/project'. Loader repository: 'http://myownrepo/project' username: 'myself' password: 'secret'.
(this acts as adding universes to apt-get of debian)
And you can use "temporal" repositories: Loader new repository: 'http://myownrepo/project'; load: 'Blah'.
This repostories are dropped after use it, but any managed project keeps it for future managing.
I hope this will solve all the loading issues. In the future, you could do just:
Loader new load: 'Pharo'. and get a full PharoDev image :)
Cheers, Esteban
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
of course ;) but now I'm going on vacations (after two years without any vacation at all)... When I came back, I will refactor everything as GoferConfigurationLoader, and adding "Gofer configuration" protocol. Cheers, Esteban pd: maybe 'Gofer project' is better than 'Gofer configuration', what do you think? On 2010-01-08 12:56:09 -0300, Stéphane Ducasse <Stephane.Ducasse@inria.fr> said:
Esteban
From a vocabulary point of view could loader be an extension of Gofer? Because we have Gofer, metacello, and keeping the list to the minimum would be cool.
Gofer configuration list GoferConfigurationLoader list
??
Stef
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.
yep, that's true. Currently I'm alpha-testing it and writing some tests and documentation, but now you can do things like:
Loader new list. "Lists all available projects, scanning all repositories" Loader new search: 'Blah'. "Looks for project Blah scanning all repositories. 'Blah' can be a segment, not just a full name" Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah." Loader new load: 'Blah' version: '1.0'. "Load '1.0' version of ConfigurationOfBlah." Loader new managed. "Answers a list of current managed projects." Loader new update. "Updates configurations for all managed projects." Loader new update: 'Blah'. "Updates ConfigurationOfBlah." Loader new upgrade. "Upgrades all managed project to a newest version (if present)". Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest version (if present)".
You can specify permanent repositories by executing:
Loader repository: 'http://myownrepo/project'. Loader repository: 'http://myownrepo/project' username: 'myself' password: 'secret'.
(this acts as adding universes to apt-get of debian)
And you can use "temporal" repositories: Loader new repository: 'http://myownrepo/project'; load: 'Blah'.
This repostories are dropped after use it, but any managed project keeps it for future managing.
I hope this will solve all the loading issues. In the future, you could do just:
Loader new load: 'Pharo'. and get a full PharoDev image :)
Cheers, Esteban
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
pd: maybe 'Gofer project' is better than 'Gofer configuration', what do you think?
I think so. Alexandre
On 2010-01-08 12:56:09 -0300, Stéphane Ducasse <Stephane.Ducasse@inria.fr> said:
Esteban
From a vocabulary point of view could loader be an extension of Gofer? Because we have Gofer, metacello, and keeping the list to the minimum would be cool.
Gofer configuration list GoferConfigurationLoader list
??
Stef
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.
yep, that's true. Currently I'm alpha-testing it and writing some tests and documentation, but now you can do things like:
Loader new list. "Lists all available projects, scanning all repositories" Loader new search: 'Blah'. "Looks for project Blah scanning all repositories. 'Blah' can be a segment, not just a full name" Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah." Loader new load: 'Blah' version: '1.0'. "Load '1.0' version of ConfigurationOfBlah." Loader new managed. "Answers a list of current managed projects." Loader new update. "Updates configurations for all managed projects." Loader new update: 'Blah'. "Updates ConfigurationOfBlah." Loader new upgrade. "Upgrades all managed project to a newest version (if present)". Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest version (if present)".
You can specify permanent repositories by executing:
Loader repository: 'http://myownrepo/project'. Loader repository: 'http://myownrepo/project' username: 'myself' password: 'secret'.
(this acts as adding universes to apt-get of debian)
And you can use "temporal" repositories: Loader new repository: 'http://myownrepo/project'; load: 'Blah'.
This repostories are dropped after use it, but any managed project keeps it for future managing.
I hope this will solve all the loading issues. In the future, you could do just:
Loader new load: 'Pharo'. and get a full PharoDev image :)
Cheers, Esteban
_______________________________________________ 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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
----- "Alexandre Bergel" <alexandre@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. Alexandre, How about something like the following expressions: Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. Gofer loadConfiguration: 'NewInspector'. Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' 'Magritte-Tests' ). Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'. I whipped together some extension methods for Gofer that adds support for the above to Gofer: Gofer new gemsource: 'metacello'; package: 'Metacello-Gofer-Extensions'; load. If there is no leading ConfigurationOf in the configuration name, 'ConfigurationOf' is tacked on. If no version is specified (or is nil) the latest version of the configuration is loaded. If no explicit load list is supplied (or is nil), then the default load list is loaded. In all cases it is expected that the configuration will be found in the MetacelloRepository on SqueakSource... Dale
haha, I see that Esteban has gone much farther towards creating a set of tools that go way beyond the simple loading of a configuration ... Dale ----- "Dale Henrichs" <dale.henrichs@gemstone.com> wrote: | ----- "Alexandre Bergel" <alexandre@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. | | Alexandre, | | How about something like the following expressions: | | Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. | Gofer loadConfiguration: 'NewInspector'. | Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' | 'Magritte-Tests' ). | Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'. | | I whipped together some extension methods for Gofer that adds support | for the above to Gofer: | | Gofer new | gemsource: 'metacello'; | package: 'Metacello-Gofer-Extensions'; | load. | | If there is no leading ConfigurationOf in the configuration name, | 'ConfigurationOf' is tacked on. If no version is specified (or is nil) | the latest version of the configuration is loaded. If no explicit load | list is supplied (or is nil), then the default load list is loaded. In | all cases it is expected that the configuration will be found in the | MetacelloRepository on SqueakSource... | | Dale | | _______________________________________________ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
This is getting cool: Interdim build server, Hudson integration, Metacello, Loader, new Sunit extension and refactorm etc ......excellent !!! On Fri, Jan 8, 2010 at 12:51 AM, Dale Henrichs <dale.henrichs@gemstone.com>wrote:
haha, I see that Esteban has gone much farther towards creating a set of tools that go way beyond the simple loading of a configuration ...
Dale
----- "Dale Henrichs" <dale.henrichs@gemstone.com> wrote:
| ----- "Alexandre Bergel" <alexandre@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. | | Alexandre, | | How about something like the following expressions: | | Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. | Gofer loadConfiguration: 'NewInspector'. | Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' | 'Magritte-Tests' ). | Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'. | | I whipped together some extension methods for Gofer that adds support | for the above to Gofer: | | Gofer new | gemsource: 'metacello'; | package: 'Metacello-Gofer-Extensions'; | load. | | If there is no leading ConfigurationOf in the configuration name, | 'ConfigurationOf' is tacked on. If no version is specified (or is nil) | the latest version of the configuration is loaded. If no explicit load | list is supplied (or is nil), then the default load list is loaded. In | all cases it is expected that the configuration will be found in the | MetacelloRepository on SqueakSource... | | Dale | | _______________________________________________ | 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
How about something like the following expressions:
I feel the notion of Configuration unnecessary.
Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'.
Gofer load: 'Pharo' version: '1.0-rc2.10505'. is shorter
Gofer loadConfiguration: 'NewInspector'.
Gofer load: 'NewInspector'
Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' 'Magritte-Tests' ).
Gofer forProject: 'Magritte' loadClassCategories: #( 'Magritte-Model' 'Magritte-Tests' ).
Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'.
Gofer forProject: 'OmniBrowser' loadConfiguration: 'Core' version: '1.0'
In all cases it is expected that the configuration will be found in the MetacelloRepository on SqueakSource...
Shall I move ConfigurationOfMondrian from Mondrian to MetacelloRepository? I have no problem in doing so. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Alexandre, Thanks for the feedback, my little set of extensions were meant as a proof of concept. Esteban's Loader provides a similar API with many more features, so I'll let my experiment rest for the time being. By all means add your configuration to MetacelloRepository. Dale ----- "Alexandre Bergel" <alexandre@bergel.eu> wrote: | > How about something like the following expressions: | | I feel the notion of Configuration unnecessary. | | > Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. | | Gofer load: 'Pharo' version: '1.0-rc2.10505'. | is shorter | | > Gofer loadConfiguration: 'NewInspector'. | | Gofer load: 'NewInspector' | | > Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' | > 'Magritte-Tests' ). | | Gofer forProject: 'Magritte' loadClassCategories: #( 'Magritte-Model' | | 'Magritte-Tests' ). | | > Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: | 'Core'. | | Gofer forProject: 'OmniBrowser' loadConfiguration: 'Core' version: | '1.0' | | > In all cases it is expected that the configuration will be found in | | > the MetacelloRepository on SqueakSource... | | Shall I move ConfigurationOfMondrian from Mondrian to | MetacelloRepository? I have no problem in doing so. | | Alexandre | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
By all means add your configuration to MetacelloRepository.
I added the one for which I am involved. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Alexandre,
How about something like the following expressions:
Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. Gofer loadConfiguration: 'NewInspector'. Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' 'Magritte-Tests' ). Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'.
sounds good.
I whipped together some extension methods for Gofer that adds support for the above to Gofer:
Gofer new gemsource: 'metacello'; package: 'Metacello-Gofer-Extensions'; load.
If there is no leading ConfigurationOf in the configuration name, 'ConfigurationOf' is tacked on. If no version is specified (or is nil) the latest version of the configuration is loaded. If no explicit load list is supplied (or is nil), then the default load list is loaded. In all cases it is expected that the configuration will be found in the MetacelloRepository on SqueakSource...
Dale
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Great! On Jan 7, 2010, at 22:19 , Mariano Martinez Peck wrote:
On Thu, Jan 7, 2010 at 10:11 PM, Michael Roberts <mike@mjr104.co.uk> wrote:
Hi,
if you can give me a script to load the stable (blessed?) version of ConfigurationOfPharo I will try and add it to the interim build server.
Sure. Take the latest PharoCore 10505 image and evaluate
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
((Smalltalk at: #ConfigurationOfPharo) project version: '1.0- rc2.10505') load.
In a 10505 image I get the following warning: This package depends on the following classes: OBCodeBrowser OBCommand You must resolve these dependencies before you will be able to load these definitions: OBCmdMetacello OBCmdMetacello>>chooseVersion:message: OBCmdMetacello>>commitPackageSpec:into:with: OBCmdMetacello>>currentVersion ...etc Cheers, Adrian
On Thu, Jan 7, 2010 at 10:47 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Great!
On Jan 7, 2010, at 22:19 , Mariano Martinez Peck wrote:
On Thu, Jan 7, 2010 at 10:11 PM, Michael Roberts <mike@mjr104.co.uk> wrote:
Hi,
if you can give me a script to load the stable (blessed?) version of ConfigurationOfPharo I will try and add it to the interim build server.
Sure. Take the latest PharoCore 10505 image and evaluate
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
((Smalltalk at: #ConfigurationOfPharo) project version: '1.0- rc2.10505') load.
In a 10505 image I get the following warning:
This package depends on the following classes: OBCodeBrowser OBCommand You must resolve these dependencies before you will be able to load these definitions: OBCmdMetacello OBCmdMetacello>>chooseVersion:message: OBCmdMetacello>>commitPackageSpec:into:with: OBCmdMetacello>>currentVersion ...etc
Thanks for reporting Adrian. I should have told about that. That's something with Metacello that when it ensure that Metacello is installed, it tries to install a version that has not only the core but also all the tools. Those tools depends on OB...so.But Metacello in itself is working, no problem. I gave the idea to Dale last week to change this so that ensureMetacello just loads the core (without tools) and he was agree. So I hope next Metacello version will have this and that warning will disappear. Even more...it has already been fixed: http://code.google.com/p/metacello/issues/detail?id=33&can=1&q=ensureMetacel... cheers Mariano ps: There is another version about some tests...sorry, those are the OB tests (BogusTestCase) and I don't know why it depends on soemthing I don't know what it is...if someone can help me :)
Cheers, Adrian
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
ps: There is another version about some tests...sorry, those are the OB tests (BogusTestCase) and I don't know why it depends on soemthing I don't know what it is...if someone can help me :)
Yes I got this message on a 10504 rc1 PharoCore. Other than that, the process went ok. Good job. -- Miguel Cobá http://miguel.leugim.com.mx
----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | ps: There is another version about some tests...sorry, those are the | OB | tests (BogusTestCase) and I don't know why it depends on soemthing I | don't | know what it is...if someone can help me :) The package BogusInfo is required for OB-Tests-Standard (it's an Umbrella package that loads Bogus and BogusExt which contain the mock classes used by the tests)...I've update ConfigurationOfOmniBrowser with the information for BogusInfo which should fix the problem ... a load of just the 'Core Tests' into a 10502 dev image worked without complaint. Dale
Wonderful news Mariano! This will ease the usage of Pharo in ways unseen before. Thanks. -- Miguel Cobá http://miguel.leugim.com.mx
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 "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
This seems correct. The naming convention is: - "Pharo" for PharoCore + dev tools - "PharoCore" is the base Pharo image Adrian On Jan 8, 2010, at 13:12 , Esteban Lorenzano wrote:
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 "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
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
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
El vie, 08-01-2010 a las 13:48 +0100, Mariano Martinez Peck escribió:
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)
I'm writing the metacello config for Magma. I suppose that the same applies here. a group for Client, a group for Server and a group for Tester. all of them defined in ConfigurationOfMagma. right? BTW. How did you compute dependencies in packages you aren't completely aware of the details. I remember a tool for this. Where can I find them? Cheers
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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
BTW. How did you compute dependencies in packages you aren't completely aware of the details. I remember a tool for this. Where can I find them?
I found this: http://cs.hernanmorales.com.ar/projects/dependencyBrowser/DBrowser-en.php that appears to be the one you are using. -- Miguel Cobá http://miguel.leugim.com.mx
2010/1/12 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El vie, 08-01-2010 a las 13:48 +0100, Mariano Martinez Peck escribió:
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)
I'm writing the metacello config for Magma. I suppose that the same applies here.
a group for Client, a group for Server and a group for Tester. all of them defined in ConfigurationOfMagma.
right?
Yes. You can also create groups from others groups. For example you may want a client and the test, so, you can create another groups that brings both. However it is not NECESSARY as you can always do: (ConfigOfXX project version: 'YYY' ) load: 'aGroup' or: (ConfigOfXX project version: 'YYY' ) load: #('aGroup' 'anotherGroup').
BTW. How did you compute dependencies in packages you aren't completely aware of the details. I remember a tool for this. Where can I find them?
you found it :)
Cheers
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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- 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
----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | So far, I created: ConfigurationOfNewInspector, | ConfigurationOfOCompletion, | ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, | ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, | ConfigurationOfShout , and......ConfigurationOfPharo!!! Mariano, I'm working on a ConfigurationOfOmneBrowser that works on both Squeak and Pharo (and ultimately GemStone ...). Would you prefer that I start a new baseline/version or just overwrite 1.0? I lean towards overwriting, especially this early in the process, but I want your opinion. Dale
On Sat, Jan 9, 2010 at 12:47 AM, Dale Henrichs <dale.henrichs@gemstone.com>wrote:
----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote:
| So far, I created: ConfigurationOfNewInspector, | ConfigurationOfOCompletion, | ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, | ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, | ConfigurationOfShout , and......ConfigurationOfPharo!!!
Mariano,
I'm working on a ConfigurationOfOmneBrowser that works on both Squeak and Pharo (and ultimately GemStone ...).
Would you prefer that I start a new baseline/version or just overwrite 1.0?
Hi Dale. Good we are working in OB. This weekend / next-week I want to create a PharoDev image with OB so maybe I would rather if you can create a new baseline (taking 1.0 as a base) and if you want, later we can "merge" if necessary. What do you think ? Is this ok for you ?
I lean towards overwriting, especially this early in the process, but I want your opinion.
Dale
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
just fine..thanks ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | On Sat, Jan 9, 2010 at 12:47 AM, Dale Henrichs | <dale.henrichs@gemstone.com>wrote: | | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | So far, I created: ConfigurationOfNewInspector, | > | ConfigurationOfOCompletion, | > | ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, | > | ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, | > | ConfigurationOfShout , and......ConfigurationOfPharo!!! | > | > Mariano, | > | > I'm working on a ConfigurationOfOmneBrowser that works on both | Squeak and | > Pharo (and ultimately GemStone ...). | > | > Would you prefer that I start a new baseline/version or just | overwrite 1.0? | > | > | Hi Dale. Good we are working in OB. This weekend / next-week I want | to | create a PharoDev image with OB so maybe I would rather if you can | create a | new baseline (taking 1.0 as a base) and if you want, later we can | "merge" if | necessary. | | What do you think ? Is this ok for you ? | | | > I lean towards overwriting, especially this early in the process, | but I | > want your opinion. | > | > Dale | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | >
Dale: after some discussions in Pharo mailing list, the community wants to use the Lukas repository for OB instead of wiresong. I don't know the impact it makes to you, and I don't know the best way to manage this kind of situations. Right now, I create a new version and baselind to ConfigurationOfOmniBrowser that maps to Lukas repo and I change a little the dependencies, and, of course, the versions. Any thougths about this? Cheers Mariano On Sat, Jan 9, 2010 at 1:17 AM, Dale Henrichs <dale.henrichs@gemstone.com>wrote:
just fine..thanks ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote:
| On Sat, Jan 9, 2010 at 12:47 AM, Dale Henrichs | <dale.henrichs@gemstone.com>wrote: | | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | So far, I created: ConfigurationOfNewInspector, | > | ConfigurationOfOCompletion, | > | ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, | > | ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, | > | ConfigurationOfShout , and......ConfigurationOfPharo!!! | > | > Mariano, | > | > I'm working on a ConfigurationOfOmneBrowser that works on both | Squeak and | > Pharo (and ultimately GemStone ...). | > | > Would you prefer that I start a new baseline/version or just | overwrite 1.0? | > | > | Hi Dale. Good we are working in OB. This weekend / next-week I want | to | create a PharoDev image with OB so maybe I would rather if you can | create a | new baseline (taking 1.0 as a base) and if you want, later we can | "merge" if | necessary. | | What do you think ? Is this ok for you ? | | | > I lean towards overwriting, especially this early in the process, | but I | > want your opinion. | > | > Dale | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | >
Mariano, That's just fine ... make the changes that you need to make and I'll adapt that configuration for GLASS and Squeak (Gemtools). Dale ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | Dale: after some discussions in Pharo mailing list, the community | wants to | use the Lukas repository for OB instead of wiresong. | | I don't know the impact it makes to you, and I don't know the best way | to | manage this kind of situations. | | Right now, I create a new version and baselind to | ConfigurationOfOmniBrowser that maps to Lukas repo and I change a | little | the dependencies, and, of course, the versions. | | Any thougths about this? | | Cheers | | Mariano | | On Sat, Jan 9, 2010 at 1:17 AM, Dale Henrichs | <dale.henrichs@gemstone.com>wrote: | | > just fine..thanks | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | On Sat, Jan 9, 2010 at 12:47 AM, Dale Henrichs | > | <dale.henrichs@gemstone.com>wrote: | > | | > | > | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | > | > | So far, I created: ConfigurationOfNewInspector, | > | > | ConfigurationOfOCompletion, | > | > | ConfigurationOfOmniBrowser, | ConfigurationOfPharoMorphicExtras, | > | > | ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, | > | > | ConfigurationOfShout , and......ConfigurationOfPharo!!! | > | > | > | > Mariano, | > | > | > | > I'm working on a ConfigurationOfOmneBrowser that works on both | > | Squeak and | > | > Pharo (and ultimately GemStone ...). | > | > | > | > Would you prefer that I start a new baseline/version or just | > | overwrite 1.0? | > | > | > | > | > | Hi Dale. Good we are working in OB. This weekend / next-week I | want | > | to | > | create a PharoDev image with OB so maybe I would rather if you | can | > | create a | > | new baseline (taking 1.0 as a base) and if you want, later we can | > | "merge" if | > | necessary. | > | | > | What do you think ? Is this ok for you ? | > | | > | | > | > I lean towards overwriting, especially this early in the | process, | > | but I | > | > want your opinion. | > | > | > | > Dale | > | > | > | > _______________________________________________ | > | > Pharo-project mailing list | > | > Pharo-project@lists.gforge.inria.fr | > | > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > | >
On Mon, Jan 11, 2010 at 7:11 PM, Dale Henrichs <dale.henrichs@gemstone.com>wrote:
Mariano,
That's just fine ... make the changes that you need to make and I'll adapt that configuration for GLASS and Squeak (Gemtools).
Thanks Dale. And regardless my intention to let you know this so that it is all right with you, what do you think the way I am managing this ? So far, I create a new pair of baseline/version, but maybe you have a better idea. Cheers Mariano
Dale
----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote:
| Dale: after some discussions in Pharo mailing list, the community | wants to | use the Lukas repository for OB instead of wiresong. | | I don't know the impact it makes to you, and I don't know the best way | to | manage this kind of situations. | | Right now, I create a new version and baselind to | ConfigurationOfOmniBrowser that maps to Lukas repo and I change a | little | the dependencies, and, of course, the versions. | | Any thougths about this? | | Cheers | | Mariano | | On Sat, Jan 9, 2010 at 1:17 AM, Dale Henrichs | <dale.henrichs@gemstone.com>wrote: | | > just fine..thanks | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | On Sat, Jan 9, 2010 at 12:47 AM, Dale Henrichs | > | <dale.henrichs@gemstone.com>wrote: | > | | > | > | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | > | > | So far, I created: ConfigurationOfNewInspector, | > | > | ConfigurationOfOCompletion, | > | > | ConfigurationOfOmniBrowser, | ConfigurationOfPharoMorphicExtras, | > | > | ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, | > | > | ConfigurationOfShout , and......ConfigurationOfPharo!!! | > | > | > | > Mariano, | > | > | > | > I'm working on a ConfigurationOfOmneBrowser that works on both | > | Squeak and | > | > Pharo (and ultimately GemStone ...). | > | > | > | > Would you prefer that I start a new baseline/version or just | > | overwrite 1.0? | > | > | > | > | > | Hi Dale. Good we are working in OB. This weekend / next-week I | want | > | to | > | create a PharoDev image with OB so maybe I would rather if you | can | > | create a | > | new baseline (taking 1.0 as a base) and if you want, later we can | > | "merge" if | > | necessary. | > | | > | What do you think ? Is this ok for you ? | > | | > | | > | > I lean towards overwriting, especially this early in the | process, | > | but I | > | > want your opinion. | > | > | > | > Dale | > | > | > | > _______________________________________________ | > | > Pharo-project mailing list | > | > Pharo-project@lists.gforge.inria.fr | > | > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > | >
I think that refactoring the baseline so the common requirements are common and the specific requirements that differ are made conditional upon the platform. It is entirely possible that the bulk of the baseline will be common (differing only on which repository is used). then of course the version will be completely different for each platform. I'm working in thie area, so I think that I will create a sample baseline that you can look at and if it makes sense to you you can fold into the configuration. Dale ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | On Mon, Jan 11, 2010 at 7:11 PM, Dale Henrichs | <dale.henrichs@gemstone.com>wrote: | | > Mariano, | > | > That's just fine ... make the changes that you need to make and I'll | adapt | > that configuration for GLASS and Squeak (Gemtools). | > | > | Thanks Dale. And regardless my intention to let you know this so that | it is | all right with you, what do you think the way I am managing this ? | So far, I create a new pair of baseline/version, but maybe you have a | better | idea. | | Cheers | | Mariano | | | > Dale | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | Dale: after some discussions in Pharo mailing list, the community | > | wants to | > | use the Lukas repository for OB instead of wiresong. | > | | > | I don't know the impact it makes to you, and I don't know the best | way | > | to | > | manage this kind of situations. | > | | > | Right now, I create a new version and baselind to | > | ConfigurationOfOmniBrowser that maps to Lukas repo and I change | a | > | little | > | the dependencies, and, of course, the versions. | > | | > | Any thougths about this? | > | | > | Cheers | > | | > | Mariano | > | | > | On Sat, Jan 9, 2010 at 1:17 AM, Dale Henrichs | > | <dale.henrichs@gemstone.com>wrote: | > | | > | > just fine..thanks | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | > | > | > | > | On Sat, Jan 9, 2010 at 12:47 AM, Dale Henrichs | > | > | <dale.henrichs@gemstone.com>wrote: | > | > | | > | > | > | > | > | > ----- "Mariano Martinez Peck" <marianopeck@gmail.com> | wrote: | > | > | > | > | > | > | So far, I created: ConfigurationOfNewInspector, | > | > | > | ConfigurationOfOCompletion, | > | > | > | ConfigurationOfOmniBrowser, | > | ConfigurationOfPharoMorphicExtras, | > | > | > | ConfigurationOfPharoSound, | ConfigurationOfRefactoringBrowser, | > | > | > | ConfigurationOfShout , and......ConfigurationOfPharo!!! | > | > | > | > | > | > Mariano, | > | > | > | > | > | > I'm working on a ConfigurationOfOmneBrowser that works on | both | > | > | Squeak and | > | > | > Pharo (and ultimately GemStone ...). | > | > | > | > | > | > Would you prefer that I start a new baseline/version or | just | > | > | overwrite 1.0? | > | > | > | > | > | > | > | > | Hi Dale. Good we are working in OB. This weekend / next-week | I | > | want | > | > | to | > | > | create a PharoDev image with OB so maybe I would rather if | you | > | can | > | > | create a | > | > | new baseline (taking 1.0 as a base) and if you want, later we | can | > | > | "merge" if | > | > | necessary. | > | > | | > | > | What do you think ? Is this ok for you ? | > | > | | > | > | | > | > | > I lean towards overwriting, especially this early in the | > | process, | > | > | but I | > | > | > want your opinion. | > | > | > | > | > | > Dale | > | > | > | > | > | > _______________________________________________ | > | > | > Pharo-project mailing list | > | > | > Pharo-project@lists.gforge.inria.fr | > | > | > | > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > | > | > | > | >
participants (9)
-
Adrian Lienhard -
Alexandre Bergel -
Dale Henrichs -
Esteban Lorenzano -
Mariano Martinez Peck -
Michael Roberts -
Miguel Enrique Cobá Martinez -
Stéphane Ducasse -
Stéphane Ducasse