I cannot see the code in the latest Moose build
by Fabrizio Perin
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
10 years, 10 months
glamour help
by Usman Bhatti
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
10 years, 10 months
glamour placing last character on next line
by Usman Bhatti
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
10 years, 10 months
customizing menus for moose entities in moose finder
by Usman Bhatti
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
10 years, 10 months
Mondrian new method identityBorderColorOf:
by Fabrizio Perin
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
10 years, 10 months
refcode and duplicated code in dude
by Usman Bhatti
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
10 years, 10 months
new Mondrian example 'changing subview layout interactively'
by Ben Coman
Just sharing a cool result of some experimentation with Mondrian. I was
pleasantly surprised with what I ended up with.
Contents of attached text file can be copied to Workspace. Also I've
uploaded this for Mondrian Easel as Mondrian-Example-BenComan.44.
cheers -ben
| view b actionBlock makeMenu |
view := MOViewRenderer new.
"Define shape such that the MOLayout name is displayed above the subview children"
b := MOFormsBuilder new.
b column; fill; row; fill; row; fill .
b x:1 y:1 add:
( MORectangleShape new
text: [ :value | (view nodeForDomainValue: value) layout. ];
textAlignment: #center;
borderColor: Color white
) .
b x:1 y:2 add: ( MORectangleShape new ) .
b x:1 y:2 add: ( MOChildrenShape new ) .
view shape: b shape.
"Define menus for setting the layouts of subviews"
actionBlock :=
[ :selectedValue :newLayout |
| element position |
element := view nodeForDomainValue: selectedValue.
position := element bounds origin.
element layout: newLayout.
element applyLayout.
element resetFormCacheUpToTheRoot.
element translateBy: position.
view updateWindow.
].
makeMenu :=
[ :layout |
view interaction item: (layout class name asString) action: [ :selectedValue | actionBlock value: selectedValue value: layout ].
].
makeMenu value: (MOGridLayout new).
makeMenu value: (MOBottomFlowLayout new).
makeMenu value: (MOBulletTreeLayout new).
makeMenu value: (MOCircleLayout new scaleBy: 6).
makeMenu value: (MODominanceTreeLayout new).
makeMenu value: (MOFADELayout new).
makeMenu value: (MOFlowLayout new).
makeMenu value: (MOForceBasedLayout new).
makeMenu value: (MOHorizontalDominanceTreeLayout new).
makeMenu value: (MOFlowLayout new).
makeMenu value: (MODominanceTreeLayout new).
makeMenu value: (MOHorizontalLineLayout new).
makeMenu value: (MOHorizontalNarrowTreeLayout new).
makeMenu value: (MOHorizontalTreeLayout new).
makeMenu value: (MOMinimumGridLayout new).
makeMenu value: (MOVerticalNarrowTreeLayout new).
makeMenu value: (MORadialTreeLayout new).
makeMenu value: (MOSpringLayout new).
makeMenu value: (MOSugiyamaLayout new).
makeMenu value: (MOTreeLayout new).
makeMenu value: (MOVerticalLineLayout new).
"Define some nodes and edges"
view
nodes: (10 to: 70 by: 10)
forEach:
[ :each |
view shape rectangle size: 20; withText.
view nodes: ( each+1 to: each+9).
view edge: each+1 from: each+1 to: each+2.
view edge: each+1 from: each+1 to: each+3.
view edge: each+1 from: each+1 to: each+4.
view edge: each+2 from: each+2 to: each+5.
view edge: each+2 from: each+2 to: each+6.
view edge: each+2 from: each+2 to: each+7.
view edge: each+3 from: each+3 to: each+7.
view edge: each+3 from: each+3 to: each+8.
view edge: each+3 from: each+3 to: each+9.
view circleLayout scaleBy: 6.
].
view circleLayout scaleBy: 25.
view open
10 years, 10 months
TreeMapLayout
by Dennis Schenk
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
10 years, 10 months
