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
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
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
Do we have components ?
For now, I just change the superclass of FAMIXPlugin. It was FAMIXNamedEntity, now it is FAMIXContainerEntity that have incoming and outgoing references.
Jannik
On Jun 16, 2011, at 16:28 , Nicolas Anquetil wrote:
The idea is to map eclipse plugins to Components.
Does not make sense ?
nicolas
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
containerEntity is a SourcedEntity plugins/components are not
No we don't have Components. My idea is to create them to be a bit more generic than just Eclipse plugins (if that 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:33:24 Objet: [Moose-dev] Re: Eclipse plugins
Do we have components ?
For now, I just change the superclass of FAMIXPlugin. It was FAMIXNamedEntity, now it is FAMIXContainerEntity that have incoming and outgoing references.
Jannik
On Jun 16, 2011, at 16:28 , Nicolas Anquetil wrote:
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
You are right. I would like to create component also.
Now, we should discuss about where to place them in the hierarchy...
Jannik
On Jun 16, 2011, at 16:38 , Nicolas Anquetil wrote:
containerEntity is a SourcedEntity plugins/components are not
No we don't have Components. My idea is to create them to be a bit more generic than just Eclipse plugins (if that make sense)
nicolas De: "jannik.laval" jannik.laval@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Jeudi 16 Juin 2011 16:33:24 Objet: [Moose-dev] Re: Eclipse plugins
Do we have components ?
For now, I just change the superclass of FAMIXPlugin. It was FAMIXNamedEntity, now it is FAMIXContainerEntity that have incoming and outgoing references.
Jannik
On Jun 16, 2011, at 16:28 , Nicolas Anquetil wrote:
The idea is to map eclipse plugins to Components.
Does not make sense ?
nicolas
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
I would suggest to just implement the FAMIXEclipsePlugin as a subclass of FAMIXEntity. If another similar entity appears we can unify then. Until that time, it is artificial to introduce an abstract entity (i.e. component) because we do not know what we want it to have exactly.
Cheers, Doru
On 16 Jun 2011, at 16:47, jannik.laval wrote:
You are right. I would like to create component also.
Now, we should discuss about where to place them in the hierarchy...
Jannik
On Jun 16, 2011, at 16:38 , Nicolas Anquetil wrote:
containerEntity is a SourcedEntity plugins/components are not
No we don't have Components. My idea is to create them to be a bit more generic than just Eclipse plugins (if that make sense)
nicolas De: "jannik.laval" jannik.laval@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Jeudi 16 Juin 2011 16:33:24 Objet: [Moose-dev] Re: Eclipse plugins
Do we have components ?
For now, I just change the superclass of FAMIXPlugin. It was FAMIXNamedEntity, now it is FAMIXContainerEntity that have incoming and outgoing references.
Jannik
On Jun 16, 2011, at 16:28 , Nicolas Anquetil wrote:
The idea is to map eclipse plugins to Components.
Does not make sense ?
nicolas
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving should be focused on describing the problem in a way that makes the solution obvious."
Ok, I will do in next days.
Jannik
On Jun 16, 2011, at 19:33 , Tudor Girba wrote:
Hi,
I would suggest to just implement the FAMIXEclipsePlugin as a subclass of FAMIXEntity. If another similar entity appears we can unify then. Until that time, it is artificial to introduce an abstract entity (i.e. component) because we do not know what we want it to have exactly.
Cheers, Doru
On 16 Jun 2011, at 16:47, jannik.laval wrote:
You are right. I would like to create component also.
Now, we should discuss about where to place them in the hierarchy...
Jannik
On Jun 16, 2011, at 16:38 , Nicolas Anquetil wrote:
containerEntity is a SourcedEntity plugins/components are not
No we don't have Components. My idea is to create them to be a bit more generic than just Eclipse plugins (if that make sense)
nicolas De: "jannik.laval" jannik.laval@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Jeudi 16 Juin 2011 16:33:24 Objet: [Moose-dev] Re: Eclipse plugins
Do we have components ?
For now, I just change the superclass of FAMIXPlugin. It was FAMIXNamedEntity, now it is FAMIXContainerEntity that have incoming and outgoing references.
Jannik
On Jun 16, 2011, at 16:28 , Nicolas Anquetil wrote:
The idea is to map eclipse plugins to Components.
Does not make sense ?
nicolas
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving should be focused on describing the problem in a way that makes the solution obvious."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks.
In any case, having the plugins is a very nice addition. Just a question: is the information populated by VerveineJ?
Cheers, Doru
On 16 Jun 2011, at 19:37, jannik.laval wrote:
Ok, I will do in next days.
Jannik
On Jun 16, 2011, at 19:33 , Tudor Girba wrote:
Hi,
I would suggest to just implement the FAMIXEclipsePlugin as a subclass of FAMIXEntity. If another similar entity appears we can unify then. Until that time, it is artificial to introduce an abstract entity (i.e. component) because we do not know what we want it to have exactly.
Cheers, Doru
On 16 Jun 2011, at 16:47, jannik.laval wrote:
You are right. I would like to create component also.
Now, we should discuss about where to place them in the hierarchy...
Jannik
On Jun 16, 2011, at 16:38 , Nicolas Anquetil wrote:
containerEntity is a SourcedEntity plugins/components are not
No we don't have Components. My idea is to create them to be a bit more generic than just Eclipse plugins (if that make sense)
nicolas De: "jannik.laval" jannik.laval@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Jeudi 16 Juin 2011 16:33:24 Objet: [Moose-dev] Re: Eclipse plugins
Do we have components ?
For now, I just change the superclass of FAMIXPlugin. It was FAMIXNamedEntity, now it is FAMIXContainerEntity that have incoming and outgoing references.
Jannik
On Jun 16, 2011, at 16:28 , Nicolas Anquetil wrote:
The idea is to map eclipse plugins to Components.
Does not make sense ?
nicolas
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving should be focused on describing the problem in a way that makes the solution obvious."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
----- Mail original -----
De: "Tudor Girba" tudor@tudorgirba.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Vendredi 17 Juin 2011 01:03:12 Objet: [Moose-dev] Re: Eclipse plugins Thanks.
In any case, having the plugins is a very nice addition. Just a question: is the information populated by VerveineJ?
No, I prefer to keep things separated, Eclipse is not Java and vice-versa. So I created a small new app. : verveineEclipse (or something along these lines)
The idea is to run verveineJ and then run verveineEclipse with the same parameters. VerveineEclipse reads the output.mse generated by verveineJ, browses the directories to find which one are eclipse plugins, and then looks for FamixTypes that are inside these directories (using the FileAnchors).
From that, FamixPlugins are created and populated with the types found.
It is running, but I did not have time to iron it out yet.
nicolas
Hi, I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Comments are welcome. Jannik
On Jun 17, 2011, at 10:13 , Nicolas Anquetil wrote:
----- Mail original -----
De: "Tudor Girba" tudor@tudorgirba.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Vendredi 17 Juin 2011 01:03:12 Objet: [Moose-dev] Re: Eclipse plugins Thanks.
In any case, having the plugins is a very nice addition. Just a question: is the information populated by VerveineJ?
No, I prefer to keep things separated, Eclipse is not Java and vice-versa. So I created a small new app. : verveineEclipse (or something along these lines)
The idea is to run verveineJ and then run verveineEclipse with the same parameters. VerveineEclipse reads the output.mse generated by verveineJ, browses the directories to find which one are eclipse plugins, and then looks for FamixTypes that are inside these directories (using the FileAnchors).
From that, FamixPlugins are created and populated with the types found.
It is running, but I did not have time to iron it out yet.
nicolas
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
I have a problem with your EclipseReference when I "export" it to Java (which is statically typed):
the type of source is not compatible between FAMIXRefefrence (a ContainerEntity) and FAMIXEclipseReference (a EclipsePlugin)
To correct that in the Java code I would need to specify FAMIXEntity for both :-( So may be it would be better to put it directly below FAMIXAssociation? And also may be rename it to something more specific (import, requirement, dependency)?
nicolas
----- Mail original -----
De: "Nicolas Anquetil" nicolas.anquetil@inria.fr À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Lundi 20 Juin 2011 09:46:43 Objet: [Moose-dev] Re: Eclipse plugins
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Jun 20, 2011, at 16:48 , Nicolas Anquetil wrote:
I have a problem with your EclipseReference when I "export" it to Java (which is statically typed):
the type of source is not compatible between FAMIXRefefrence (a ContainerEntity) and FAMIXEclipseReference (a EclipsePlugin)
I do not understand the need of compatibility.
To correct that in the Java code I would need to specify FAMIXEntity for both :-(
what is the problem ?
So may be it would be better to put it directly below FAMIXAssociation?
why not. The problem is the duplication of code.
And also may be rename it to something more specific (import, requirement, dependency)?
Yes, we should fix the name used.
Jannik
nicolas
----- Mail original -----
De: "Nicolas Anquetil" nicolas.anquetil@inria.fr À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Lundi 20 Juin 2011 09:46:43 Objet: [Moose-dev] Re: Eclipse plugins
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Jun 20, 2011, at 9:46 , Nicolas Anquetil wrote:
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
I have no problem with the name. But we should fix it :)
Jannik
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I would vote with FAMIXEclipsePluginImport.
Cheers, Doru
On 20 Jun 2011, at 22:19, jannik.laval wrote:
On Jun 20, 2011, at 9:46 , Nicolas Anquetil wrote:
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
I have no problem with the name. But we should fix it :)
Jannik
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Ok, it is fixed.
Jannik
On Jun 20, 2011, at 22:22 , Tudor Girba wrote:
I would vote with FAMIXEclipsePluginImport.
Cheers, Doru
On 20 Jun 2011, at 22:19, jannik.laval wrote:
On Jun 20, 2011, at 9:46 , Nicolas Anquetil wrote:
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
I have no problem with the name. But we should fix it :)
Jannik
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I would also like to rename incomingReferences and outgoingReferences, the two instance variables of FAMIXEclipsePlugin with incoming/outgoing EclipsePluginImport.
Is it ok for you ? It should have an impact on the mse exporter (eg, verveineEclipse)
Jannik
On Jun 20, 2011, at 22:22 , Tudor Girba wrote:
I would vote with FAMIXEclipsePluginImport.
Cheers, Doru
On 20 Jun 2011, at 22:19, jannik.laval wrote:
On Jun 20, 2011, at 9:46 , Nicolas Anquetil wrote:
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
I have no problem with the name. But we should fix it :)
Jannik
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
ok for me go ahead
nicolas
----- Mail original -----
De: "jannik.laval" jannik.laval@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Envoyé: Vendredi 24 Juin 2011 12:03:58 Objet: [Moose-dev] Re: Eclipse plugins I would also like to rename incomingReferences and outgoingReferences, the two instance variables of FAMIXEclipsePlugin with incoming/outgoing EclipsePluginImport.
Is it ok for you ? It should have an impact on the mse exporter (eg, verveineEclipse)
Jannik
On Jun 20, 2011, at 22:22 , Tudor Girba wrote:
I would vote with FAMIXEclipsePluginImport.
Cheers, Doru
On 20 Jun 2011, at 22:19, jannik.laval wrote:
On Jun 20, 2011, at 9:46 , Nicolas Anquetil wrote:
I just reimplemented the EclipsePlugin. It inherits from FamixEntity. I also implemented a FAMIXEclipseReference that inherits from FAMIXReference.
FAMIXEclipseReference is for dependence between eclipse plugins? If so, may be a better name could be found? e.g. FamixEclipsePluginImport, FamixEclipsePluginDependence
I have no problem with the name. But we should fix it :)
Jannik
it is available on: http://www.squeaksource.com/dsm/Famix-EclipsePlugin
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
jannik.laval -
Nicolas Anquetil -
Tudor Girba