15 Mar
2011
15 Mar
'11
10:30 p.m.
Hi Jannik,
On 15 Mar 2011, at 14:49, jannik.laval wrote:
Hi,
I am not jumping to conclusion, I am beginning discussion :)
Ok, then I misunderstood your statement :)
With a small time to check, it seems that it is
MooseCook that is broken.
Here is the example: http://dl.dropbox.com/u/7739334/seaside30-28062010.mse.zip
I put it in Dropbox because of 3Mb.
You can load it in Moose without problems.
Now, if you browse "All Model Classes" and you select one class, there is an
error. because a FamixClass does not now a parentType.
It seems that there is a change in scope.
I took a look at your case study. The problem stems from a Smalltalk importer bug that was
reported in Aug 2008 (!), and that is now finally fixed: the implicit variable used to be
attached to the class and now it is attached to the method:
http://code.google.com/p/moose-technology/issues/detail?id=16
Cheers,
Doru
Cheers,
Jannik
On Mar 15, 2011, at 13:50 , Tudor Girba wrote:
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem
understanding."
Hi,
I am on the run now, but what MSE files do not work? The changes to the FAMIX meta-model
should not have broken anything.
I have files created in 2009 that load just fine. So, before jumping to conclusions,
please let's take a look at the actual cases. Could you make available such an MSE
file?
Cheers,
Doru
On 15 Mar 2011, at 13:28, Simon Denier wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev What are the problems exactly?
One thing would be to add a Mse version metadata in each file. I think Cyrille has
started something similar.
Simon
On 15 mars 2011, at 12:52, "jannik.laval" <jannik.laval(a)gmail.com>
wrote:
--
www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi all,
We are using Moose 4.3 and we have lots of problems due to the metamodel changes from 4.1
to 4.3.
For example all my mse files generated in 4.1 are obsolete in 4.3, but we develop tools
in 4.3 not compatible with 4.1.
The situation is not really cool, and the message sent by this problem also.
To solve this problem, I would propose to replace the version 4.3 by a version 5.0.
Like that we can build tools to move from version 4.x to 5.x.
And the message is better.
What is your opinion about these changes and what is the impact on the community ?
Thanks
Jannik
_______________________________________________
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