[Pharo-project] Showing the setUp method in Nautilus
alexandre.bergel at me.com
Mon Mar 5 12:09:30 EST 2012
Voila, I produced version 4.1
I did not use a plugin since the commands are directly implemented on NautilusUI, I therefore guess that a plugin is not the way to define commands.
Also, something that I would find very useful, is to open a new Nautilus directly on the Group tab. I often see myself switching to the Group tab. Am I the only one?
On 5 Mar 2012, at 13:40, Benjamin wrote:
> On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote:
>> I worked on a new method item action to easily show the setUp method of a testCase. This helps reduce the amount of clicks and context switching when one wants to know what the setUp method is about while writing a test method.
>> I think it is a good candidate for being included in Nautilus.
>> Ben, if you agree with this, I can to commit in the Nautilus rep and produce a new version of the configuration. How does that sound?
> Commit, and I will have a look ;)
> I though you started also a NautilusPlugin related to that, am I wrong ?
>> Question: how to associate a shortcut to an action?
> Anywhere on class side something like:
> buildRefactoringMethodShortcutsOn: aBuilder
> (aBuilder shortcut: #rename)
> category: #NautilusMethodShortcuts
> default: $r command
> do: [:target || scroll |
> scroll := target methodWidget vScrollValue.
> target refactor renameMethodFor: target selectedMethod.
> target methodWidget vScrollValue: scroll]
> The categories are:
> and here target is the NautilusUi instance which get the keyStroke.
>> Side comment: it would be a good move to adopt a class hierarchy a la OB to define commands. Defining all the commands in NautilusUI does not scale and simply does not work for non trivial command.
> For me, it generates to much classes. And now that Guillermo did a great work for KeyMappings, I prefer to use it :)
>> Alexandre Bergel http://www.bergel.eu
Alexandre Bergel http://www.bergel.eu
More information about the Pharo-dev