Hi,
Great.
In the meantime, I fixed Mondrian and EyeSee to not throw errors. The problem was that in
Pharo 2.0 Morphs send announcements, and these got confused with the specific
announcements for Mondrian and EyeSee.
Now Glamour has 7 errors but they are all due to the same problem of not being able to set
the value of a port from outside when rendering a list. The issue comes from some internal
modifications of MorphTreeMorph. It would be cool if someone could take a look at this.
There are also a couple of Mondrian tests failing, but they are due to Easel accessing a
missing class MorphicTextEditor which was already deprecated in 1.4. Nevertheless, the
Easel is no longer really needed because we have one in Glamour.
Cheers,
Doru
On Mar 7, 2013, at 4:26 PM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
For info.
---------- Forwarded message ----------
From: Usman Bhatti <usman.bhatti(a)gmail.com>
Date: Thu, Mar 7, 2013 at 4:15 PM
Subject: mini-moose sprint tomorrow
To: RMoD private list <lsehub-staff(a)lists.gforge.inria.fr>
Now that Moose has moved to SThub and we loading it on Pharo 2.0, there are some failing
tests in Moose:
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testR…
Tomorrow, we will try to make green FAMIX/Moose related tests.
The place will be decided at "runtime" according to the number of
participants.
usman
--
www.tudorgirba.com
"Every thing has its own flow."