Dear List,
I am currently working on a C importer based on srcML output. I
created an extension of FAMIX3 (I am working with Pharo) since FAMIX3
did not express procedural languages.
Essentially, 4 classes defines this extension:
- CAFunction subclass of FAMIXBehaviouralEntity
- CAInclue subclass of FAMIXAssociation
- CAModule subclass of FAMIXScopingEntity
- CAVariable subclass of FAMIXGlobalVariable
An instance of CAModule is intended to describe a C Module, instance
being generated from a C file. I think this should be the right way
to do.
On the other hand, there are FAMIXFolder and FAMIXFile. Ideally, a C
file should be seen as a file _and_ as a module. The class FAMIXFile
contains useful methods, that I would like to use on a CAModule. But
having one instance of CAModule and one instance of FAMIXFile per .c
file is clearly suboptimal.
My intuitions argues for creating a trait TFAMIXFile, that will be
used by both FAMIXFile and CAModule.
Any comment on this trait?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I just stumble upon the case when adding Famix.SourceAnchor to the
metamodel. It does not make much sense to make SourceAnchor a subclass
of FamixEntity.
Yet a common way to 'get' the Famix metamodel (found here and there in
the code) is to use FAMIXEntity withAllSubclasses (which misses
SourceAnchor)
Yet another way is to use PackageInfo, but then I need to know all
packages in which Famix extensions have been defined.
Any suggestion?
Note: we dont have this problem with MooseModel, because MooseModel
uses MooseEntity withAllSubclasses :)
but I dont want to always have this dependency on Moose when loading
Famix alone
--
Simon
Hi All,
Running HismoTest raises an error. Apparently, FAMIXSourceAnchor seems
to be not properly fame described.
A "MooseModel resetMeta does not help. FAMIXSourceAnchor is a subclass
of MooseEntity, whereas in its annotation states it is a subclass of
Object. I tried to replace Object by MooseEntity but same result.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Alex,
I need some new features in sqMondrian:
- to fix a width for MOLabelShape (method width: )
- preserve the height of a MORectangleShape when a MOLabelShape is
inserted in it
- have the property text: working in MORectangleShape
- edges in top of the figure
- fix edges :
this code doesn't work fine:
----
| view |
view := MOViewRenderer new.
view interaction popupText: [:e | e asString].
view nodes: (1 to: 2) forEach: [:each |
view interaction popupText: [:e | e asString].
view nodes: (1 to: 5).
view gridLayout].
view edges: view domain
from: [:ea | ea]
to: [:ea | ea+1]
fromGlobal: false
toGlobal: false.
view open
----
Cheers
---
Jannik Laval
PhD Student - Software Quality - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi All!
I cleaned a bit MOViewRenderer by removing all methods that set event
handlers. In other words, if you were used to write:
view popupText: [:each | ... ].
You now need to do
view interaction popupText: [:each | ... ].
Spring is coming, need to clean a bit.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Jannik,
I fixed the problem you described with the gap. If you now set a
gapSize to 0, you should not get a gap between subnodes and the
encapsulating node.
Let me know whether it is fine.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
With the work of the last few weeks, I am happy to see more and more
tests running green
From 628 tests, 587 are green (I did not run tests for Cook and
others).
I updated the class diagram on the website with the current state,
only retaining Famix-Core package (thus excluding metrics properties)
http://moose.unibe.ch/docs/famix/famix3.0/classdiagram
For the next weeks, from a pure engineering point of view, I think we
should concentrate on streamlining the experience with manipulating,
exporting/importing models, in particular with respect to MSE and its
various format
--
Simon
Can someone explain the difference between the two?
Because currently there are multiple properties with these names, some
in FamixClass, FamixBehaviouralEntity, FamixMethod....
Are they duplicated properties?
--
Simon
