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

Re: [Pharo-users] Pharo 7 and shortcuts

by Norbert Hartl

> Am 07.07.2018 um 17:08 schrieb Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > >> Le 07/07/2018 Ã 16:17, Ben Coman a Ã©crit : >> Any seeming agreement may just have been the nay-sayers falling silent since >> there seemed little chance of having it changed when it came as a >> done-deal with Nautilus. >> Personally I tried to conform to using the double-sequence-shortcuts >> but could never get over the cumbersome feel of it, >> to the point where in Nautlius I actually stopped using shortcuts and >> reverted to using context menus. >> >> I guess lovers of the double-sequence-shortcuts are now in that boat. >> I'm not sure there was much discussion around Calypso using >> single-key-shortcuts. >> But I'm personally very happy with this behaviour change introduced by >> Nautlius was reverted. >> I'm glad to using shortcuts in the System Browser again. >> > For my part I'm not because before I could delete/rename/add a > package/class/protocol/method without the mouse but now it became much > harder with simple key shortcut since it works only on the focused pane. > > But I guess this kind of things depend on everyone. > > Maybe it could be good to be able to customize it via settings. > I donât understand anyway why keyboard shortcuts are dependent on a tool. Shouldnât there be an abstraction mapping between action and shortcut? Norbert >> cheers -ben >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

July 7, 2018

Re: [Pharo-users] Pharo 7 and shortcuts

by Cyril Ferlicot D.

Le 07/07/2018 Ã 16:17, Ben Coman a Ã©critÂ : > Any seeming agreement may just have been the nay-sayers falling silent since > there seemed little chance of having it changed when it came as a > done-deal with Nautilus. > Personally I tried to conform to using the double-sequence-shortcuts > but could never get over the cumbersome feel of it, > to the point where in Nautlius I actually stopped using shortcuts and > reverted to using context menus. > > I guess lovers of the double-sequence-shortcuts are now in that boat. > I'm not sure there was much discussion around Calypso using > single-key-shortcuts. > But I'm personally very happy with this behaviour change introduced by > Nautlius was reverted. > I'm glad to using shortcuts in the System Browser again. > For my part I'm not because before I could delete/rename/add a package/class/protocol/method without the mouse but now it became much harder with simple key shortcut since it works only on the focused pane. But I guess this kind of things depend on everyone. Maybe it could be good to be able to customize it via settings. > cheers -ben > -- Cyril Ferlicot https://ferlicot.fr

July 7, 2018

Re: [Pharo-users] Pharo 7 and shortcuts

by Norbert Hartl

> Am 07.07.2018 um 16:17 schrieb Ben Coman <btc(a)openinworld.com>: > >> On 7 July 2018 at 20:35, Norbert Hartl <norbert(a)hartl.name> wrote: >> Maybe I missed an important discussion but as Iâm trying pharo7 now and I wonder about the keyboard shortcuts. >> >> Wasnât the old agreement moving to the multiple keys? So browsing senders with CMD-bn instead of the old CMD-n? > > Any seeming agreement may just have been the nay-sayers falling silent since > there seemed little chance of having it changed when it came as a > done-deal with Nautilus. > Personally I tried to conform to using the double-sequence-shortcuts > but could never get over the cumbersome feel of it, > to the point where in Nautlius I actually stopped using shortcuts and > reverted to using context menus. > > I guess lovers of the double-sequence-shortcuts are now in that boat. > I'm not sure there was much discussion around Calypso using > single-key-shortcuts. > But I'm personally very happy with this behaviour change introduced by > Nautlius was reverted. > I'm glad to using shortcuts in the System Browser again. > I cannot say I liked the idea of having double key sequences. You see Iâm using vi since 28 years and never emacs for exactly that reason. The important constraint for this seems to be number of shortcuts you need. I thought there is going to be more. So I convinced myself not to be sad having double key sequences. Iâm more or less glad about the revert, too. Best is that now the keyboard shortcuts are unified again ð Norbert > cheers -ben >

July 7, 2018

Re: [Pharo-users] Pharo 7 and shortcuts

by Ben Coman

On 7 July 2018 at 20:35, Norbert Hartl <norbert(a)hartl.name> wrote: > Maybe I missed an important discussion but as Iâm trying pharo7 now and I wonder about the keyboard shortcuts. > > Wasnât the old agreement moving to the multiple keys? So browsing senders with CMD-bn instead of the old CMD-n? Any seeming agreement may just have been the nay-sayers falling silent since there seemed little chance of having it changed when it came as a done-deal with Nautilus. Personally I tried to conform to using the double-sequence-shortcuts but could never get over the cumbersome feel of it, to the point where in Nautlius I actually stopped using shortcuts and reverted to using context menus. I guess lovers of the double-sequence-shortcuts are now in that boat. I'm not sure there was much discussion around Calypso using single-key-shortcuts. But I'm personally very happy with this behaviour change introduced by Nautlius was reverted. I'm glad to using shortcuts in the System Browser again. cheers -ben

July 7, 2018

Pharo 7 and shortcuts

by Norbert Hartl

Maybe I missed an important discussion but as Iâm trying pharo7 now and I wonder about the keyboard shortcuts. Wasnât the old agreement moving to the multiple keys? So browsing senders with CMD-bn instead of the old CMD-n? What I find really confusing is that the shortcut keys in the menu are uppercase but the shortcut is lowercase. This does not look like an improvement to me. Any hints are highly appreciated. Norbert

July 7, 2018

Re: [Pharo-users] Pharo stable version with git support

by Dimitris Chloupis

I have used Pharo with Git, for versioning source code and variable assets , images and audio files using filetree and the git client of my choosing. Git is super flexible , especially if you combine it with make files that I also use to build my own custom pharo images together with pharo startup scripts (the operate on the startup of a pharo image to check for dependencies and incompatibilities with the image and then compensate for any such problem). Iceberg is great to make things easier and keep everything organized from inside the image but I cannot stress enough that Iceberg SHOULD NOT be used to avoid learning Git because in the end Git is extremely powerful , although sometimes not that elegant, its not easy to replace the existing super powerful gui clients that exist for it and are used by millions of developers worldwide. If you are on windows I recommend tortoiseGit cause integrates elegantly with windows explorer and is very powerful. For MacOS I recommend GitUp it has its own Undo functionality to quickly recover from accidental mistakes. All the above of course can be used together with Iceberg and there is little reason for them to conflict because in the end , everything has to follow the Git workflow and rules. I have also tested these workflow for Gitlab (an open source alternative to Github and probably the second most popular online repo website after Github) and it works without any issues. The workflows is practically the same. On Sat, Jul 7, 2018 at 11:54 AM dario.trussardi(a)tiscali.it < dario.trussardi(a)tiscali.it> wrote: > > Ciao, > thanks..... > > Hi Dario, > >> i'm interested to port all my code to new Pharo version that >>> manage git support. >>> >>> I found information in pharo.org news, it talk of Pharo 6.1. >>> >>> But it run only on macOS 64bits o i can run it on Linux Ubuntu >>> 16.04 LTS System? >>> >>> New information - update about it? >>> >>> Pharo 6.1 runs on 64bits, except for windows. > > OK, i have setup a Pharo 6.1 image with Iceberg update as >> https://github.com/pharo-vcs/iceberg >> >> Now i'm "new" to git support ...... >> > > Take into account that this is highly necessary. The version of Iceberg in > Pharo 6.1 is just an old preview version. > While Pharo works on 64 bits, Iceberg itself was not at that time, so > upgrading is necessary to have that support. > > > 1) OK, i have do the upgrade to: iceberg:dev-0.7 > > "load iceberg"Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v1.?'; > onWarningLog; > load."Re-initialize libgit2" > (Smalltalk at: #LGitLibrary) initialize. > > But it's the last version ? > > How i can understand what is the right version to update ? > > 2) for error i delete the......shared/pharo-local/iceber/git/iceberg > directory. > > i need to setup a new pharo environment ? > > > >> I understand ??? that Iceberg has some limitations, it is not complete >> ......???? >> > > Iceberg already has pretty good support to manage pharo code. > > You'll find however that it does not manage (yet) non-pharo files. That > is, if your repository has scripts, pictures or such kind of resources, you > will have for now to edit and commit them from the outside (command line or > another tool). > > The reasons for that are so far explained in here > https://github.com/pharo-vcs/iceberg/blob/master/docs/The-Working-Copy(ies)… > > I would be grateful if someone explained to me how operatively I can >> manage everything ... up to where I can do with Iceberg directly from Pharo >> and how to operate from the shell on the git repository. >> >> Documentation in this sense? >> > > Well, you have iceberg's wiki > > https://github.com/pharo-vcs/iceberg/wiki > > We are moving the documentation (hey, bit thanks to Tim Mackinon here!) > to the main repository so people can easy contribute to it. > See https://github.com/pharo-vcs/iceberg/tree/master/docs. > What is left is a sync mechanism between that directory and the wiki > repository. > >> >> My goal is to setup a environment for integrate Pharo development with >> Gemstone GLASS Tode git support..... >> >> Does anyone have experience in this sense? >> > > That's not me, I hope you'll find somebody. But if you have any questions > regarding Iceberg, don't hesitate to ask them! > > > You intend at this support ? > > Thanks, > > Dario > >

July 7, 2018

Re: [Pharo-users] Pharo stable version with git support

by dario.trussardi＠tiscali.it

Ciao, thanks..... > Hi Dario, >> i'm interested to port all my code to new Pharo version that manage git support. >> >> I found information in pharo.org news, it talk of Pharo 6.1. >> >> But it run only on macOS 64bits o i can run it on Linux Ubuntu 16.04 LTS System? >> >> New information - update about it? >> > > Pharo 6.1 runs on 64bits, except for windows. > > OK, i have setup a Pharo 6.1 image with Iceberg update as https://github.com/pharo-vcs/iceberg > > Now i'm "new" to git support ...... > > Take into account that this is highly necessary. The version of Iceberg in Pharo 6.1 is just an old preview version. > While Pharo works on 64 bits, Iceberg itself was not at that time, so upgrading is necessary to have that support. 1) OK, i have do the upgrade to: iceberg:dev-0.7 "load iceberg" Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v1.?'; onWarningLog; load. "Re-initialize libgit2" (Smalltalk at: #LGitLibrary) initialize. But it's the last version ? How i can understand what is the right version to update ? 2) for error i delete the......shared/pharo-local/iceber/git/iceberg directory. i need to setup a new pharo environment ? > > > I understand ??? that Iceberg has some limitations, it is not complete ......???? > > Iceberg already has pretty good support to manage pharo code. > > You'll find however that it does not manage (yet) non-pharo files. That is, if your repository has scripts, pictures or such kind of resources, you will have for now to edit and commit them from the outside (command line or another tool). > > The reasons for that are so far explained in here https://github.com/pharo-vcs/iceberg/blob/master/docs/The-Working-Copy(ies)… > > I would be grateful if someone explained to me how operatively I can manage everything ... > > up to where I can do with Iceberg directly from Pharo and how to operate from the shell on the git repository. > > Documentation in this sense? > > Well, you have iceberg's wiki > > https://github.com/pharo-vcs/iceberg/wiki > > We are moving the documentation (hey, bit thanks to Tim Mackinon here!) to the main repository so people can easy contribute to it. > See https://github.com/pharo-vcs/iceberg/tree/master/docs. > What is left is a sync mechanism between that directory and the wiki repository. > > My goal is to setup a environment for integrate Pharo development with Gemstone GLASS Tode git support..... > > Does anyone have experience in this sense? > > That's not me, I hope you'll find somebody. But if you have any questions regarding Iceberg, don't hesitate to ask them! You intend at this support ? Thanks, Dario

July 7, 2018

Re: [Pharo-users] Pharo stable version with git support

by Guillermo Polito

Hi Dario, > i'm interested to port all my code to new Pharo version that >> manage git support. >> >> I found information in pharo.org news, it talk of Pharo 6.1. >> >> But it run only on macOS 64bits o i can run it on Linux Ubuntu >> 16.04 LTS System? >> >> New information - update about it? >> >> Pharo 6.1 runs on 64bits, except for windows. OK, i have setup a Pharo 6.1 image with Iceberg update as > https://github.com/pharo-vcs/iceberg > > Now i'm "new" to git support ...... > Take into account that this is highly necessary. The version of Iceberg in Pharo 6.1 is just an old preview version. While Pharo works on 64 bits, Iceberg itself was not at that time, so upgrading is necessary to have that support. > I understand ??? that Iceberg has some limitations, it is not complete > ......???? > Iceberg already has pretty good support to manage pharo code. You'll find however that it does not manage (yet) non-pharo files. That is, if your repository has scripts, pictures or such kind of resources, you will have for now to edit and commit them from the outside (command line or another tool). The reasons for that are so far explained in here https://github.com/pharo-vcs/iceberg/blob/master/docs/The-Working-Copy(ies)… I would be grateful if someone explained to me how operatively I can manage > everything ... up to where I can do with Iceberg directly from Pharo and > how to operate from the shell on the git repository. > > Documentation in this sense? > Well, you have iceberg's wiki https://github.com/pharo-vcs/iceberg/wiki We are moving the documentation (hey, bit thanks to Tim Mackinon here!) to the main repository so people can easy contribute to it. See https://github.com/pharo-vcs/iceberg/tree/master/docs. What is left is a sync mechanism between that directory and the wiki repository. > > My goal is to setup a environment for integrate Pharo development with > Gemstone GLASS Tode git support..... > > Does anyone have experience in this sense? > That's not me, I hope you'll find somebody. But if you have any questions regarding Iceberg, don't hesitate to ask them!

July 7, 2018

Re: [Pharo-users] [Moose-dev] Re: Roassal2 in Pharo 6.1 (Win) 137 tests fails

by HernÃ¡n Morales Durand

Hi Peter, I don't know why but restarted the PC and it worked! On a new image and Roassal2 installation. Thank you, Cheers, HernÃ¡n 2018-07-06 12:52 GMT-03:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> May be Roassal2 is broken on Windows? > > Sometimes Pharo on Windows decides that it will not load external library. > > Try to restart your PC and see if it persists. > > Peter > > On Fri, Jul 6, 2018 at 5:38 PM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> >> In a clean Pharo 6.1 (Windows 8) I loaded Roassal2 with the following >> spec in a baseline: >> >> spec >> project: 'Roassal2' >> with: [ >> spec >> className: #ConfigurationOfRoassal2; >> versionString: #stable; >> repository: >> 'http://www.smalltalkhub.com/mc/ObjectProfile/Roassal2' ]. >> >> But many Trachel tests fails because of "External module not found" >> error (Screenshots attached). >> May be Roassal2 is broken on Windows? >> >> I tried loading Roassal2 from the Catalog browser and the same 137 tests >> fails. >> >> Any idea what could be missing? >> >> Cheers, >> >> HernÃ¡n >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev >> > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

July 7, 2018

Re: [Pharo-users] [Moose-dev] Re: Roassal2 in Pharo 6.1 (Win) 137 tests fails

by HernÃ¡n Morales Durand

Hi Alex, I used the VM which is provided by the zeroconf, i.e.: wget -O- https://get.pharo.org | bash This VM is Cog Spur VM 5.0 (release) from May 9 2018. gcc 6.4.0 Could happen that loading a library on Windows sometimes fails? It would be nice to have the path or additional information on the loading error. Cheers, HernÃ¡n 2018-07-06 13:55 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Dear Hernan, > > Likely that you use a VM that does not have the Cairo library. Can you try > updating your VM? > > Cheers > Alexandre > > http://bergel.eu > > Le 6 juil. 2018 Ã 18:38, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> a > Ã©crit : > > In a clean Pharo 6.1 (Windows 8) I loaded Roassal2 with the following > spec in a baseline: > > spec > project: 'Roassal2' > with: [ > spec > className: #ConfigurationOfRoassal2; > versionString: #stable; > repository: > 'http://www.smalltalkhub.com/mc/ObjectProfile/Roassal2' ]. > > But many Trachel tests fails because of "External module not found" > error (Screenshots attached). > May be Roassal2 is broken on Windows? > > I tried loading Roassal2 from the Catalog browser and the same 137 tests > fails. > > Any idea what could be missing? > > Cheers, > > HernÃ¡n > > <Test Runner.png> > > <Error - External module not found.png> > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

July 7, 2018