Alex, could you try this?

Doru

On Tue, Oct 16, 2012 at 4:03 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:

        first you take a Moose version
        and you snapshot it, it will create a new script in MooseConfiguration.

        then you version the MooseConfiguration

        then in a 1.4 image you reload reloader and ask reloader to use the MooseConfiguration and to reload the script you created.

Stef

PS: by the end of the week SmalltalkHub will up port private and projects so we will be able to move reloader there and avoid to fork it.
Alex create an account on smalltalkhub and I will give you write access to reloader.



> Hi!
>
> I am not sure how I can load using Reloader. I've tried:
>
> Reloader new
>       repositoryClass: MooseConfigurationRepository;
>       reload: 3
>
> What exactly should I provide as argument to reload: ?
> MooseConfigurationRepository defines script1, script2 and script3.
> I though that providing 3 will load script3.
>
> Cheers,
> Alexandre
>
>
>
> On Oct 16, 2012, at 3:05 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
>
>> Hi,
>>
>> On 16 Oct 2012, at 00:12, Alexandre Bergel <alexandre.bergel@me.com> wrote:
>>
>>> Yes, I am interested in this!
>>
>> Thanks.
>>
>>> However the tasks you mentions are highly time consuming...
>>
>> So, what does that mean? :)
>>
>> Here is a possible start: take MooseReloader and see if you can reproduce the current image:
>> http://www.smalltalkhub.com/#!/~StephaneDucasse/MooseReloader
>>
>>
>>
>> Doru
>>
>>
>>> Alexandre
>>>
>>>
>>> On Oct 15, 2012, at 3:28 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have to think about releasing Moose 4.7 and moving to Pharo 2.0.
>>>>
>>>> There are several reasons why the move to 2.0 would make sense:
>>>> 1. Athens is coming. We have a major interest in this technology and we need to get on it as soon as possible.
>>>> 2. The environment moved to RPackage entirely.
>>>> 3. Pharo needs users.
>>>>
>>>> Before moving to Pharo 2.0, we need to release a robust 4.7. There are still some open points:
>>>> http://code.google.com/p/moose-technology/issues/list?can=2&q=milestone%3D4.7
>>>>
>>>> The most pressing ones are:
>>>> Issue 799: Editing code in Glamour must be faster
>>>> Issue 851: Create a stable version for Moose and all its subparts
>>>> Issue 853: ConfigurationOfMoose should be split to reflect core vs suite
>>>>
>>>> Another area to look into is the cleaning of the FAMIX navigation. Right now it's a mess in there. We should probably remove most of the hardcoded methods and rely on Chef. Any taker?
>>>>
>>>> My idea is to target a release this year. Input is more than welcome :)
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Every thing has its own flow"
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev@iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev@iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "Next time you see your life passing by, say 'hi' and get to know her."
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev@iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>


_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
www.tudorgirba.com

"Every thing has its own flow"