[Pharo-dev] 13102

Tudor Girba tudor at tudorgirba.com
Mon Apr 14 09:15:29 EDT 2014


Sorry for not replying before but I was offline. This issue is not to fix
Keymapping at this point. The current solution was designed with intent to
work in the current way. We can certainly discuss about fixing it, but the
solution is not for Pharo 3.

The current discussion is about disabling the global shortcuts for opening
the Workspace and other tools. In the Moose image, we disable those
shortcuts because with the current implementation of Keymapping having
complicated global keybindings simply leads to problems (for example, we
cannot use Cmd+o for anything). Do not get me wrong: Keymapping is an
excellent contribution that simplified a lot an important area. My
suggestion is to remove the global mappings for Pharo 3.0, and then
continue to work on getting Keymappings to an even better state.


On Mon, Apr 14, 2014 at 2:49 PM, GOUBIER Thierry <thierry.goubier at cea.fr>wrote:

> Hi Esteban, Marcus,
> in that particular case, I would propose the following simple fix which
> could solve the first impression.
> - Document global shortcuts, ensure that they are single key.
>   - Document an overload (or not) effect when your app redefines a global
> shortcut.
> - Change a bit Keymapping so that single key shortcuts match first.
> This would solve the immediate problem and let us time to consider a more
> complex solution for Pharo 4.
> Thierry
> ________________________________________
> De : Pharo-dev [pharo-dev-bounces at lists.pharo.org] de la part de Esteban
> Lorenzano [estebanlm at gmail.com]
> Envoyé : lundi 14 avril 2014 14:39
> À : Pharo Development List
> Objet : Re: [Pharo-dev] 13102
> On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker at inria.fr> wrote:
> >
> > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan at stack.nl> wrote:
> >
> >> Hi Marcus,
> >>
> >> I think 13102 is a showstopper. Can’t explain this to new users.
> >>
> sorry, but I have to disagree… this is an important problem, I agree.
> But fix that will need (AFAIK) a lot of work and probably a revamp of the
> keybindings in system.
> Also… this problem was (again, AFAIK) present since pharo2 and we have
> been able to continue working even with that annoyance.
> We will always have problems to fix. And we still have many *really
> important* problem to fix. But if we do not release even with some bugs, we
> will never release.
> "Show stopper” IMO, is a bug that prevents the system to continue working.
> Explain to students an annoyance in the system is bad, but not show stopper.
> so… I’m with Marcus. We can delay this fix. But I also believe this kind
> of problems are a “shoot in the foot”, not good for attract newcomers.
> That’s why we are suggesting that Pharo4 should centred on the tooling: we
> have the feeling that out tools are one (or several) step(s) behind the
> power that pharo has.
> Esteban
> >
> > The question is do we hold up the release for it?
> > That is: is not releasing better than releasing with this?
> >
> > How long do we stop releasing, considering that we will not find
> > anyone to fix it?
> >
> >       Marcus
> >
> >


"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140414/0eca3a63/attachment-0002.html>

More information about the Pharo-dev mailing list