- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Call for help for reviewing code

by Sean P. DeNigris

StÃ©phane Ducasse wrote > > So can you give a hand and have a look the fixes. > I just looked through about 6 issues marked FixReviewNeeded. I loaded the fixes and requested more info, and learned a few things: * it's hard to deal with issues that do not accurately explain the issue, preferably in a reproducible way * this is especially important when dealing with system critical things, e.g. the Debugger, that lead to image freezes and emergency evaluators. * including tests is key because it's not always clear what the fix is even supposed to do HTH, Sean -- View this message in context: http://forum.world.st/Call-for-help-for-reviewing-code-tp3992746p4092471.ht… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 21, 2011

Re: [Pharo-project] Startup Preferences

by Benjamin

I definitively think that you should have a kind of preference folder, because we want to have some information centralized The cache may be a good example, startup scripts, and probably more stuff :) On Nov 21, 2011, at 1:05 PM, Esteban Lorenzano wrote: > 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? Why not :) When I choose the path, I was thinking of my linux distrib, with all the ~/.applicationName folders :) I can easily be changed, and that's also why I sent this mail. To discuss about what is a good name for this folder :) >> 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… >> I just pushed a new version when scripts are from ~/.config/pharo/#{version}/startup.st or ~/.config/pharo/general/* Like that, you have the local script for each version + the general scripts from the general directory. Tomorrow I will add more examples (and probably a way to set the name of general scripts). Ben >> -- >> 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] Loading projects and building your own images with Metacello

by Mariano Martinez Peck

On Mon, Nov 21, 2011 at 1:35 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > 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. > > Thanks :) > 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. > > -- Mariano http://marianopeck.wordpress.com

Nov. 21, 2011

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

by Dale Henrichs

Mariano ... I was waiting for the video and or slides to show up, but a post is even better ... I put a couple of links to your post up on the Metacello wiki... Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <marianopeck(a)gmail.com> | To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr>, "A friendly place where any question about pharo is | welcome" <pharo-users(a)lists.gforge.inria.fr>, metacello(a)googlegroups.com | Sent: Saturday, November 19, 2011 12:33:32 PM | Subject: [Metacello] Loading projects and building your own images with Metacello | | Hi. I usually don't advertise my blog, but I think this post may be | interesting to some of you: | http://marianopeck.wordpress.com/2011/11/19/loading-projects-and-building-y… | | Cheers, | | -- | Mariano | http://marianopeck.wordpress.com | |

Nov. 21, 2011

Re: [Pharo-project] Fwd: [squeak-dev] OmniBrowser and ToolBuilder

by Sean P. DeNigris

Lukas Renggli wrote > > The latest GUI... brings resizable column > Thank you, Lukas! -- View this message in context: http://forum.world.st/Fwd-squeak-dev-OmniBrowser-and-ToolBuilder-tp4088492p… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 21, 2011

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