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
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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel alexandre@bergel.euwrote:
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 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
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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--- Jannik Laval
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
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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--- Jannik Laval
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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
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
--- Jannik Laval
-
Alexandre Bergel -
Laval Jannik -
Laval Jannik -
Mariano Martinez Peck -
Simon Denier