Hi all,
I have the following setup:
browser transmit to: #cls; andShow: [:a |
a title: 'Classes'.
a list title: 'H'; display: self cprops.
a list title: 'W'; display: self cprops].
(where self cprops returns what it should. Not really important for this discussion.)
and I have
browser transmit to: #mpanel; from: #cls; andShow: [:a |
a mondrian painting: [:view :classprop |
...
Now I would like to know if the classprop that comes from #cls was selected on the 'H' tab or on the 'W' tab. I tried
browser transmit to: #mpanel; from: #cls; from: #cls->#activeEntity; andShow: [:a |
a mondrian painting: [:view :classprop :classtab|
but classtab is always nil. Also, supposing this works, every time a tab is switched this would lead to a mondrian redraw, which is not what I want ...
So how do I do this?
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Hi Alex,
The default font size in Mondrian is now set to 10. However, the
default goal of Mondrian is to deal with lots of data, not few. The
default 10 font size does not really favor placing many items on the
screen. It is more like you would favor a UML diagram.
So, I suggest to reset the value to 5 :)
Cheers,
Doru
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of
problem understanding."
Hi,
Before or after committing a package, please ensure that there was no
other version published in parallel.
I encountered several times the problem of versions that were lost
along the way.
Cheers,
Doru
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."
Hi,
I am looking into the Moose-Algos-Graph package. It's pretty cool,
especially that you can create graphs easily.
The only problem I encountered so far is that I cannot create nested
graphs.
I just see now that MOGraphStructure is a subclass of MOGraphAlgorithm
and that MOGraphAlgorithm has nodes and edges. This means that these
can handle only one level of nodes and edges.
This problem was solved in Mondrian by making each node or edge a
graph. Using a similar approach, MOGraphAlgorithm could then just
point to one root node that holds everything.
Or maybe we need a MOGraphBuilder that creates the graph and
MOGraphAlgorithm just deals with a set of nodes and edges.
What do you think?
Cheers,
Doru
--
www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Hello,
When importing C code with CAnalyzer, if you open a mooseFinder on the
generated model, select allCAUnitElements and then select anyOne of this
CAUnitsElements, it will raise an Error:
"My subclass should have overriden 'classes'".
CAunitElement is a subclass of FAMIXScopingEntity. FAMIXScopingEntity
declare the abstract method 'classes' (which make no sense for a
CAUnitElement ). Then, it seems that the mooseFinder require this method to
browse a CAUnitElement.
Hi Cyrille,
I have a bit of feedback for Distribution Map:
- The computation from Distribution Map Wizard is too expensive
because you iterate over the meta elements and for each of them you go
over all elements of Moose through the method includesElementsOfType:
It would be better if you would go over all cached groups and decide
based on that rather than traversing the entire entities collection
(which can be millions of objects).
- It would be better if Distribution Map gets its own package because
it starts to be large
Cheers,
Doru
--
www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."