November 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Loading projects and building your own images with Metacello

by Sean P. DeNigris

Thanks, Mariano. This is inspiring me to utilize Metacello more for my personal images. I've been using a lot of little Gofer scripts, but this looks cleaner and more flexible. Sean -- View this message in context: http://forum.world.st/Loading-projects-and-building-your-own-images-with-Me… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 21, 2011

Re: [Pharo-project] Moving a file

by Sean P. DeNigris

StÃ©phane Ducasse wrote > > Did you write some tests? > Not yet. -- View this message in context: http://forum.world.st/Moving-a-file-tp3983916p4092117.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 21, 2011

Re: [Pharo-project] Startup Preferences

by Esteban Lorenzano

yeah... the repository cache could be defaulted to there too El 21/11/2011, a las 4:53a.m., Damien Cassou escribiÃ³: > Very good idea indeed. I'm just concerned about the directory location: > > On Sat, Nov 19, 2011 at 2:13 PM, Benjamin > <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> ~/.pharo#{version} > > what about using the freedesktop.org specification of using > $HOME/.config to put configuration files? What about having the > #{version} as a subdirectory? That would result in something like: > > ~/.config/pharo/#{version}/ > > Also, it could be interesting to load all files in > ~/.config/pharo/general/, whatever the version of Pharo. This would be > useful to set passwords for example. > > The specification is at > http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html#vari… > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

Nov. 21, 2011

Re: [Pharo-project] scripting a package backup

by jannik.laval

On Nov 21, 2011, at 10:19 , Lukas Renggli wrote: > > > On Monday, 21 November 2011, jannik.laval <jannik.laval(a)gmail.com> wrote: > > Hi Lukas, > > > > What I need is the information stored in the Monticello objects (I do not know which one for now). > > I would like to do something like that: > > > > === > > Gofer new > > url: (MCSomething new: myPackage) projectUrl; > > version: currentVersion; > > fetch > > Gofer new > > directory: myDirectory; > > package: myPackage; > > push > > === > > > > Do you know how to get the Monticello distant url of a package ? and to get the current version ? > > The package does not know its URL, but the working copy (MCWorkingCopy allManagers) has a repository group containing all the associated repositories. Thank you Lukas, I will search in this way. Cheers, Jannik > > > I saw that the Monticello GUI does it. > > Then look in that code :-) > > Lukas > > > > > Thank you > > Jannik > > > > > > On Nov 18, 2011, at 22:07 , Lukas Renggli wrote: > > > >> On 18 November 2011 21:40, jannik.laval <jannik.laval(a)gmail.com> wrote: > >>> My point is that I do not want to know the remote repository. > >>> I just want to copy my current package on a local repository. > >>> > >>> When you write squeaksource: 'remote', you suppose that your package is on squeaksource in the project named remote. > >>> That is that information that I do not want to give. > >> > >> Everything that is not your package cache is remote. It can also be a > >> directory on your HD, a GOODS database, or whatever ... > >> > >>> I need the process that creates the mcz file, to copy it on a repository. > >> > >> I do not get it. Maybe you want to give more context? > >> > >>> Jannik > >>> > >>> On Nov 18, 2011, at 18:37 , Lukas Renggli wrote: > >>> > >>>> On 18 November 2011 16:11, jannik.laval <jannik.laval(a)gmail.com> wrote: > >>>>> Yes, that is my problem ! > >>>>> I want to export packages in a repository outside the package cache and with an empty package cache. > >>>>> The problem to pull the version first, is to know the url of the version. > >>>> > >>>> I don't get your problem! > >>>> > >>>> Gofer new > >>>> squeaksource: 'remote'; > >>>> version: 'Foo-123'; " or package: 'Foo' if you want > >>>> all version " > >>>> fetch > >>>> > >>>> Gofer new > >>>> squeaksource: 'backup'; > >>>> version: 'Foo-123'; > >>>> push > >>>> > >>>> > >>>> > >>>>> > >>>>> Jannik > >>>>> > >>>>> On Nov 18, 2011, at 16:03 , Lukas Renggli wrote: > >>>>> > >>>>>> It is all relative to your package cache, so maybe you have to pull > >>>>>> the versions first? > >>>>>> > >>>>>> On 18 November 2011 10:53, jannik.laval <jannik.laval(a)gmail.com> wrote: > >>>>>>> Hi Lukas, > >>>>>>> I tried: > >>>>>>> > >>>>>>> === > >>>>>>> RPackageOrganizer packageInfoNames do:[:e | > >>>>>>> Gofer new > >>>>>>> directory: '/Users/janniklaval/Desktop/MCPackages'; > >>>>>>> package: e; > >>>>>>> push. > >>>>>>> ] > >>>>>>> === > >>>>>>> but if the package was not modified, it does not copy the source files. > >>>>>>> > >>>>>>> Jannik > >>>>>>> > >>>>>>> On Nov 18, 2011, at 10:38 , Lukas Renggli wrote: > >>>>>>> > >>>>>>>> It would be trivial with Gofer: > >>>>>>>> > >>>>>>>> Gofer new > >>>>>>>> squeaksource: 'backupproject'; > >>>>>>>> package: 'P1'; > >>>>>>>> package: 'P2'; > >>>>>>>> package: 'P3'; > >>>>>>>> push > >>>>>>>> > >>>>>>>> Now of course you can find your script a working script in the class GoferPush. > >>>>>>>> > >>>>>>>> Lukas > >>>>>>>> > >>>>>>>> On 18 November 2011 10:03, jannik.laval <jannik.laval(a)gmail.com> wrote: > >>>>>>>>> Hi Pharoers, > >>>>>>>>> > >>>>>>>>> I would like to backup my packages in a repository with a script. > >>>>>>>>> I have one constraint: I need to use Monticello (eg, not gofer or metacello). > >>>>>>>>> And I do not want to have a version incrementation. > >>>>>>>>> > >>>>>--- > > Jannik Laval > > > > > > > > -- > Lukas Renggli (mobile) > http://www.lukas-renggli.ch --- Jannik Laval

Nov. 21, 2011

Re: [Pharo-project] scripting a package backup

by Lukas Renggli

On Monday, 21 November 2011, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hi Lukas, > > What I need is the information stored in the Monticello objects (I do not know which one for now). > I would like to do something like that: > > === > Gofer new > url: (MCSomething new: myPackage) projectUrl; > version: currentVersion; > fetch > Gofer new > directory: myDirectory; > package: myPackage; > push > === > > Do you know how to get the Monticello distant url of a package ? and to get the current version ? The package does not know its URL, but the working copy (MCWorkingCopy allManagers) has a repository group containing all the associated repositories. > I saw that the Monticello GUI does it. Then look in that code :-) Lukas > > Thank you > Jannik > > > On Nov 18, 2011, at 22:07 , Lukas Renggli wrote: > >> On 18 November 2011 21:40, jannik.laval <jannik.laval(a)gmail.com> wrote: >>> My point is that I do not want to know the remote repository. >>> I just want to copy my current package on a local repository. >>> >>> When you write squeaksource: 'remote', you suppose that your package is on squeaksource in the project named remote. >>> That is that information that I do not want to give. >> >> Everything that is not your package cache is remote. It can also be a >> directory on your HD, a GOODS database, or whatever ... >> >>> I need the process that creates the mcz file, to copy it on a repository. >> >> I do not get it. Maybe you want to give more context? >> >>> Jannik >>> >>> On Nov 18, 2011, at 18:37 , Lukas Renggli wrote: >>> >>>> On 18 November 2011 16:11, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>> Yes, that is my problem ! >>>>> I want to export packages in a repository outside the package cache and with an empty package cache. >>>>> The problem to pull the version first, is to know the url of the version. >>>> >>>> I don't get your problem! >>>> >>>> Gofer new >>>> squeaksource: 'remote'; >>>> version: 'Foo-123'; " or package: 'Foo' if you want >>>> all version " >>>> fetch >>>> >>>> Gofer new >>>> squeaksource: 'backup'; >>>> version: 'Foo-123'; >>>> push >>>> >>>> >>>> >>>>> >>>>> Jannik >>>>> >>>>> On Nov 18, 2011, at 16:03 , Lukas Renggli wrote: >>>>> >>>>>> It is all relative to your package cache, so maybe you have to pull >>>>>> the versions first? >>>>>> >>>>>> On 18 November 2011 10:53, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>>>> Hi Lukas, >>>>>>> I tried: >>>>>>> >>>>>>> === >>>>>>> RPackageOrganizer packageInfoNames do:[:e | >>>>>>> Gofer new >>>>>>> directory: '/Users/janniklaval/Desktop/MCPackages'; >>>>>>> package: e; >>>>>>> push. >>>>>>> ] >>>>>>> === >>>>>>> but if the package was not modified, it does not copy the source files. >>>>>>> >>>>>>> Jannik >>>>>>> >>>>>>> On Nov 18, 2011, at 10:38 , Lukas Renggli wrote: >>>>>>> >>>>>>>> It would be trivial with Gofer: >>>>>>>> >>>>>>>> Gofer new >>>>>>>> squeaksource: 'backupproject'; >>>>>>>> package: 'P1'; >>>>>>>> package: 'P2'; >>>>>>>> package: 'P3'; >>>>>>>> push >>>>>>>> >>>>>>>> Now of course you can find your script a working script in the class GoferPush. >>>>>>>> >>>>>>>> Lukas >>>>>>>> >>>>>>>> On 18 November 2011 10:03, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>>>>>> Hi Pharoers, >>>>>>>>> >>>>>>>>> I would like to backup my packages in a repository with a script. >>>>>>>>> I have one constraint: I need to use Monticello (eg, not gofer or metacello). >>>>>>>>> And I do not want to have a version incrementation. >>>>>>>>> >>>>>--- > Jannik Laval > > > -- Lukas Renggli (mobile) http://www.lukas-renggli.ch

Nov. 21, 2011

Re: [Pharo-project] scripting a package backup

by jannik.laval

Hi Lukas, What I need is the information stored in the Monticello objects (I do not know which one for now). I would like to do something like that: === Gofer new url: (MCSomething new: myPackage) projectUrl; version: currentVersion; fetch Gofer new directory: myDirectory; package: myPackage; push === Do you know how to get the Monticello distant url of a package ? and to get the current version ? I saw that the Monticello GUI does it. Thank you Jannik On Nov 18, 2011, at 22:07 , Lukas Renggli wrote: > On 18 November 2011 21:40, jannik.laval <jannik.laval(a)gmail.com> wrote: >> My point is that I do not want to know the remote repository. >> I just want to copy my current package on a local repository. >> >> When you write squeaksource: 'remote', you suppose that your package is on squeaksource in the project named remote. >> That is that information that I do not want to give. > > Everything that is not your package cache is remote. It can also be a > directory on your HD, a GOODS database, or whatever ... > >> I need the process that creates the mcz file, to copy it on a repository. > > I do not get it. Maybe you want to give more context? > >> Jannik >> >> On Nov 18, 2011, at 18:37 , Lukas Renggli wrote: >> >>> On 18 November 2011 16:11, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>> Yes, that is my problem ! >>>> I want to export packages in a repository outside the package cache and with an empty package cache. >>>> The problem to pull the version first, is to know the url of the version. >>> >>> I don't get your problem! >>> >>> Gofer new >>> squeaksource: 'remote'; >>> version: 'Foo-123'; " or package: 'Foo' if you want >>> all version " >>> fetch >>> >>> Gofer new >>> squeaksource: 'backup'; >>> version: 'Foo-123'; >>> push >>> >>> >>> >>>> >>>> Jannik >>>> >>>> On Nov 18, 2011, at 16:03 , Lukas Renggli wrote: >>>> >>>>> It is all relative to your package cache, so maybe you have to pull >>>>> the versions first? >>>>> >>>>> On 18 November 2011 10:53, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>>> Hi Lukas, >>>>>> I tried: >>>>>> >>>>>> === >>>>>> RPackageOrganizer packageInfoNames do:[:e | >>>>>> Gofer new >>>>>> directory: '/Users/janniklaval/Desktop/MCPackages'; >>>>>> package: e; >>>>>> push. >>>>>> ] >>>>>> === >>>>>> but if the package was not modified, it does not copy the source files. >>>>>> >>>>>> Jannik >>>>>> >>>>>> On Nov 18, 2011, at 10:38 , Lukas Renggli wrote: >>>>>> >>>>>>> It would be trivial with Gofer: >>>>>>> >>>>>>> Gofer new >>>>>>> squeaksource: 'backupproject'; >>>>>>> package: 'P1'; >>>>>>> package: 'P2'; >>>>>>> package: 'P3'; >>>>>>> push >>>>>>> >>>>>>> Now of course you can find your script a working script in the class GoferPush. >>>>>>> >>>>>>> Lukas >>>>>>> >>>>>>> On 18 November 2011 10:03, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>>>>> Hi Pharoers, >>>>>>>> >>>>>>>> I would like to backup my packages in a repository with a script. >>>>>>>> I have one constraint: I need to use Monticello (eg, not gofer or metacello). >>>>>>>> And I do not want to have a version incrementation. >>>>>>>> >>>>>>>> Does someone have any script or any way to do that ? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Jannik >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Lukas Renggli >>>>>>> www.lukas-renggli.ch >>>>>>> >>>>>> >>>>>> --- >>>>>> Jannik Laval >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> www.lukas-renggli.ch >>>>> >>>> >>>> --- >>>> Jannik Laval >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> --- >> Jannik Laval >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > --- Jannik Laval

Nov. 21, 2011

Re: [Pharo-project] Startup Preferences

by Damien Cassou

Very good idea indeed. I'm just concerned about the directory location: On Sat, Nov 19, 2011 at 2:13 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > ~/.pharo#{version} what about using the freedesktop.org specification of using $HOME/.config to put configuration files? What about having the #{version} as a subdirectory? That would result in something like: ~/.config/pharo/#{version}/ Also, it could be interesting to load all files in ~/.config/pharo/general/, whatever the version of Pharo. This would be useful to set passwords for example. The specification is at http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html#vari… -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Nov. 21, 2011

Re: [Pharo-project] #ifCurtailed:

by Igor Stasenko

On 20 November 2011 16:19, Philippe Marschall <kustos(a)gmx.net> wrote: > Hi > > Am I right that the argument to #ifCurtailed: is run in a different process > (like #ensure: in an exception case)? > not necessary. A non-local returns are also trapped by it: [ ^ xx ] ifCurtailed: [ ... ] > Cheers > Philippe > > > -- Best regards, Igor Stasenko.

Nov. 21, 2011

[Pharo-project] [update 1.4] #14233

by StÃ©phane Ducasse

14233 ----- - Issue 5004: Decompiler miss-initialize the Encoder literalStream with a ReadStream when a WriteStream is expected. Thanks Nicolas Cellier. http://code.google.com/p/pharo/issues/detail?id=5004

Nov. 20, 2011

Re: [Pharo-project] Zinc Post requests

by Sven Van Caekenberghe

On 20 Nov 2011, at 22:30, Lukas Renggli wrote: > Yes please, because the current Zinc does not work otherwise for POST requests. Name: Zinc-Seaside-SvenVanCaekenberghe.21 Author: SvenVanCaekenberghe Time: 20 November 2011, 10:55:28 pm UUID: 2d3dd79e-7210-4e42-ba85-b08e6f74b689 Ancestors: Zinc-Seaside-SvenVanCaekenberghe.20 added a new implementation of ZnZincServerAdaptor>>#requestBodyFor: this idea is that we have to return a String that contains the raw entity bytes. we don't do this when #requestFieldsFor: returns that data in an other form (i.e. when it is a POST with application/x-www-form-urlencoded or multipart/form-data). still this is inefficient for ZnStringEntity objects with a non-trivial encoding since they will be reencoded after just being decoded.

Nov. 20, 2011