Sean Thanks for this. At the back of my mind in asking was whether I want to use Fuel more extensively as a way of storing object structures long term on disk. If I move to Pharo 5 later on, will that have a new version of Fuel which will refuse to read my saved files, so that I will have to convert all my files to the new version? As far as I can see, I could not do that using the device you suggest; I would have to have one version of Fuel which could materialize files of version 193 and re-serialize to version 194. I see that both FLSerializer and FLMaterializer have class side methods called #currentVersion; could I set those to give different version numbers, and do the conversion that way?
Alternatively, I could use Sven's suggestion of STON, provided that will not go the way of version changes without backward compatibility. I suppose a lot will depend on the efficiency of the two approaches, both in terms of storage space on disk and in conversion times. Thanks to both for the suggestions. I have food for thought and ideas for further experiment. Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Sean P. DeNigris Sent: 28 May 2015 17:39 To: pharo-users@lists.pharo.org Subject: Re: [Pharo-users] How to move data between Pharo versions Peter Kenny wrote > My question is what should I have done? There is usually an overlap between the Fuel versions loadable in consecutive Pharo versions, so you have to either (via Metacello) upgrade the Fuel in your source image, or downgrade in the target image, so that you can save and move the data without conflict. ----- Cheers, Sean -- View this message in context: http://forum.world.st/How-to-move-data-between-Pharo-versions-tp4829102p4829 115.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
