September 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Distributing File Resources

by Tudor Girba

Hi Jeff, Would you have an interest looking into this and prototyping a solution? Doru On Tue, Sep 3, 2013 at 12:44 PM, J.F. Rick <self(a)je77.com> wrote: > I'm surprised this doesn't exist yet. It seems like it would be a natural > thing to be part of Monticello. > > Cheers, > > Jeff > > > On Tue, Sep 3, 2013 at 11:29 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> 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(a)highoctane.be wrote: >> >> yes that would be great to have indeed. >> >> >> >> On Tuesday, September 3, 2013, J.F. Rick <self(a)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 >> >> >> >> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 3, 2013

Re: [Pharo-dev] SmallInteger infamous bug is back in town

by Esteban Lorenzano

is that I don't know exactly when it returned. And know that involves invest time that I really don'y have this days (you wouldn't know the amount of things I have/want to finish before esug :P) but yes, if I find some time, I will check which version is the offending one :) Esteban On Sep 3, 2013, at 12:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > can the 'latest version' not be retracted ? > > On 03 Sep 2013, at 11:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> ... most probably due to errors in the integration process. >> I spotted it in last vm :( >> >> sadly, I do not have time to tackle it before ESUG, so... until I fix it, please don't use the latest vm. >> Instead, take one of the olders if you need to download a new one. >> >> I'm sorry for the inconvenience :( >> >> Esteban >> >> > >

Sept. 3, 2013

Re: [Pharo-dev] Distributing File Resources

by J.F. Rick

I'm surprised this doesn't exist yet. It seems like it would be a natural thing to be part of Monticello. Cheers, Jeff On Tue, Sep 3, 2013 at 11:29 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 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(a)highoctane.be wrote: > > yes that would be great to have indeed. > > > > On Tuesday, September 3, 2013, J.F. Rick <self(a)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 > > > > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Sept. 3, 2013

Re: [Pharo-dev] SmallInteger infamous bug is back in town

by Sven Van Caekenberghe

can the 'latest version' not be retracted ? On 03 Sep 2013, at 11:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > ... most probably due to errors in the integration process. > I spotted it in last vm :( > > sadly, I do not have time to tackle it before ESUG, so... until I fix it, please don't use the latest vm. > Instead, take one of the olders if you need to download a new one. > > I'm sorry for the inconvenience :( > > Esteban > >

Sept. 3, 2013

Re: [Pharo-dev] Distributing File Resources

by StÃ©phane Ducasse

Managing resources is not well handled and it would be great to have some propositions. > Hi everyone, Welcome!! > > 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

Sept. 3, 2013

Re: [Pharo-dev] Distributing File Resources

by Marcus Denker

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(a)highoctane.be wrote: > yes that would be great to have indeed. > > > > On Tuesday, September 3, 2013, J.F. Rick <self(a)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 > > >

Sept. 3, 2013

Re: [Pharo-dev] Distributing File Resources

by phil＠highoctane.be

yes that would be great to have indeed. On Tuesday, September 3, 2013, J.F. Rick <self(a)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

Sept. 3, 2013

[update 3.0] #30365

by Marcus Denker

Sept. 3, 2013

SmallInteger infamous bug is back in town

by Esteban Lorenzano

... most probably due to errors in the integration process. I spotted it in last vm :( sadly, I do not have time to tackle it before ESUG, so... until I fix it, please don't use the latest vm. Instead, take one of the olders if you need to download a new one. I'm sorry for the inconvenience :( Esteban

Sept. 3, 2013

Re: [Pharo-dev] Win32 Console support

by Igor Stasenko

On 3 September 2013 00:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > is very nice :) > > but... a bit of criticism (and probably ignorant criticism :P) > > why those methods names? > sets, gets. colored, colorgreen... > > instead pharoish names? > I think because most of windows API functions named like that. Which sometimes better, to keep connection with original API.. Not sure about color names though :) > > Cheers, > Esteban > > On Sep 2, 2013, at 11:34 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > > I played with NativeBoost and the Windows API again > > this evening with the result to be able to open a > > native Win32 console window, influence title and colors > > and write to it from Pharo. This can be useful for coral > > and stdout support on Windows too. > > > > Attached is a screenshot. > > > > Cleaned up code will follow soon. > > > > Thx > > T. <winconsole.png> > > > -- Best regards, Igor Stasenko.

Sept. 3, 2013