Pharo 2 and old shortcuts
Locked
12
12
 
|
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 |
|
|
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 <[hidden email]> 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 |
|
|
Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: > 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 <[hidden email]> 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? >> |
|
|
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 <[hidden email]> wrote: > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: > >> 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 <[hidden email]> 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? >>> > > > |
Re: Pharo 2 and old shortcuts
|
|
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 <[hidden email]> wrote: ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) |
Re: Pharo 2 and old shortcuts
|
|
On Feb 19, 2013, at 1:09 PM, Benjamin <[hidden email]> wrote:
We should think about cleaning this up in 3.0…
|
|
|
In reply to this post by EstebanLM
Thanks Esteban!
Norbert Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: > 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 <[hidden email]> wrote: > >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: >> >>> 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 <[hidden email]> 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? >>>> >> >> >> > > |
|
|
In reply to this post by EstebanLM
That was short time fun. If I select the "old style" option and try to find a class using cmd-f I get the following error
 Maybe I stay in 1.4 a while longer… Norbert Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) |
|
|
I cannot reproduce it... did you tried in a new nautilus instance?
please, do not stay in 1.4... we need the feedback of people using 2.0 to improve, otherwise we will not realize what is wrong :) Esteban On Feb 19, 2013, at 2:12 PM, Norbert Hartl <[hidden email]> wrote:
|
|
|
Am 19.02.2013 um 14:19 schrieb Esteban Lorenzano <[hidden email]>: I downloaded latest 2.0 image. I opened it, opened the Settings browser, searched for "old style", checked option. Closed Settings browser, opened over world menu a system browser, click in the left-most pane (classes), pressed cmd-f, typed RxMatcher, selected appearing RxMatcher in list and pressed enter. Norbert
|
|
|
he, I have it... providing a fix now...
On Feb 19, 2013, at 2:25 PM, Norbert Hartl <[hidden email]> wrote:
|
|
|
thanks!
N.
Am 19.02.2013 um 14:38 schrieb Esteban Lorenzano <[hidden email]>:
|
|
|
slice is in inbox, I will integrate in half an hour
http://code.google.com/p/pharo/issues/detail?id=7542
On Feb 19, 2013, at 2:45 PM, Norbert Hartl <[hidden email]> wrote:
|
|
|
In reply to this post by EstebanLM
There is a potential problem for me with 2.0:
It includes NativeBoost/Athens.... As I am targeting iOS running on a StackVM, am I stuck to 1.4? Is there anything to do to ensure that Pharo 2.0 is not a dead end for such developments? Maybe this is just me scaring myself... There is value in an all software Pharo stack. Which is why I went that way in the first place. Phil 2013/2/19 Esteban Lorenzano <[hidden email]>: > I cannot reproduce it... did you tried in a new nautilus instance? > > please, do not stay in 1.4... we need the feedback of people using 2.0 to > improve, otherwise we will not realize what is wrong :) > > Esteban > > On Feb 19, 2013, at 2:12 PM, Norbert Hartl <[hidden email]> wrote: > > That was short time fun. If I select the "old style" option and try to find > a class using cmd-f I get the following error > > <Bildschirmfoto 2013-02-19 um 14.10.24.png> > > Maybe I stay in 1.4 a while longer… > > Norbert > > Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: > > 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 <[hidden email]> wrote: > > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: > > 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 <[hidden email]> 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? > > > > > > > > |
|
|
you are just scared :)
1) NB does not need to be used in 2.0... is just there, as any other package... it just will not work in iOS, but the image will be ok 2) Athens will replace old graphics infrastructure, but not in 2.0 and certainly, that should not be a problem for use it in iOS in the future (since athens is a framework that uses cairo, but can use other backends, like the old balllon3d) Esteban On Feb 19, 2013, at 2:55 PM, "[hidden email]" <[hidden email]> wrote: > There is a potential problem for me with 2.0: > > It includes NativeBoost/Athens.... > > As I am targeting iOS running on a StackVM, am I stuck to 1.4? > Is there anything to do to ensure that Pharo 2.0 is not a dead end for > such developments? > > Maybe this is just me scaring myself... There is value in an all > software Pharo stack. Which is why I went that way in the first place. > > Phil > > 2013/2/19 Esteban Lorenzano <[hidden email]>: >> I cannot reproduce it... did you tried in a new nautilus instance? >> >> please, do not stay in 1.4... we need the feedback of people using 2.0 to >> improve, otherwise we will not realize what is wrong :) >> >> Esteban >> >> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <[hidden email]> wrote: >> >> That was short time fun. If I select the "old style" option and try to find >> a class using cmd-f I get the following error >> >> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >> >> Maybe I stay in 1.4 a while longer… >> >> Norbert >> >> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: >> >> 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 <[hidden email]> wrote: >> >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: >> >> 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 <[hidden email]> 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? >> >> >> >> >> >> >> >> > |
|
|
In reply to this post by philippeback
It might be a good idea to open a new thread if you have a new topic to discuss.
thanks, Norbert Am 19.02.2013 um 14:55 schrieb [hidden email]: > There is a potential problem for me with 2.0: > > It includes NativeBoost/Athens.... > > As I am targeting iOS running on a StackVM, am I stuck to 1.4? > Is there anything to do to ensure that Pharo 2.0 is not a dead end for > such developments? > > Maybe this is just me scaring myself... There is value in an all > software Pharo stack. Which is why I went that way in the first place. > > Phil > > 2013/2/19 Esteban Lorenzano <[hidden email]>: >> I cannot reproduce it... did you tried in a new nautilus instance? >> >> please, do not stay in 1.4... we need the feedback of people using 2.0 to >> improve, otherwise we will not realize what is wrong :) >> >> Esteban >> >> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <[hidden email]> wrote: >> >> That was short time fun. If I select the "old style" option and try to find >> a class using cmd-f I get the following error >> >> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >> >> Maybe I stay in 1.4 a while longer… >> >> Norbert >> >> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: >> >> 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 <[hidden email]> wrote: >> >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: >> >> 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 <[hidden email]> 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? >> >> >> >> >> >> >> >> > |
|
|
In reply to this post by EstebanLM
Question: should I do a Load or a Merge of such slices in Monticello?
TIA Phil 2013/2/19 Esteban Lorenzano <[hidden email]>: > slice is in inbox, I will integrate in half an hour > > http://code.google.com/p/pharo/issues/detail?id=7542 > > On Feb 19, 2013, at 2:45 PM, Norbert Hartl <[hidden email]> wrote: > > thanks! > > N. > Am 19.02.2013 um 14:38 schrieb Esteban Lorenzano <[hidden email]>: > > he, I have it... providing a fix now... > > On Feb 19, 2013, at 2:25 PM, Norbert Hartl <[hidden email]> wrote: > > > Am 19.02.2013 um 14:19 schrieb Esteban Lorenzano <[hidden email]>: > > I cannot reproduce it... did you tried in a new nautilus instance? > > I downloaded latest 2.0 image. I opened it, opened the Settings browser, > searched for "old style", checked option. Closed Settings browser, opened > over world menu a system browser, click in the left-most pane (classes), > pressed cmd-f, typed RxMatcher, selected appearing RxMatcher in list and > pressed enter. > > Norbert > > please, do not stay in 1.4... we need the feedback of people using 2.0 to > improve, otherwise we will not realize what is wrong :) > > Esteban > > On Feb 19, 2013, at 2:12 PM, Norbert Hartl <[hidden email]> wrote: > > That was short time fun. If I select the "old style" option and try to find > a class using cmd-f I get the following error > > <Bildschirmfoto 2013-02-19 um 14.10.24.png> > > Maybe I stay in 1.4 a while longer… > > Norbert > > Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: > > 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 <[hidden email]> wrote: > > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: > > 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 <[hidden email]> 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? > > > > > > > > > > > > |
|
|
slices need to be merged, always
and just the latest one, not all Esteban On Feb 19, 2013, at 3:11 PM, "[hidden email]" <[hidden email]> wrote: > Question: should I do a Load or a Merge of such slices in Monticello? > > TIA > Phil > > 2013/2/19 Esteban Lorenzano <[hidden email]>: >> slice is in inbox, I will integrate in half an hour >> >> http://code.google.com/p/pharo/issues/detail?id=7542 >> >> On Feb 19, 2013, at 2:45 PM, Norbert Hartl <[hidden email]> wrote: >> >> thanks! >> >> N. >> Am 19.02.2013 um 14:38 schrieb Esteban Lorenzano <[hidden email]>: >> >> he, I have it... providing a fix now... >> >> On Feb 19, 2013, at 2:25 PM, Norbert Hartl <[hidden email]> wrote: >> >> >> Am 19.02.2013 um 14:19 schrieb Esteban Lorenzano <[hidden email]>: >> >> I cannot reproduce it... did you tried in a new nautilus instance? >> >> I downloaded latest 2.0 image. I opened it, opened the Settings browser, >> searched for "old style", checked option. Closed Settings browser, opened >> over world menu a system browser, click in the left-most pane (classes), >> pressed cmd-f, typed RxMatcher, selected appearing RxMatcher in list and >> pressed enter. >> >> Norbert >> >> please, do not stay in 1.4... we need the feedback of people using 2.0 to >> improve, otherwise we will not realize what is wrong :) >> >> Esteban >> >> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <[hidden email]> wrote: >> >> That was short time fun. If I select the "old style" option and try to find >> a class using cmd-f I get the following error >> >> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >> >> Maybe I stay in 1.4 a while longer… >> >> Norbert >> >> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <[hidden email]>: >> >> 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 <[hidden email]> wrote: >> >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <[hidden email]>: >> >> 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 <[hidden email]> 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? >> >> >> >> >> >> >> >> >> >> >> >> > |
Re: Pharo 2 and old shortcuts
|
A bit related to this thread... is there an easy way to add a custom shortcut to an already existing context menu action in Nautilus? I'd love to have c-r trigger #format, as it did in 1.4's OB :)
2013/2/19 Esteban Lorenzano <[hidden email]> slices need to be merged, always Bernat Romagosa. |
Re: Pharo 2 and old shortcuts
|
|
You can using key mapping.
But cmd r is already use to rename (temp or the method depending of the selection)
Ben On Feb 26, 2013, at 12:08 PM, Bernat Romagosa <[hidden email]> wrote:
|
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |