On 11/1/07, Don Dwiggins <[EMAIL PROTECTED]> wrote: > This would be a good idea in general: give the user a list of plugins, > and a way to control their loading: on startup, on first use, or never > (this could be useful to keep the plugin in the list for occasional use, > but avoid having it loaded inadvertently).
Good idea. > Come to think of it, the > list should probably be a tree to show dependencies among plugins. You'd actually have to use a dependency graph, because a plugin could depend on more than one plugin. (I suppose if you really wanted to use a tree you could show the same plugin in multiple places in a tree, but that might get confusing.) It might be easier just to have a sortable list of plugins and show the dependencies in the information panel. Eclipse probably does something like this, since it's entirely plugin based. I'll have to get more memory and try it out. :) Anyone have any other examples of this sort of hierarchical dependency-based plugin management? Rob
