29 May
2012
29 May
'12
10:18 p.m.
Hi,
Excellent!
Let's move on. I do not think there are many data that depend on 1.6. And if there are
cases, people can just do the migration.
The Moose image is built by loading ConfigurationOfFuelMooseExtension #stable. Please go
ahead and upgrade this.
On a related note, perhaps it would be a good idea to change the name of the file
extensions to be something like .fuel1dot8 to denote the version of the format.
Cheers,
Doru
On 29 May 2012, at 21:42, Mariano Martinez Peck wrote:
Hi Doru. I have updated FuelMooseExtension to work
with the latest stable version of Fuel 1.8. I think this is worth it because:
1) Right now you are using an old version of Fuel (1.6) which is like an year ago. The
older it is the more difficult it will be in the future to update.
2) If you don't take into account the time to compute attributes we can have
improvement up to 30% in export time.
3) Fuel 1.8 is integrated by default in Pharo 2.0 now, meaning that you will have
problems when moving Moose to Pharo 2.0 (because you would need 1.6).
Of course the bad news is that if you have already exported files you won't be able
to import them with this new version.
If you agree, let me know. I will create a new version 1.5 in
ConfigurationOfFuelMooseExtension but I don't know how the Moose image is built (it
seems it is not using ConfigurationOfFuel).
Cheers
--
Mariano
http://marianopeck.wordpress.com
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Speaking louder won't make the point worthier."