> >I'm all for making the API more flexible and more powerful, however,
> >I would rather see the toolbar and menu code moved OUT of the base
> >and into plugins rather than moving plugin code back into the base.
> >I think that anything that doesn't require access to the mozilla
> >objects would be best outside of the base, since it allows easier
> >access to developers.
> That's true. There's one thing that makes it less certain for this case,
> and that is that menus and rebars are tied into MFC. This means that
> everything you want to do with them from plugins must be in some way
> supported in the main program as well. Drag and drop configuration for
> rebar would probably not be as easy to get unless there everything
> needed is implemented in the program and then made available through the
> plugin interface.
I must be missing something in your proposal; I don't see how moving
the menuing and rebar control to the plugins would reqire much more
than the existing CreateToolbar function. After that, the plugin has
the ability to add/remove/move buttons inside of that rebar. By
subclassing the main window, Drag and Drop support could also be
handled internally by the plugin without requiring any interaction
with the main app. Am I missing something?
> Either way I think we should keep the menus, toolbars and accelerators
> close together in the gui. Probably a single dialog like the tabbed
> version commonly used in M$ programs.