Smalltalk › Pharo › Pharo Smalltalk Users

[DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

Torsten Bergmann

[DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager

>How can I de-activate the ctrl-D shortcut for the Desktop manager for
>the time being?

By not using DesktopManager. The shortcut handlers are installed upon load initialize.

Bye
T.

Hannes Hirzel

Re: [DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager

On 9/5/17, Torsten Bergmann <[hidden email]> wrote:
>>How can I de-activate the ctrl-D shortcut for the Desktop manager for
>>the time being?
>
> By not using DesktopManager.

Sure...

What I was asking for: How can I use it _without_ the ctrl-D short
cut. Or how can I replace the ctrl - D shortcut with another short
cut.

>The shortcut handlers are installed upon load
> initialize.

And how can I bypass or adapt this initialize method?

What is the initialization code in case I load the classes manually?

>

best wishes
--Hannes

Ben Coman

Re: [DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager

On Tue, Sep 5, 2017 at 5:41 PM, H. Hirzel <[hidden email]> wrote:

On 9/5/17, Torsten Bergmann <[hidden email]> wrote:
>>How can I de-activate the ctrl-D shortcut for the Desktop manager for
>>the time being?
>
> By not using DesktopManager.

Sure...

What I was asking for: How can I use it _without_ the ctrl-D short
cut. Or how can I replace the ctrl - D shortcut with another short
cut.

>The shortcut handlers are installed upon load
> initialize.

And how can I bypass or adapt this initialize method?

You can find pertinent methods like this...

(RPackageOrganizer default packageNamed: 'Balloon')

definedClasses flatCollect: [ :c |

c class methods select: [:m| m selector = #initialize ] ]

The rough way would be to edit them how you like and save the package locally, then when you load that into a fresh image it runs how you like. More elegant might be setting a flag with startup actions which the #initialize looks for, and contribute that mod back to the original repo.

What is the initialization code in case I load the classes manually?

I'm not sure whether the class-side-initialize methods are run only when Monticello loads a class, or also when loading via changesets or file-in. You could experiment.

cheers -ben

Tim Mackinnon

Re: [DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager

It’s always handy to put a <script> pragma in there anyway, so you can click on the triangle in the browser if you need to re-run it.

Which reminds me - I was going to put it out there, that it might be handy to have something like a <reset> pragma, such that Pharo could have an easy menu to offer ways to reset frameworks it knows about. It’s so frustrating trying to find out how to reset things like Iceberg, Glory, Seaside etc when things go wrong and you just want to go back to the start. I Amy propose this in a new thread to generate some conversation.

Tim

On 8 Sep 2017, at 12:59, Ben Coman <[hidden email]> wrote:

On Tue, Sep 5, 2017 at 5:41 PM, H. Hirzel <[hidden email]> wrote:
On 9/5/17, Torsten Bergmann <[hidden email]> wrote:
>>How can I de-activate the ctrl-D shortcut for the Desktop manager for
>>the time being?
>
> By not using DesktopManager.

Sure...

What I was asking for: How can I use it _without_ the ctrl-D short
cut. Or how can I replace the ctrl - D shortcut with another short
cut.

>The shortcut handlers are installed upon load
> initialize.

And how can I bypass or adapt this initialize method?

You can find pertinent methods like this...
(RPackageOrganizer default packageNamed: 'Balloon')
definedClasses flatCollect: [ :c |
c class methods select: [:m| m selector = #initialize ] ]

The rough way would be to edit them how you like and save the package locally, then when you load that into a fresh image it runs how you like. More elegant might be setting a flag with startup actions which the #initialize looks for, and contribute that mod back to the original repo.

What is the initialization code in case I load the classes manually?

I'm not sure whether the class-side-initialize methods are run only when Monticello loads a class, or also when loading via changesets or file-in. You could experiment.

cheers -ben