Hi Martin,
Thanks, that is what I thought. So, we should check this possible bug.
Cheers, Doru
On 5 Jan 2011, at 15:16, Martin Dias wrote:
On Wed, Jan 5, 2011 at 9:37 AM, Tudor Girba tudor.girba@gmail.com wrote:
Hmm, on the other hand, I have a question about the logic behind the Fame Fuel. I did not check the implementation too closely, but I would expect the Fame entities to be traversed in the same way as for the MSE export.
Yes! I used the Fame meta-descriptions.
However, there was a bug with FAMIXAccess that when the isWrite flag was nil, isRead would raise an error (it is fixed in the meantime). This appeared when I exported the model with MSE, but it did not appear when I used Fuel. This leads me to believe that export has a different logic.
That should be a bug, because my goal was to imitate MSE logic. En fact I made two prototypes before this version that reused the Fame/MSE implementation classes, but the result was not so good, so finally I wrote the logic in other way.
Am I correct? If yes, I would like to know what are the implications.
Do I answered the question?
Cheers, Doru
On 5 Jan 2011, at 10:26, Mariano Martinez Peck wrote:
On Wed, Jan 5, 2011 at 12:51 AM, Tudor Girba tudor.girba@gmail.com wrote: This is what I got for the export:
Fuel: 76481. MSE: 201837.
Excellent!!
There are several reports on the fuel page: http://rmod.lille.inria.fr/web/pier/software/Fuel
yes, but I wanted to see yours ;)
Cheers, Doru
On 4 Jan 2011, at 18:23, Mariano Martinez Peck wrote:
On Tue, Jan 4, 2011 at 6:14 PM, Tudor Girba tudor.girba@gmail.com wrote: Excellent job, Martin!
I tested it briefly with ArgoUML (194936 objects), and I get really cool results:
- Fuel import: 12988 ms
- MSE import: 65543 ms
Tudor, and the export ?
thanks
mariano
Also, the size of the file is 14.9 MB instead of 30 MB.
This package will go in the default Moose configuration. Could you please add a ConfigurationOfFuel with a default configuration so that we can load it easily from the ConfigurationOfMoose?
Cheers, Doru
On 4 Jan 2011, at 14:53, Martin Dias wrote:
Hi
I have been working in a object serialization framework last months, called Fuel. And in order to test it in a real case, I made a package that adds new import and export commands to Moose panel.
Fuel and this Moose extension still need a lot of work on functionalities and performance optimizations.
The idea was to imitate the export/import MSE capabilities, and at least in the basic cases I tried, it imitates well, but I have not too much experience with Moose, so it would be nice to have feedback of more experienced users, and to know if it could be useful or not.
I have tried in Moose 4.1 release and Moose 4.3 build #77 from http://hudson.moosetechnology.org/job/moose-latest-dev/
More information at the end of this website:
http://rmod.lille.inria.fr/web/pier/software/Fuel
To install:
Gofer new squeaksource: 'Fuel'; version: 'Fuel-MartinDias.78'; version: 'FuelFameExtension-MartinDias.21'; load.
Cheers! Martin _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Some battles are better lost than fought."
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
"We are all great at making mistakes."
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
"Every thing has its own flow."
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
"Every thing has its own flow."