- Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo 2 and old shortcuts

by Marcus Denker

On Feb 19, 2013, at 1:09 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > This setting "use Historical keys" is to set if you want cmd+arrows to switch between windows or opt+tab > We should think about cleaning this up in 3.0â¦ > Ben > > On Feb 19, 2013, at 12:44 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) >> is "Use old style keys" under Nautilus group >> >> Esteban >> >> On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> which most places? >>> >>> e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. >>> >>> Norbert >>> >>>> the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. >>>> >>>> Esteban >>>> >>>> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>>> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >>>>> Is there a way change that? >>>>> >>> >>> >>> >> >> >

Feb. 19, 2013

Aero snap for Pharo: where to start?

by phil＠highoctane.be

Hello, I'd like to have a feature in Pharo, namely the Aero Snap behavior like in Windows 7. Where should I start to have that? Maybe TWM has it already. If not, where should I start in it to make that work? TIA Phil

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Benjamin

This setting "use Historical keys" is to set if you want cmd+arrows to switch between windows or opt+tab Ben On Feb 19, 2013, at 12:44 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) > is "Use old style keys" under Nautilus group > > Esteban > > On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> which most places? >> >> e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. >> >> Norbert >> >>> the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. >>> >>> Esteban >>> >>> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >>>> Is there a way change that? >>>> >> >> >> > >

Feb. 19, 2013

Slices and monticello - add to package... or add package to ... ? + procedure

by phil＠highoctane.be

I was educating myself on slices. Maybe I'll be able to contribute a bit properly one of these days. Reading from http://code.google.com/p/pharo/wiki/HowToContribute. Creating a slice in my own package-cache is all fine. Now, to add it to the PharoInbox, I watched the screencast: http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html There is this thing were we need to go to the PharoInbox repo in the right pane on monticello. The right click and select the Add to package.. option and then select the slice. All right, I can understand but this feels like unnatural to be on a repository and ask to "Add to package..." where what I want to do is to add the package to the repository. I understand that this is required to have the repository associated with the package so that I can save the package to one of its associated repositories. Maybe "Associate with package..." may be more helpful. Also the procedure on HowToContribute is not right anymore. As the UI changed. There is my version: # How to make a slice Slice: Your modification affect more than one package: you have to create a SLICE package in your package cache A SLICE is just a package with dependents ones, so you have to indicate the dependent packages. ## Procedure Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name). Select your package-cache repository on the right hand pane. Create the new SLICE (click on the ''+SLICE'' button) and follow the instructions. ### Old way _Mark all_ the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages. (Yeah, boring) ### New way (Pharo 2.0 at least) Put the issue tracker number in the Issue Number box and hit "Grab" to get the title of the issue. The (un)select in the list of "Dirty Packages to be included in the slice" ### Back to regular programming... Select your package-cache repository, this will enable the save button. Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. (Name: something along the lines of SLICE-Issue-XXXX-YYYY-ZZZZ-Comment-Initials.1) You will be prompted for a log message (for each one of them ?), type a useful comment for the first package, (copy it and paste it on the others - sure?). Make sure to give the number of the issue your SLICE addresses in the comment. Publish the package to PharoInbox repository. # Hwo to publish to the PharoInbox repository Open monticello. Select the PharoInbox repository on the right pane. Right click the repository and select "Add to package..." (this will associate the package to the repository). You'll be presented with a list of possible packages. Pick up your slice. Then, go back to Monticello Browser with a list of packages on the left and a list of repositories on the right. Select on your slice on the left. Select the PharoInbox repository on the right. Click the Save button on the top bar. That's it, slice now in PharoInbox. Phil

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) is "Use old style keys" under Nautilus group Esteban On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> which most places? > > e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. > > Norbert > >> the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. >> >> Esteban >> >> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >>> Is there a way change that? >>> > > >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Norbert Hartl

Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > which most places? e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. Norbert > the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. > > Esteban > > On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >> Is there a way change that? >>

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

which most places? the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. Esteban On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. > Is there a way change that? > > Norbert

Feb. 19, 2013

Pharo 2 and old shortcuts

by Norbert Hartl

For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. Is there a way change that? Norbert

Feb. 19, 2013

Pharo By Example 2 Book - Assembled Files in PDF form.

by phil＠highoctane.be

Hi all, I struggled with the fact that the PBE2 book was in tex format and not all chapters were together in a single PDF. So, I ran the scripts in order to get a version with all the parts put together. This should be made into a Jenkins job I think so that we can have the PBE2 and other books in PDF form for easier dissemination. Here is the current assembly: https://www.dropbox.com/s/t8pesgxsovy61k5/PBE2-Assembled-20130213.pdf 412 pages of Pharo explanations. How lovely! Enjoy, Phil

Feb. 19, 2013

Re: [Pharo-users] Spec - openWithSpecLayout: vs. openWithSpec:

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > Maybe a refactor here is needed (the first one should maybe use the second > one) Okay, I opened an issue for 3.0 - Issue 7537: [Cleanup]: openWithSpecLayout: vs. openWithSpec: -- View this message in context: http://forum.world.st/Spec-openWithSpecLayout-vs-openWithSpec-tp4670560p467… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 19, 2013