Hi folks. Today Adrian released an integration between the Squeak/Pharo VM
and DTrace. I read his post and the code and seems VERY interested. I know
very very little about Moose, but I guess if moose wants to move on, it
should start to analyze more the runtime world. For such purpose, it will
requiere PROBABLY (almost sure) a particular VM. For example, what I plan
to do now (playing with DistributionMap and used/unused objects) will
requiere my own VM. In this case of Adrian too. So....
The Adrian's post can be found here: http://www.adrian-lienhard.ch/blog
Please take a look. Not necessary to the implementation details but to the
features it can you you.
Finally, read the last sentence: "DTrace by itself does not provide
visualizations but since its output can be formatted as required (using
printf) and piped into a file, one can feed the data to a visualization tool
(e.g., print output in MSE format, import it into Moose, and create
interactive visualizations with Mondrian)."
I am using flowLayout to control the maxWidth, but if the window is maximized or resized, I would like to change the maxWidth automatically too, so i can use better the space.
Is this possible? how?
Just for fun, I created a class in the GraphViz package that takes a
given view script and generates files with different layouts. This
might be useful for deciding on the kinds of layouts that might be
appropriate for your graphs. I put this in the MondrianGraphVizLayout
package because I have hard references to GraphViz classes.
Here is an example:
MOAllLayouts exportView: [:view |
view nodes: (1 to: 100).
view shape arrowedLine.
view edges: (1 to: 100) from: [:x | x // 10] to: #yourself.
view nodes: (100 to: 200).
view shape arrowedLine.
view edges: (100 to: 200) from: [:x | (x // 10) + 100 ] to: #yourself.
The result is attached here.
"We cannot reach the flow of things unless we let go."
Perhaps this is of interest to someone.
I produced a new visualization to show the dependencies introduced by
annotations in a Java system:
The goal of the visualization is twofold:
- help identify which annotations are closer together and with this
occasion get an idea of what technologies are used
- make explicit the fact that annotations do introduce another layer
At the moment, this works for Java systems. Perhaps it would be
interesting to populate the Annotation entities from Smalltalk as well.
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
CALL FOR CONTRIBUTIONS
FAMOOSr 2010 - 4th Workshop on FAMIX and Moose in Reengineering
Co-located with ICSM 2010, Timisoara, Romania
We solicit experience reports and position papers (2-4 pages, IEEE format). Experience reports will be expected to discuss meta-modeling and software analysis using, but not limited to, FAMIX or Moose. Position papers will be expected to describe new directions and challenges for software analysis infrastructures, like FAMIX or Moose.
Papers may address issues along general themes, including but not limited to:
- Analysis specific meta-models for evolution data, dynamic traces, bug entries, etc...
- Meta-modeling in reengineering tools
- Visualization techniques.
- Analysis techniques: clustering, data mining, machine learning, pattern matching, probabilistic approaches, etc...
- Mechanisms for tool composition and rapid tool prototyping.
- Reusability of research: making research results and tools available to and reusable by the community.
- Persistency and manipulation of models and meta-models.
Submissions are not limited to FAMIX and Moose or to their active users. We welcome any related ideas.
During the workshop, authors are expected to present their ideas using a short format, lasting 3 to 7 minutes, in order to spawn vivid discussions between participants. Presentations with demos are also warmly welcomed (and may be given 10 minutes). More information about this format can be found at: http://moose.unibe.ch/events/famoosr2008/presenterskit
Submissions should be made via Easychair at
- submission: July 5
- notification: July 19
- workshop: September 17
- Simon Denier, INRIA Lille, France
- Mircea Lungu, University of Lugano, Switzerland
Could it be possible that anywhere we get a class (either as mondrian) or list or whatever
we could get a default navigation menus offering all the navigation facilities?
Because now we arrive to some dead-ends.
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?
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
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 :)
"Problem solving efficiency grows with the abstractness level of
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.
"Be rather willing to give than demanding to get."