Larry Becker wrote: > > Michaël still needs an easier method of associating menu items with > plug-ins. Perhaps just additional convenience methods in > FeatureInstaller? The OJ committee will have to decide this. > Yes, it seems like some well-designed convenience methods might give Michael his ease of configuration, but satisfy my affinity to pure Java 8^) I do agree that the JUMPConfiguration class is pretty bloated with a lot of stuff that is mostly boilerplate code. > I still want a better way to install add-on plug-ins, preferably > workbench-properties.xml. However, I don't intend to replace the > Extension concept, only create an alternative. > Absolutely, I understand your problem. It would definitely be nice to make it easy to add in plugins.
Could you possibly partition your plugins into several JARs? Originally it seemed to us that using the JAR as the "unit of extensibilty" was a nice, simple concept. And as Michael just pointed out, workbench-properties.xml was designed to do this as well. What it *doesnt'* do is control where the plugins install themselves in the menu structure - it was left to the plugin to do this (on the theory that the plugin designer is the one who best knows where they should go, and to prevent the confusion of everyone designing their own menu arrangement). If it's onerous to specify every single plugin in the workbench-properties, this could be extended to recognize Extension classes as well and load them entirely. -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
