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
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
