[Pharo-project] Showing the setUp method in Nautilus

Stéphane Ducasse stephane.ducasse at inria.fr
Mon Mar 5 15:32:15 EST 2012


May remove the read from squeak source :)

Stef

On Mar 5, 2012, at 6:28 PM, Mariano Martinez Peck wrote:

> 
> 
> On Mon, Mar 5, 2012 at 6:20 PM, Benjamin <benjamin.vanryseghem.pharo at gmail.com> wrote:
> You are using a really old version of Nautilus.
> 
> You load the configuration from the old repo. Now everything is on Gemstone.
> 
> Ben, can you update not only the "Wiki" in ss but also the "Overview"  (first tab)  ?
> 
> :)
> 
>  
> 
> I still can't understand why you do not use a plugin for that.
> Or an external class.
> 
> Since menu items and shortcuts are pragma based, you can define them anywhere in the system. And you can also retrieve data from the NautilusUI instance.
> 
> Ben
> 
> On Mar 5, 2012, at 6:09 PM, Alexandre Bergel wrote:
> 
> > Voila, I produced version 4.1
> > 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.
> >
> > 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?
> >
> > 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
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com
> 





More information about the Pharo-dev mailing list