Hi,
I download the latest yellow build from the moose web site (8 may). When I
open Nautilus I cannot see the code.
I don't have any clue if it is about Nautilus or about how Nautilus is
loaded in Moose or about something else.
Any idea?
Cheers,
Fabrizio
Hello,
I am working to add a new tab in Moose Finder's pane to display code: So
when I select a class, I want to show its methods as a tree and clicking on
each method shows the code of the method.
Here is the code of my attempt:
mooseFinderChildrenTreeIn2: composite
<moosePresentationOrder: 80>
composite tabulator with: [:t |
t row: #methodList; row: #code; title: 'Details'.
t transmit
to: #methodList
andShow: [ :a | a tree display: [:each | each methods]]
].
Problem: my method is not executing the display block and hence the
tabulator tab does not show the list (I can see empty tabulator). I think
its related to embedding a tabulator within a composite presentation and
transmission of values but I do not precisely where to look to correct it.
thanx,
Usman
In MooseFinder, table presentation is placing last character on the next
line (see the attached image). Is there a way to force the text to display
on a single line? I'm sure its not related to the size of the text.
thanx,
Usman
Hi,
As discussed, I am working on the idea how to customize menus for entities
in Moose Finder. As the menu construction depends on the pragmas defined on
moose entity hierarchy, the idea is to read pragmas in some specific way.
We tried something with Stéphane yesterday and here I am sending you the
change set. Can you please have a look?
The change set does not complete resolve the problem :-). The problem is
that menus are duplicated and changes are still invasive (that is the code
overrides the default moose finder behavior). But this can be a possible
approach to resolve it.
tx
Usman
Hi,
I implemented this new method:
MOFilledShape>>identityBorderColorOf: aBlockOrObject
"Set the border color based on the identity returned by the block."
borderColor := MONIdentityNormalizer withCommand: aBlockOrObject
Noting fancy but could be cool to have it in the mondrian core, what do you
think?
Cheers,
Fabrizio
Some questions on dude. I am using an external tool for computing
duplications and trying to instantiate appropriate entities in moose:
1. What is referenceCode and duplicateCode in the context of SmallDude and
what is the difference between the two?
2. What is a signature?
tx
Usman
Hi,
We just had over the last couple of days some 194 failed tests:
http://ci.moosetechnology.org/job/moose-latest-dev/957/
191 of them came from a parallel commit into Mondrian. I solved it now, but to prevent this kind of thing in the future, I now changed the build to send notifications to this mailing list.
We still have three tests (related to Monticello) that are failing on the server.
Cheers,
Doru
--
www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
Hi,
I made some progress with the TreeMapLayout. Two challenges remain to be
solved.
The first one is related to dragging. It is kind if complicated to explain
in words, so I made this short screencast:
http://cl.ly/150n1t2Z2h1y3L0z1U0L
As you can see the positions of the shapes get updated only when hovering
over them, not instantly when dragging, as I would like them to.
One difference code-wise to other graph layouts is that the owner of all
shapes is, in this case, not MORoot but the node "org", which is a normal
MONode. I had to do this (change ownership) because MORoot does not get
drawn (is this by design?).
Does anyone have some ideas on what could explain this behavior?
Another question would be: Is it possible to make the inner nodes not
draggable? The user should not be able to move individual shapes inside the
TreeMap around.
Cheers,
Dennis
