June 2018 - Pharo-users - lists.pharo.org

Scripting package updates

by HernÃ¡n Morales Durand

Hi guys, I am working on Pharo 6.1 and already have an image with multiple packages loaded via Iceberg. Every time I want to load other's remote changes to my image I have to open the Iceberg UI and select repository, synchronize, update, hit fetch + merge (or pull). Does anyone has a script to automate this process and avoid manually open the UI, etc? Cheers, HernÃ¡n

June 5, 2018

Re: [Pharo-users] more on "can't get keyboard shortcuts to work on Mac"

by Gregg Williams

Tim and Ben, Thanks for your help. Sorry for not being clear. When I said "I just can't get keyboard shortcuts to work on Mac," what I should have said is "I just can't get Pharo-specific shortcuts to work on the Macintosh implementation of Pharo" (6.1 is what I'm using BTW). Maybe I should have said "keymap shortcuts"? I'm talking about things like Meta+Shift+f for 'find class', and Meta+x, Meta+m for 'remove method'. I've looked for what the definition of Meta is for Mac OS. All I can find is meta-click is Shift+Option+click, but that doesn't seem to work. Option + <many keys> gives "special characters" like â, Ã, and Å. I hope that now you can simply say, "Oh, of course, what you need to do isâ¦". Thanks! > I just can't get keyboard shortcuts to work on Mac. I?ve tried a lot of stuff, more than I can list here. Here are some things I?ve tried: > > * searching the Pharo by Example book > * turning off all Mac keyboard-macro programs > * switching from extended to standard US keyboard > * looking at options in System Preferences > Keyboard > > > If you?re on the Mac, do you have this problem? If so, what?s your solution? Thanks! >

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Ben Coman

On 5 June 2018 at 00:59, Tim Mackinnon <tim(a)testit.works> wrote: > > P7 will force you to be in the right branch or you will not be able to > doâ¦ almost anything :) > > you can have two (or ten) images opened at once and work on them, but at > a moment you will need to ârepairâ each image to commit. > > So are we saying that the easiest and less complicated option is to just > have local copies for every project. These days, disk space is pretty cheap > (and projects arenât that big source wise)? > For me its not the disk space, but the download time to sync the full Pharo repo if I want to work on an issue. I often wonder how hard it would be to have a master copy of the Pharo repo and each Image does something like --reference or --shared,, but I'm not familiar with their operation and issues except what I read here... * https://randyfay.com/content/reference-cache-repositories-speed-clones-git-… * https://stackoverflow.com/questions/23304374/what-are-the-differences-betwe… * http://lists-archives.com/git/494327-clarify-git-clone-local-shared-referen… * http://blog.plataformatec.com.br/2013/05/how-to-properly-mirror-a-git-repos… cheers -ben > > Iâm sure for others it might be a bigger deal - but Iâm trying to > understand what is the easiest option to avoid gotchaâs (that more advanced > guys can better cope with) > > Tim > > > On 4 Jun 2018, at 14:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > hi, > > > >> On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> > >> Evan Donahue <emdonahu(a)gmail.com> wrote: > >>> I have "Share repositories between images" checked in both images, > >> > >> Share repositories at the moment just provides a shared location on disk > >> where the repositories are located. That is only useful if you are very > >> disciplined about stashing and switching to the branch needed for your > >> current image, and you only have one image open at a time. > > > > not really. > > P7 will force you to be in the right branch or you will not be able to > doâ¦ almost anything :) > > you can have two (or ten) images opened at once and work on them, but at > a moment you will need to ârepairâ each image to commit. > > > > Esteban > > > >> > >> Stephan > >> > >> > >> > >> > >> > > > > > > >

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Esteban Lorenzano

> On 4 Jun 2018, at 18:59, Tim Mackinnon <tim(a)testit.works> wrote: > >> P7 will force you to be in the right branch or you will not be able to doâ¦ almost anything :) >> you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit. > > So are we saying that the easiest and less complicated option is to just have local copies for every project. These days, disk space is pretty cheap (and projects arenât that big source wise)? is about you :) > Iâm sure for others it might be a bigger deal - but Iâm trying to understand what is the easiest option to avoid gotchaâs (that more advanced guys can better cope with) most of the time you do not switch all the time. most of the time you can work on a feature in image A that will detach image B. But then, most of the time you will want to update image B (or kept it detached, is your choice). cheers, Esteban > > Tim > >> On 4 Jun 2018, at 14:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> hi, >> >>> On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> Evan Donahue <emdonahu(a)gmail.com> wrote: >>>> I have "Share repositories between images" checked in both images, >>> >>> Share repositories at the moment just provides a shared location on disk >>> where the repositories are located. That is only useful if you are very >>> disciplined about stashing and switching to the branch needed for your >>> current image, and you only have one image open at a time. >> >> not really. >> P7 will force you to be in the right branch or you will not be able to doâ¦ almost anything :) >> you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit. >> >> Esteban >> >>> >>> Stephan >>> >>> >>> >>> >>> >> >> > >

June 4, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Peter UhnÃ¡k

> but Iâm trying to understand what is the easiest option to avoid gotchaâs (that more advanced guys can better cope with) I guess the question is whether you want to handle conflict resolutions directly with git, or through iceberg. I've been using separate clones for each image for a long time and it works well. Especially when you are also modifying non-smalltalk files in each clone. Peter On Mon, Jun 4, 2018 at 7:26 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > . > > P7 will force you to be in the right branch or you will not be able to > > doâ¦ almost anything :) > > you can have two (or ten) images opened at once and work on them, but at > > a moment you will need to ârepairâ each image to commit. > > Ah, nice. How is that guarded against concurrent access, live-lock & > dead-lock? > > Stephan > > > >

June 4, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Stephan Eggermont

Esteban Lorenzano <estebanlm(a)gmail.com> wrote: . > P7 will force you to be in the right branch or you will not be able to > doâ¦ almost anything :) > you can have two (or ten) images opened at once and work on them, but at > a moment you will need to ârepairâ each image to commit. Ah, nice. How is that guarded against concurrent access, live-lock & dead-lock? Stephan

June 4, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Tim Mackinnon

> P7 will force you to be in the right branch or you will not be able to doâ¦ almost anything :) > you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit. So are we saying that the easiest and less complicated option is to just have local copies for every project. These days, disk space is pretty cheap (and projects arenât that big source wise)? Iâm sure for others it might be a bigger deal - but Iâm trying to understand what is the easiest option to avoid gotchaâs (that more advanced guys can better cope with) Tim > On 4 Jun 2018, at 14:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > hi, > >> On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> Evan Donahue <emdonahu(a)gmail.com> wrote: >>> I have "Share repositories between images" checked in both images, >> >> Share repositories at the moment just provides a shared location on disk >> where the repositories are located. That is only useful if you are very >> disciplined about stashing and switching to the branch needed for your >> current image, and you only have one image open at a time. > > not really. > P7 will force you to be in the right branch or you will not be able to doâ¦ almost anything :) > you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit. > > Esteban > >> >> Stephan >> >> >> >> >> > >

June 4, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Esteban Lorenzano

hi, > On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Evan Donahue <emdonahu(a)gmail.com> wrote: >> I have "Share repositories between images" checked in both images, > > Share repositories at the moment just provides a shared location on disk > where the repositories are located. That is only useful if you are very > disciplined about stashing and switching to the branch needed for your > current image, and you only have one image open at a time. not really. P7 will force you to be in the right branch or you will not be able to doâ¦ almost anything :) you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit. Esteban > > Stephan > > > > >

June 4, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Stephan Eggermont

Evan Donahue <emdonahu(a)gmail.com> wrote: > I have "Share repositories between images" checked in both images, Share repositories at the moment just provides a shared location on disk where the repositories are located. That is only useful if you are very disciplined about stashing and switching to the branch needed for your current image, and you only have one image open at a time. Stephan

June 4, 2018

Re: [Pharo-users] metacello and github under a custom domain

by Thierry Goubier

2018-06-04 10:42 GMT+02:00 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > On 03/06/2018 16:42, Tudor Girba wrote: >> Hi, >> > > Hi, > >> I am working with a GitHub enterprise installation that resides under a custom domain (e.g., github.example.com) >> >> I can clone the repository using Iceberg and ssh: git@github.example.com:user/repo.git >> >> How can I tell Metacello to load a baseline from that repository? >> > > Currently it's not possible in Metacello to support custom urls :( GitFileTree provides for custom url in Metacello. Doru request would be: Metacello new baseline: 'Example'; repository: 'gitfiletree://github.example.com/user/repo'; load I've been using various git entreprise installation with that scheme for the past 3 or 4 years, via ssh mostly, but https. I believe there is a discussion underway to do the same with, maybe tonel:// urls. Regards, Thierry > There was some discussions about extending Metacello but until now > nobody got the time to begin an implementation of it. > > See: https://groups.google.com/forum/#!topic/metacello/QbpngL6Jhg8 > >> Cheers, >> Doru >> >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "To lead is not to demand things, it is to make them happen." >> >> >> >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 4, 2018