7 Mar
2013
7 Mar
'13
10:36 p.m.
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."
8 Mar
8 Mar
2:10 p.m.
New subject: mini-moose sprint tomorrow
Hello Thierry,
We are moving Moose to Pharo 2.0 and trying to make build green. There was
a Glamour-related bug fix in MorphTreeMroph to correct this issue:
http://code.google.com/p/moose-technology/issues/detail?id=905
The fix is integrated in Pharo2.0 and now when loading and running tests of
Glamour and Moose-related browsers, there are a few failing tests and the
trail leads to the update method in MorphTreeMorph because the pager is
nil. Can you please have a look?
You can get the latest dev image of Moose on pharo2.0 here:
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8
and the problem can be reproduced when running glamour-related tests (e.g.
GLMUpdateMorphicTest >>testInvalidateSelection).
tx,
Usman
On Thu, Mar 7, 2013 at 10:36 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
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."
4307
days inactive
4308
days old
1 comments
2 participants
participants (2)
-
Tudor Girba -
Usman Bhatti