On 15 janv. 2010, at 23:03, Mariano Martinez Peck wrote:
2010/1/15 Simon Denier
<Simon.Denier@inria.fr>
On 15 janv. 2010, at 21:20, Mariano Martinez Peck wrote:
On Fri, Jan 15, 2010 at 5:55 PM, Romain Robbes
<romain.robbes@gmail.com> wrote:
yes it has overrides ...
that's because as far as I know, there's no keyboard shortcut management facility
in Pharo. If there was one, I suppose Algernon and WorkingSet would coexist.
So...all your overrides are due to the shortcuts? I think it is not fear to "forbid" a package to be included in a Dev image if we don't provide from the core a way to manage shortcuts. So:
1) Or we let this projects to be installed in the Dev image
2) We fix the problem with the shortcuts.
Romain: can you tell us where exactly the problem is ? maybe someone can give you a hand.
Taking a look at that, there are 2 overrides in WorkingSet
How did you detect that ?
Manually, using an extension-aware browser (O2Package, MC browse package, or the package environment) to detect extensions, then check history in the versions browser.
Impressive. You should be a detective :)
A few years ago, I was called the human debugger during a project :) Now I try to restrain from this kind of sessions though, it's time consuming.