Yup, this sounds like it could be a good application of that idea.

Question though - at this moment, the code to isntantiate the package is

refactory:= Module named: 'Refactory'.
What would it be if we had custom subclasses? something like "RBModule
current"? or just RBModule? the second sounds like it's enough - don't
think there's any interesting state there, at the moment...

Daniel

Avi Bryant <avi at beta4.com> wrote:
> Not currently.  If you want to try adding it,
> Module>>isYourClassExtension: is what you'd need to modify.  The
> programmatic change should be easy, but letting the UI manage these
> shortcuts, and making sure the shortcut info gets filed out and back in
> with the module will be a little trickier.
> 
> One thing I was discussing with Daniel V. was allowing you to define a
> custom subclass of Module for each Module you wrote; since this would be
> filed out with all of the rest of your code, no separate metadata would be
> needed.