What I would like to have is -> A way to save files per package in the image in a virtual file system -> Monticello support to save that virtual file system as part of the .mcz We could clean up *a lot* of methods in the image and even save memory: right now the "save Base64 encoded strings in methods" means that we have the data two times: the string literal and the object created from it. (and the source on disk). On Sep 3, 2013, at 11:23 AM, phil@highoctane.be wrote:
yes that would be great to have indeed.
On Tuesday, September 3, 2013, J.F. Rick <self@je77.com> wrote:
Hi everyone, I've been trying to move things over to Pharo and may be a bit more active on the list. Part of that is trying to use smalltalkhub to manage my code. Since I do a lot of visual work, I tend to have a lot of images (and sounds) to manage. I'd like to be able to distribute them easily but I can't seem to find a way to upload them to a shared directory. In Squeak, there was this idea of .SAR files for distributing files. Is there a good solution for this outside of the Seaside approach of embedding the file information in class methods. I'm talking about hundreds of files and multiple MBs here, rather than one or two small files. Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick
-- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos
High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium
Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller