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

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
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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

_______________________________________________
Pharo-project mailing list
[hidden email]
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________

Pharo-project mailing list
[hidden email]
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 <[hidden email]> 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
> > [hidden email]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
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 <[hidden email]>
> 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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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" <[hidden email]> wrote:

| ----- "Alexandre Bergel" <[hidden email]> 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
| [hidden email]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project