Le 18/11/15 13:56, Esteban Lorenzano a écrit :
On 18 Nov 2015, at 09:50, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
Ok, for that problem we already have a solution provided by the Keymapping engine:
(KMRepository default globalCategories detect: [ :each | each isKindOf: GTSpotterGlobalShortcut ]) allEntries keymaps do: #disable thatâs a workaround, not a solution :) (Iâm ok if thatâs the way to do it in Pharo4⦠I will still add a setting in Pharo5)
And a unload method.
cheers, Esteban
Cheers, Doru
On Nov 18, 2015, at 1:38 PM, Ferlicot D. Cyril <cyril.ferlicot@gmail.com> wrote:
Le 18/11/2015 13:25, Tudor Girba a écrit :
Do you mean that you want to have a different search solution when you press Shift+Enter or when you select it from the World menu?
At the moment, this is not possible.
May I ask where is the problem coming from? Perhaps there are things we can do to solve your problem.
The problem is that I want a desktop application.
With the spotter we can access to the code, so I just want to disable it when we are not in development mode.
We can add a setting to Pharo 5 but in Pharo 4 there is no easy way to disable it.
I think we should also add an easy way to create a deployment image directly inside Pharo.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
-- Cyril Ferlicot (cyril.ferlicot@synectique.eu)
165 Avenue Bretagne Lille 59000 France
-- www.tudorgirba.com
"Reasonable is what we are accustomed with."