Im currently using the dev version of Moose. For some parts it is still
very unstable. For example when using the Mondrian Easel examples, it
always crashes after a short while. Also autocomplete does not seem to work
at the moment.
I looked at ConfigurationOfMoose to see if I could use the stable version
for some of the development, but there the stable version currently points
to version 4.3.4 as far as I can tell.
Would it be possible to create a configuration for the latest stable
version of Moose, i guess that would be 4.6.x?
I implement a browser with glamour. To provide data to the browser I use
the Hismo models that are installed in the Moose Panel:
browser openOn: MooseModel root allModelHistories
How can I refresh the data shown by the browser when a new Hismo model is
added to the Moose Panel?
After fixing Collection>>union: in Pharo, the Moose tests are better. We now have only 8 failing tests.
Any help to fix these would be appreciated :)
"What is more important: To be happy, or to make happy?"
Labels: Type-Defect Priority-Medium
New issue 783 by google....(a)ben.coman.com.au: hidden 'Name already defined'
tempvar & ivar clash
Moose 4.6 has some hidden clashes between instance variables and method
In order to observe the operation of #forNode:do: in Mondrian, I went to
add only 'self halt' to
When I tried to <Accept> this, it complained temporary variable 'view'
was 'Name already defined' and indeed MOViewRendererTest does have a
clashing instance variable 'view' which prevents me from saving my change.
Similar has happened to me previously a few times, so I thought I would
flag it in case anyone was curious to determine how this got past the
compiler into the system, and also might be able to do some automated sweep
of the code to detect any similar occurances.
In Moose 4.6, World > Moose > Mondrian Easel > Examples > basic > edges
+ tiled nodes
has this code...
| nodes |
view shape rectangle
nodes := view nodes: (1 to: 20).
view shape arrowedLine.
view edges: (2 to: 20) from: 1 to: #yourself.
view layout: (MOCircleLayout forNodes: nodes allButFirst)
which displays text inside each rectangular node.
If I change the second line to...
view shape ellipse
then nodes do appear as ellipses but the text disappears. That is not
what I expected. How can text be made to display within an ellipse?
Are you using Moose for something?
If yes, could you let us know what that something is?
It can be research, play, commercial, short term, long term, for software analysis, for other kinds of analysis.
Or maybe you are using only some part of it all. Anything would do.
Please take 2 minutes to reply.
"We can create beautiful models in a vacuum.
But, to get them effective we have to deal with the inconvenience of reality."
I added a new importer in the Moose Panel and so I can browse my model. It
show me that no SourceLanguage was defined so I added my own
sourceLanguage, inheriting from FAMIXSourceLanguage. I have a problem is
about this call:
anObject mooseInterestingEntity mooseDescription allPrimitiveAttributes
because mooseDescription return nil.
The problem is about asMooseDescription send to my class because it refer
to the MooseModel meta dictionnary and my class is not in, so it return nil.
I have implemented the class method annotation but it doesn't change
How can I have my class in the dictionnary?
Thanks in advance.
i try to use EyeSee to plot mathematical functions with ESLineDiagram.
They is not easy as i might expect at the beginning :-)
The problem is EyeSee is using collections as models. I try to
transform the function as a collection like above but maybe there is a
better way to do that.
|diag f functionAsModel|
f := [:x | x*x].
functionAsModel := (0 to:10 by:0.1) collect:[:each | f value:each].
diag := ESDiagramRenderer new.
defaultColor: Color green;
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk
We got down to one failing test:
This is related to the order in collection noticed by Alex.
Begin forwarded message:
> From: admin(a)moosetechnology.org
> Subject: Jenkins build is unstable: moose-latest-dev #900
> Date: 22 March 2012 07:45:23 CET
> To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)gmail.com
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/900/>
"Sometimes the best solution is not the best solution."