CAnalyzer has been updated with the last version of Moose. It works well, but does not follow the Moose rules and conventions (e.g., I do not know whether the metamodel is properly Fame compliant, it does not use MooseChef).
In any case, large C programs are loadable in the last version of Moose. I will keep you informed about my progresses.
Alexandre Bergel http://www.bergel.eu
We are working on the visualization of plugins in Mondrian and we are trying
to create some custom visu. Question: Is there anyway we can color a few
edges in Mondrian according to some condition? That is, we are trying to
describe a condition for coloring edges according to the plugin they target
as illustrated by the bold line in the script below:
view shape rectangle
width: [:p | p outgoingFAMIXEclipsePluginImport size] ;
height: [:p | p incomingFAMIXEclipsePluginImport size] ;
if: [ p | p name includesSubString: 'uml'] fillColor: Color blue.
view nodes: (eclipsePluginGroup select: [:p | p name includesSubString:
view shape arrowedLine
*if: [ :i | i target name = 'org.eclipse.papyrus.core'] fillColor:
view edges: (MooseModel root allModels first allWithType:
FAMIXEclipsePluginImport) from: #source to: #target.
view dominanceTreeLayout .
thanx in advance,
Usman & Nicolas
I did a demo yesterday and the new little icon does not work from a ui perspective.
When you do change like that it would be good that:
- they are discussed in the mailing-list
- that proposed changed are not worse than before: a check button is not an actuator
it is a check box.
Moose people and pharoers are interested in your library to map XML to objects. So I was wondering what was its
Do you got a bit more documentation/tests because I would like to start reading them so that
after I can see what we can do to help.
I was discussing with andre and I would like to know what are the solutions that we have in Moose for the following two scenarios.
We have a model in FAMIX
1- we want to create entities that are described (probably exported by another tool) in XML.
2- we want to annotate existing entities
Another scenario would be to turn XML into mse and create Smalltalk class of the metamodel but this is another story.
Doru I do not remember the goal and status of OPAX.
Labels: Type-Defect Priority-Medium Component-XML Milestone-4.6
New issue 719 by tudor.gi...(a)gmail.com: XMLSupport should be in the
XMLSupport was taken out of the configuration because it used to be shipped
However, it is not present in Pharo 1.3 anymore. So, we have to add it back
to the ConfigurationOfMoose.