On Mar 5, 2012, at 6:09 PM, Alexandre Bergel wrote: > Voila, I produced version 4.1
Version 4.1 already existed :S > Please check. > 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. Why did you add stuff in Nautilus for that ? Why not using an external class ? > > 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? There is a setting for that Ben > > Cheers, > Alexandre > > > On 5 Mar 2012, at 13:40, Benjamin wrote: > >> >> On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote: >> >>> Hi! >>> >>> 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. >> >> Cool >> >>> 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 >> <keymap> >> >> (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: >> #NautilusMethodShortcuts >> #NautilusProtocolShortcuts >> #NautilusClassShortcuts >> #NautilusPackageShortcuts >> >> 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 :) >> >> >> Ben >> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> <ShowSetupInNautilus.1.cs> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >
