The idea is to map eclipse plugins to Components.
Does not make sense ?
nicolas
----- Mail original -----
De: "jannik.laval" jannik.laval@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Jeudi 16 Juin 2011 16:25:06 Objet: [Moose-dev] Re: Eclipse plugins
Yes, that is what I have implemented. I should also add a "reference" to other plugins.
The source code is available for now:
Gofer new squeaksource: ’dsm’; package: ’Dsm − Plugins’; load.
Jannik
On Jun 16, 2011, at 16:07 , Alexandre Bergel wrote:
I have the impression that you need a FAMIXEclipsePlugin class somewhere...
Alexandre
On 16 Jun 2011, at 10:02, Nicolas Anquetil wrote:
For a project on a large Eclipse Application (Papyrus, for drawing UML graphs), we needed to add Eclipse Plugins.
Jannik did a first implementation in Famix to be able to run moose, but it would be nice to do-it-right.
So the proposition would be (this is not how we implemented it right now):
FamixComponent sub-concept of FamixEntity
has:
- belongsTo another FamixComponent
- childNamedEntities
A component is suppose to provide interfaces and require interfaces.
How can we represent that? with Type?
Eclipse plugins actually decalre other plugins that they require. I believe this is not standard as component should only rely on interfaces, not other explicitly named components ...
all input welcome
nicolas
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev