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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev