Moose on pharo 1.2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

Moose on pharo 1.2

Laval Jannik-2
I just tried to load Moose on pharo1.2

I only do this script (loading OB is not needed I think):

=====
Gofer new
                squeaksource: 'rb';
                package: 'AST-Core';
                package: 'Refactoring-Core';
                package: 'Refactoring-Critics';
                package: 'Refactoring-Environment';
                package: 'Refactoring-Spelling';
                package: 'Refactoring-Changes';
                load.

Gofer new
squeaksource: 'shout';
version: 'Shout-cyrille_delaunay.87';
package: 'ShoutWorkspace.1';
package: 'ShoutTests';
load.

Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfOmniBrowser';
load.
((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.

Gofer new
squeaksource: 'Moose';
package: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
=====

With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
So we do not save our work on moose repository.

What do we do for next steps ?
Do we change our Pharo system and go to 1.2 or working on 1.1 ?

Cheers,
---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Alexandre Bergel
We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.

Alexandre



On 20 Sep 2010, at 10:43, Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
> squeaksource: 'rb';
> package: 'AST-Core';
> package: 'Refactoring-Core';
> package: 'Refactoring-Critics';
> package: 'Refactoring-Environment';
> package: 'Refactoring-Spelling';
> package: 'Refactoring-Changes';
> load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

jannik laval
In reply to this post by Laval Jannik-2
Hi guys,

It is not so easy to load Moose on Pharo1.2 :)
There are two deprecated call during the loading. This is due to FileSystem, we cannot change the source code on the repository.

====
Gofer new
                squeaksource: 'rb';
                package: 'AST-Core';
                package: 'Refactoring-Core';
                package: 'Refactoring-Critics';
                package: 'Refactoring-Environment';
                package: 'Refactoring-Spelling';
                package: 'Refactoring-Changes';
                load.

Gofer new
squeaksource: 'shout';
version: 'Shout-cyrille_delaunay.87';
package: 'ShoutWorkspace.1';
package: 'ShoutTests';
load.

Gofer new
        squeaksource: 'MetacelloRepository';
        package: 'ConfigurationOfOmniBrowser';
        load.
 (ConfigurationOfOmniBrowser project version: '1.1-baseline') load.

Gofer new
squeaksource: 'Moose';
package: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.

====

For now our fixes are on files attached to the mail.
Cheers,
Jannik




On Sep 20, 2010, at 16:43 , Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
> squeaksource: 'rb';
> package: 'AST-Core';
> package: 'Refactoring-Core';
> package: 'Refactoring-Critics';
> package: 'Refactoring-Environment';
> package: 'Refactoring-Spelling';
> package: 'Refactoring-Changes';
> load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Mondrian-jl.581.mcz (433K) Download Attachment
Moose-MonticelloImporter-jl.12.mcz (11K) Download Attachment
ShoutWorkspace.1-jl.7.mcz (5K) Download Attachment
Glamour-Morphic-Renderer-jl.6.mcz (43K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Simon Denier-3

On 20 sept. 2010, at 17:14, Laval Jannik wrote:

> Hi guys,
>
> It is not so easy to load Moose on Pharo1.2 :)
> There are two deprecated call during the loading. This is due to FileSystem, we cannot change the source code on the repository.

What's the licence? Can we copy the package in Moose repo until fixes are integrated?

> ====
>
> For now our fixes are on files attached to the mail.
> Cheers,
> Jannik
>
> <Mondrian-jl.581.mcz><Moose-MonticelloImporter-jl.12.mcz><ShoutWorkspace.1-jl.7.mcz><Glamour-Morphic-Renderer-jl.6.mcz>


Do the fixes break in Pharo 1.1? Could we integrate them and still run in 1.1?


>
> On Sep 20, 2010, at 16:43 , Laval Jannik wrote:
>
>> =====
>>
>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>> So we do not save our work on moose repository.
>>
>> What do we do for next steps ?
>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?


Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now.

Actually the best plan is to check whether we could maintain the compability for a while.


--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

jannik laval

On Sep 20, 2010, at 18:52 , Simon Denier wrote:

>
> On 20 sept. 2010, at 17:14, Laval Jannik wrote:
>
>> Hi guys,
>>
>> It is not so easy to load Moose on Pharo1.2 :)
>> There are two deprecated call during the loading. This is due to FileSystem, we cannot change the source code on the repository.
>
> What's the licence? Can we copy the package in Moose repo until fixes are integrated?

I don't know, it is on wiresong.

>
>> ====
>>
>> For now our fixes are on files attached to the mail.
>> Cheers,
>> Jannik
>>
>> <Mondrian-jl.581.mcz><Moose-MonticelloImporter-jl.12.mcz><ShoutWorkspace.1-jl.7.mcz><Glamour-Morphic-Renderer-jl.6.mcz>
>
>
> Do the fixes break in Pharo 1.1? Could we integrate them and still run in 1.1?

Only Mondrian seems to be broken with my changes.
So tomorrow, I will commit the rest.

Cheers,
Jannik

>
>
>>
>> On Sep 20, 2010, at 16:43 , Laval Jannik wrote:
>>
>>> =====
>>>
>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>> So we do not save our work on moose repository.
>>>
>>> What do we do for next steps ?
>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
>
> Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now.
>
> Actually the best plan is to check whether we could maintain the compability for a while.
>
>
> --
> Simon
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Alexandre Bergel
> Only Mondrian seems to be broken with my changes.
> So tomorrow, I will commit the rest.

Can you be a bit more explicit ? Try to commit what you have, I will have a look at it.

Alexandre


>
>>
>>
>>>
>>> On Sep 20, 2010, at 16:43 , Laval Jannik wrote:
>>>
>>>> =====
>>>>
>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>> So we do not save our work on moose repository.
>>>>
>>>> What do we do for next steps ?
>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>
>>
>> Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now.
>>
>> Actually the best plan is to check whether we could maintain the compability for a while.
>>
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Stéphane Ducasse
In reply to this post by Simon Denier-3

On Sep 21, 2010, at 9:43 PM, Laval Jannik wrote:

>
> On Sep 20, 2010, at 18:52 , Simon Denier wrote:
>
>>
>> On 20 sept. 2010, at 17:14, Laval Jannik wrote:
>>
>>> Hi guys,
>>>
>>> It is not so easy to load Moose on Pharo1.2 :)
>>> There are two deprecated call during the loading. This is due to FileSystem, we cannot change the source code on the repository.
>>
>> What's the licence? Can we copy the package in Moose repo until fixes are integrated?

MIT and I hope that colin will change it slightly and that we can integrate it in Pharo.

>
> I don't know, it is on wiresong.
>
>>
>>> ====
>>>
>>> For now our fixes are on files attached to the mail.
>>> Cheers,
>>> Jannik
>>>
>>> <Mondrian-jl.581.mcz><Moose-MonticelloImporter-jl.12.mcz><ShoutWorkspace.1-jl.7.mcz><Glamour-Morphic-Renderer-jl.6.mcz>
>>
>>
>> Do the fixes break in Pharo 1.1? Could we integrate them and still run in 1.1?
>
> Only Mondrian seems to be broken with my changes.
> So tomorrow, I will commit the rest.
>
> Cheers,
> Jannik
>
>>
>>
>>>
>>> On Sep 20, 2010, at 16:43 , Laval Jannik wrote:
>>>
>>>> =====
>>>>
>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>> So we do not save our work on moose repository.
>>>>
>>>> What do we do for next steps ?
>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>
>>
>> Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now.
>>
>> Actually the best plan is to check whether we could maintain the compability for a while.
>>
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Mariano Martinez Peck
In reply to this post by Alexandre Bergel


On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.

But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
You cannot make progress without breaking things.

I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.

Cheers

Mariano

 

Alexandre



On 20 Sep 2010, at 10:43, Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
>               squeaksource: 'rb';
>               package: 'AST-Core';
>               package: 'Refactoring-Core';
>               package: 'Refactoring-Critics';
>               package: 'Refactoring-Environment';
>               package: 'Refactoring-Spelling';
>               package: 'Refactoring-Changes';
>               load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

jannik laval
In reply to this post by Alexandre Bergel

On Sep 21, 2010, at 22:07 , Alexandre Bergel wrote:

>> Only Mondrian seems to be broken with my changes.
>> So tomorrow, I will commit the rest.
>
> Can you be a bit more explicit ? Try to commit what you have, I will have a look at it.

All are on my first mail, you just have to merge.
The problem comes from ShoutWorkspace. The Preference changes are not integrated in Pharo 1.1

As I see, we should wait before going to pharo1.2


Cheers,
Jannik


>
> Alexandre
>
>
>>
>>>
>>>
>>>>
>>>> On Sep 20, 2010, at 16:43 , Laval Jannik wrote:
>>>>
>>>>> =====
>>>>>
>>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>>> So we do not save our work on moose repository.
>>>>>
>>>>> What do we do for next steps ?
>>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>>
>>>
>>> Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now.
>>>
>>> Actually the best plan is to check whether we could maintain the compability for a while.
>>>
>>>
>>> --
>>> Simon
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> ---
>> Jannik Laval
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Simon Denier-3
In reply to this post by Alexandre Bergel

On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:



On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.

But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
You cannot make progress without breaking things.

I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.


As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
I just let other people debug the process for now...

That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.


Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.



Cheers

Mariano

 

Alexandre



On 20 Sep 2010, at 10:43, Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
>               squeaksource: 'rb';
>               package: 'AST-Core';
>               package: 'Refactoring-Core';
>               package: 'Refactoring-Critics';
>               package: 'Refactoring-Environment';
>               package: 'Refactoring-Spelling';
>               package: 'Refactoring-Changes';
>               load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

jannik laval
Simon, Only two packages break on 1.2:
- FileSystem
- Mondrian.

So we can do a metacello configuration with only a part of moose to export mse.

cheers,
Jannik

On Sep 22, 2010, at 15:34 , Simon Denier wrote:


On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:



On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.

But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
You cannot make progress without breaking things.

I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.


As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
I just let other people debug the process for now...

That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.


Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.



Cheers

Mariano

 

Alexandre



On 20 Sep 2010, at 10:43, Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
>               squeaksource: 'rb';
>               package: 'AST-Core';
>               package: 'Refactoring-Core';
>               package: 'Refactoring-Critics';
>               package: 'Refactoring-Environment';
>               package: 'Refactoring-Spelling';
>               package: 'Refactoring-Changes';
>               load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Stéphane Ducasse
In reply to this post by Laval Jannik-2
Yes
Now moose people can also consider the list of pending issues and help.
There are some important fixes that nobody even packaged so that we can have a look at them.
Stef


On Sep 22, 2010, at 3:11 PM, Alexandre Bergel wrote:

> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>
> Alexandre
>
>
>
> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>
>> I just tried to load Moose on pharo1.2
>>
>> I only do this script (loading OB is not needed I think):
>>
>> =====
>> Gofer new
>> squeaksource: 'rb';
>> package: 'AST-Core';
>> package: 'Refactoring-Core';
>> package: 'Refactoring-Critics';
>> package: 'Refactoring-Environment';
>> package: 'Refactoring-Spelling';
>> package: 'Refactoring-Changes';
>> load.
>>
>> Gofer new
>> squeaksource: 'shout';
>> version: 'Shout-cyrille_delaunay.87';
>> package: 'ShoutWorkspace.1';
>> package: 'ShoutTests';
>> load.
>>
>> Gofer new
>> squeaksource: 'MetacelloRepository';
>> package: 'ConfigurationOfOmniBrowser';
>> load.
>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>>
>> Gofer new
>> squeaksource: 'Moose';
>> package: 'ConfigurationOfMoose';
>> load.
>> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
>> =====
>>
>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>> So we do not save our work on moose repository.
>>
>> What do we do for next steps ?
>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>
>> Cheers,
>> ---
>> Jannik Laval
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Mariano Martinez Peck
In reply to this post by Simon Denier-3


On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <[hidden email]> wrote:

On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:



On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.

But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
You cannot make progress without breaking things.

I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.


As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
I just let other people debug the process for now...

That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.

The only reason I found is what Stef said...if you want to help Pharo, report issues and fix them, then this is useful.
 


Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.


However, I do not think it is useful for a Hudson report. What is the sense of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken even itself ?.

Again, from my point of view, if you DO spend time trying to use Moose in Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just wait until it is stable.


 


Cheers

Mariano

 

Alexandre



On 20 Sep 2010, at 10:43, Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
>               squeaksource: 'rb';
>               package: 'AST-Core';
>               package: 'Refactoring-Core';
>               package: 'Refactoring-Critics';
>               package: 'Refactoring-Environment';
>               package: 'Refactoring-Spelling';
>               package: 'Refactoring-Changes';
>               load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

jannik laval

On Sep 22, 2010, at 16:31 , Mariano Martinez Peck wrote:



On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <[hidden email]> wrote:

On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:



On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.

But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
You cannot make progress without breaking things.

I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.


As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
I just let other people debug the process for now...

That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.

The only reason I found is what Stef said...if you want to help Pharo, report issues and fix them, then this is useful.
 


Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.


However, I do not think it is useful for a Hudson report. What is the sense of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken even itself ?.

Again, from my point of view, if you DO spend time trying to use Moose in Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just wait until it is stable.

As I see in my short try of Moose in Pharo1.2 is not a problem of bug.
There are some deprecation in Pharo 1.2 that we should integrate on Moose.

Cheers,
Jannik



 


Cheers

Mariano

 

Alexandre



On 20 Sep 2010, at 10:43, Laval Jannik wrote:

> I just tried to load Moose on pharo1.2
>
> I only do this script (loading OB is not needed I think):
>
> =====
> Gofer new
>               squeaksource: 'rb';
>               package: 'AST-Core';
>               package: 'Refactoring-Core';
>               package: 'Refactoring-Critics';
>               package: 'Refactoring-Environment';
>               package: 'Refactoring-Spelling';
>               package: 'Refactoring-Changes';
>               load.
>
> Gofer new
> squeaksource: 'shout';
> version: 'Shout-cyrille_delaunay.87';
> package: 'ShoutWorkspace.1';
> package: 'ShoutTests';
> load.
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfOmniBrowser';
> load.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>
> Gofer new
> squeaksource: 'Moose';
> package: 'ConfigurationOfMoose';
> load.
> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> =====
>
> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> So we do not save our work on moose repository.
>
> What do we do for next steps ?
> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>
> Cheers,
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Stéphane Ducasse
In reply to this post by Stéphane Ducasse

On Sep 22, 2010, at 7:24 PM, Colin Putney wrote:

> On Wed, Sep 22, 2010 at 2:51 AM, Stéphane Ducasse
> <[hidden email]> wrote:
>
>> MIT and I hope that colin will change it slightly and that we can integrate it in Pharo.
>
> Right, it's MIT-licensed, and I'm quite happy to have it integrated in
> Pharo. I'm currently implementing some of the changes we discussed at
> the conference, and I'll make sure the next release works on Pharo.

excellent!
I would love to have that in 1.2 so that we can start integrating it fully in 1.3

Jannik it would be a good nice little article for linux mag and book chapter
There is the blog of lukas already and once colin will repackage and rename (FSPath :D)
we can start writing a nice documentation :).

Stef
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Tudor Girba
Indeed, it would be nice to have that in Pharo directly. We are using it in Moose since it was released and it is a great library.

I think I forgot to thank you before. So, thanks! :)

Cheers,
Doru


On 22 Sep 2010, at 21:42, Stéphane Ducasse wrote:

>
> On Sep 22, 2010, at 7:24 PM, Colin Putney wrote:
>
>> On Wed, Sep 22, 2010 at 2:51 AM, Stéphane Ducasse
>> <[hidden email]> wrote:
>>
>>> MIT and I hope that colin will change it slightly and that we can integrate it in Pharo.
>>
>> Right, it's MIT-licensed, and I'm quite happy to have it integrated in
>> Pharo. I'm currently implementing some of the changes we discussed at
>> the conference, and I'll make sure the next release works on Pharo.
>
> excellent!
> I would love to have that in 1.2 so that we can start integrating it fully in 1.3
>
> Jannik it would be a good nice little article for linux mag and book chapter
> There is the blog of lukas already and once colin will repackage and rename (FSPath :D)
> we can start writing a nice documentation :).
>
> Stef
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Some battles are better lost than fought."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Tudor Girba
In reply to this post by Mariano Martinez Peck
The main reason for getting the Moose dev version on top of the latest Pharo dev version is because this is the simplest way to utilize the limited resources in the Smalltalk community. It is the same reason why I argue for Moose users to always use the latest Moose dev. Of course, it can be painful at times, but if you get enough users that feel the pain and that are willing to work with you, the core tends to become and stay stable.

Cheers,
Doru


On 22 Sep 2010, at 16:31, Mariano Martinez Peck wrote:

>
>
> On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <[hidden email]> wrote:
>
> On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:
>
>>
>>
>> On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
>> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>>
>> But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
>> You cannot make progress without breaking things.
>>
>> I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.
>
>
> As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
> I just let other people debug the process for now...
>
> That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.
>
> The only reason I found is what Stef said...if you want to help Pharo, report issues and fix them, then this is useful.
>  
>
>
> Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.
>
>
> However, I do not think it is useful for a Hudson report. What is the sense of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken even itself ?.
>
> Again, from my point of view, if you DO spend time trying to use Moose in Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just wait until it is stable.
>
>
>  
>
>>
>> Cheers
>>
>> Mariano
>>
>>  
>>
>> Alexandre
>>
>>
>>
>> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>>
>> > I just tried to load Moose on pharo1.2
>> >
>> > I only do this script (loading OB is not needed I think):
>> >
>> > =====
>> > Gofer new
>> >               squeaksource: 'rb';
>> >               package: 'AST-Core';
>> >               package: 'Refactoring-Core';
>> >               package: 'Refactoring-Critics';
>> >               package: 'Refactoring-Environment';
>> >               package: 'Refactoring-Spelling';
>> >               package: 'Refactoring-Changes';
>> >               load.
>> >
>> > Gofer new
>> > squeaksource: 'shout';
>> > version: 'Shout-cyrille_delaunay.87';
>> > package: 'ShoutWorkspace.1';
>> > package: 'ShoutTests';
>> > load.
>> >
>> > Gofer new
>> > squeaksource: 'MetacelloRepository';
>> > package: 'ConfigurationOfOmniBrowser';
>> > load.
>> > ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>> >
>> > Gofer new
>> > squeaksource: 'Moose';
>> > package: 'ConfigurationOfMoose';
>> > load.
>> > (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
>> > =====
>> >
>> > With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>> > So we do not save our work on moose repository.
>> >
>> > What do we do for next steps ?
>> > Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>> >
>> > Cheers,
>> > ---
>> > Jannik Laval
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
>  Simon
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"One cannot do more than one can do."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Stéphane Ducasse
In reply to this post by Mariano Martinez Peck
this is ok for me :)

Stef

On Sep 23, 2010, at 9:05 AM, Tudor Girba wrote:

> The main reason for getting the Moose dev version on top of the latest Pharo dev version is because this is the simplest way to utilize the limited resources in the Smalltalk community. It is the same reason why I argue for Moose users to always use the latest Moose dev. Of course, it can be painful at times, but if you get enough users that feel the pain and that are willing to work with you, the core tends to become and stay stable.
>
> Cheers,
> Doru
>
>
> On 22 Sep 2010, at 16:31, Mariano Martinez Peck wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <[hidden email]> wrote:
>>
>> On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:
>>
>>>
>>>
>>> On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
>>> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>>>
>>> But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
>>> You cannot make progress without breaking things.
>>>
>>> I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.
>>
>>
>> As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
>> I just let other people debug the process for now...
>>
>> That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.
>>
>> The only reason I found is what Stef said...if you want to help Pharo, report issues and fix them, then this is useful.
>>
>>
>>
>> Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.
>>
>>
>> However, I do not think it is useful for a Hudson report. What is the sense of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken even itself ?.
>>
>> Again, from my point of view, if you DO spend time trying to use Moose in Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just wait until it is stable.
>>
>>
>>
>>
>>>
>>> Cheers
>>>
>>> Mariano
>>>
>>>
>>>
>>> Alexandre
>>>
>>>
>>>
>>> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>>>
>>>> I just tried to load Moose on pharo1.2
>>>>
>>>> I only do this script (loading OB is not needed I think):
>>>>
>>>> =====
>>>> Gofer new
>>>>              squeaksource: 'rb';
>>>>              package: 'AST-Core';
>>>>              package: 'Refactoring-Core';
>>>>              package: 'Refactoring-Critics';
>>>>              package: 'Refactoring-Environment';
>>>>              package: 'Refactoring-Spelling';
>>>>              package: 'Refactoring-Changes';
>>>>              load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'shout';
>>>> version: 'Shout-cyrille_delaunay.87';
>>>> package: 'ShoutWorkspace.1';
>>>> package: 'ShoutTests';
>>>> load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'MetacelloRepository';
>>>> package: 'ConfigurationOfOmniBrowser';
>>>> load.
>>>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'Moose';
>>>> package: 'ConfigurationOfMoose';
>>>> load.
>>>> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
>>>> =====
>>>>
>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>> So we do not save our work on moose repository.
>>>>
>>>> What do we do for next steps ?
>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>>>
>>>> Cheers,
>>>> ---
>>>> Jannik Laval
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "One cannot do more than one can do."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose on pharo 1.2

Mariano Martinez Peck
I agree also, and I thanks about it. I was only answering to Alexandre comment "We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying."

My only objetion was that you cannot be sure Pharo1.2 is stable nor if it is working well. And yes, it can be annoying. This is why it is unstable, and this is the way to make progress.

Sorry for the noise. We can forget this thread :)

Mariano


On Thu, Sep 23, 2010 at 9:29 AM, Stéphane Ducasse <[hidden email]> wrote:
this is ok for me :)

Stef

On Sep 23, 2010, at 9:05 AM, Tudor Girba wrote:

> The main reason for getting the Moose dev version on top of the latest Pharo dev version is because this is the simplest way to utilize the limited resources in the Smalltalk community. It is the same reason why I argue for Moose users to always use the latest Moose dev. Of course, it can be painful at times, but if you get enough users that feel the pain and that are willing to work with you, the core tends to become and stay stable.
>
> Cheers,
> Doru
>
>
> On 22 Sep 2010, at 16:31, Mariano Martinez Peck wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <[hidden email]> wrote:
>>
>> On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:
>>
>>>
>>>
>>> On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <[hidden email]> wrote:
>>> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>>>
>>> But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
>>> You cannot make progress without breaking things.
>>>
>>> I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ?   Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.
>>
>>
>> As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
>> I just let other people debug the process for now...
>>
>> That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.
>>
>> The only reason I found is what Stef said...if you want to help Pharo, report issues and fix them, then this is useful.
>>
>>
>>
>> Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.
>>
>>
>> However, I do not think it is useful for a Hudson report. What is the sense of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken even itself ?.
>>
>> Again, from my point of view, if you DO spend time trying to use Moose in Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just wait until it is stable.
>>
>>
>>
>>
>>>
>>> Cheers
>>>
>>> Mariano
>>>
>>>
>>>
>>> Alexandre
>>>
>>>
>>>
>>> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>>>
>>>> I just tried to load Moose on pharo1.2
>>>>
>>>> I only do this script (loading OB is not needed I think):
>>>>
>>>> =====
>>>> Gofer new
>>>>              squeaksource: 'rb';
>>>>              package: 'AST-Core';
>>>>              package: 'Refactoring-Core';
>>>>              package: 'Refactoring-Critics';
>>>>              package: 'Refactoring-Environment';
>>>>              package: 'Refactoring-Spelling';
>>>>              package: 'Refactoring-Changes';
>>>>              load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'shout';
>>>> version: 'Shout-cyrille_delaunay.87';
>>>> package: 'ShoutWorkspace.1';
>>>> package: 'ShoutTests';
>>>> load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'MetacelloRepository';
>>>> package: 'ConfigurationOfOmniBrowser';
>>>> load.
>>>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'Moose';
>>>> package: 'ConfigurationOfMoose';
>>>> load.
>>>> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
>>>> =====
>>>>
>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>> So we do not save our work on moose repository.
>>>>
>>>> What do we do for next steps ?
>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>>>
>>>> Cheers,
>>>> ---
>>>> Jannik Laval
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "One cannot do more than one can do."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev