Hi
just a short question
does FAMIX-AST forces to have the AST node subclass of a Moose entity
what is the independence of the tree? can we reuse him outside of famix and moose?
Stef
Hi,
I just generated an mse with inFamix and I got a MNU while importing the
file into the latest Moose.
Is there a newer release of inFamix I should download? Is it a know problem?
Thanks,
Fabrizio
Hi,
If you have to compare two MooseModels, we got tools for you.
We created the ConfigurationOf FamixDiff and OrionMerge.
- FamixDiff enables to do a diff between two MooseModels (or one OrionModel and a MooseModel). The result is a set of changes between the two models.
- OrionMerge takes this set of changes and creates a versioned OrionModel by applying the Orion action associated to each change. The result is thus an OrionModel corresponding to the target model of the diff, but taking less space of memory since its benefits from the way of Orion to manage model (between two versions, only the modified entities are stored. A clever system enables to access each entity whatever, it has been modified or not).
More information about Orion can be found there http://www.moosetechnology.org/tools/orion
I hope it is understandable.
So if you need to use them, please don't hesitate.
Anne
Nicolas wrote:
>did you run the tests before?
>I believe I saw some of them fail in the past ... ?
Uhm, we broke the build from 981 to 984,
but I'm not aware of earlier problems.
Stephan
Hi doru
i'm trying to get the parsers written by moser to work.
I cannot get the red executed (VW mess Sunittoo vs Sunit argggggghhhhhh)
I cannot get the parsers regenerated in VW.
So I'm trying to find a fix point.
stef
Hi all,
We (Stephan and myself) decided to add a Delphi unit to the FAMIX hierarchy in the Famix-Delphi package, since this is both a package and a namespace. But here we ran into trouble: we can inherit from package, from namespace, or from a scoping entity, but in all cases the method allPackages and allNamespaces do not return the desired value. Also some derived functionality, like the code browser, does not function properly, since it uses namespaces to browse the code. So we propose the following changes:
1) allPackages and allNamespaces should return "allWithSubTypesOf: " instead of withAll:
2) The message "allWithSubTypesOf: aSmalltalkClass ofGroupClass: aGroupSmalltalkClass" should iterate over a new method call "withMooseSubclasses" instead of "withAllSubclasses"
3) Default return value of withMooseSubclasses is withAllSubclasses, except when a class registers itself as a Moose subclass, indicating it is of the "Moose type" of the class it registers to.
This allows us to create a "merged" type of package and namespace for Delphi and still allowing for the codeBrowser to function properly.
What do you think about this change. I implemented it in my image, and it seems to work fine.
Cheers,
Diego
Hello,
Mouse Enter and Leave in Roassal is not working so well. Dynamic edges are
removed sometimes but sometimes they are not. Can you please have a look?
tx,
Usman