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 <estebanlm@gmail.com>:
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 <norbert@hartl.name> 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 <estebanlm@gmail.com>:
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@hartl.name> wrote:
Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm@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@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?