2 Aug
2012
2 Aug
'12
9:25 p.m.
Hi Andrea,
On Jul 31, 2012, at 3:11 PM, Andrea Caracciolo <andyy.mailbox(a)gmail.com> wrote:
Hi Jannik,
Are you saying that this feature can't be added because some already implemented
actions are not always working as expected ? Did i understand correctly ?
The feature can be added, but is not :)
Do you think you can fix it ?
Do you need help with it ?
I attached a small code snippet which might help developing a possible solution…
<orion.txt>
It seems to be a good first approach, but I think that loading all the 2nd model to remove
it after is not efficient.
A solution could be to read the mse file and create only the necessary entities using
orion methods.
I will try to do something during August.
If you need it, you can also propose source code, and I can review it.
Cheers,
Jannik
Andrea
On Jul 30, 2012, at 9:32 PM, jannik.laval wrote:
---
Jannik Laval
Dear Andrea,
I am happy that you try to use Orion.
The primary goal of Orion was to try modifications on a model and keep changes.
The meta-model allows clearly to save history, but the infrastructure needs some work.
For now, a diff is not implemented. We have to think about this feature. I have no idea
how to do that, because some problems appear when merging or forking.
Jannik
On Jul 30, 2012, at 11:41 AM, Andrea Caracciolo <andyy.mailbox(a)gmail.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev I downloaded the latest version from OrionDev and
i tried to create 2 model versions starting from 2 MSE files of two subsequent versions of
the same project.
The following code does simply create 2 versions, the second of which contains all the
entities coming from famixModel2 and a reference to all the entities contained in model1.
model1 := OrionConverter convertFrom: famixModel1.
model2 := OrionConverter convertFrom: famixModel2.
system originalModel: model1.
model1 orionSystem: system.
model2 withParent: model1.
I would like to know if there is a method which allows to add a new version and also
makes a diff between the entities being added and the entities contained in the parent
version.
The diff should be made between entities sharing the same mooseName and should be done on
the basis of the contained code (if existing).
Thanks :)
On Jul 28, 2012, at 10:17 PM, jannik.laval wrote:
---
Jannik Laval
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>
>>
>> If there are multiple versions of a project, it would be also interesting to
distribute an Orion model of all the versions.
>> Is it possible to build such a model having an MSE file for each version as input
?
>
> yes
>> How much effort is needed to fix the bugs and make it work ?
>
> Jannik? But normally it should work.
Iep, it should work.
I used the pragma for importing elements in MSE.
But I never tried it.
> Now I do not know if orion covers all the famix entities but extending it should not
be a problem,
It is easy and fast to extend FAMIX entities.
Jannik
> What would be good is that orion gets the trick that andy and veronica implemented in
their implementation of Orion
>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev