Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
When user selects a plugin in the installpane, show the dependencies and optional dependencies in the description.
Also, have the optional dependencies with checkboxes next to them showing whether they are installed/to be installed or not.
I've been looking into this anyway, so I'll work on this one.
Alan, I was adding this to both the manage and install tabs in plugin manager. For the manage tab, it's not a problem to show all the details for plugins since they are already local. For the install tab, the details come from the downloaded plugin list, which only includes the required plugins, it does not include the optional plugins. I don't know how that list is generated -- how hard would it be to include the optional dependencies?
Hey dale, this would not be a trivial change. The plugin list is not generated from the actual plugin packages, but from the information in the database that is maintained through the Plugin Wiz by the plugin releasers. There only the mandatory dependencies are set up. So to enrich the plugin list by optional dependencies, there would roughly be necessary:
- extend the database scheme to store whether a dependency is mandatory or optional
- extend the Plugin Wiz to be able to specify whether a dependency is mandatory or optional
- go through all versions of all plugins and add the optional dependencies
- When releasing new plugins, also add the optional dependencies through Plugin Wiz
After these changes it should be possible to add the optional dependencies to the plugin list, while it would have to be checked how or whether this can be done in a backwards compatible way so that old jEdit instances still can parse the plugin list, or whether a new plugin list at a new URL would be necessary and Plugin Wiz would have to generate both versions of the plugin list.
Yes, in theory, one must go through all versions of all plugins and add optional dependency info, but in practice, the only plugins that we *need* to add this info to are the latest versions of the plugins that do not reload properly. After that, we can add the info for new plugins and not really worry about the rest.
What do you mean by "that do not reload properly" and what does this have to do with this request, especially with the part that is about showing optional dependencies in the Install pane?
This is "fixed", at least as far it can be done for now:
"When user selects a plugin in the installpane, show the dependencies"
That is all. It's in revision 23056. The rest will take a major rework of the Plugin Central code.
Actuall, there is a little more -- when the user selects a plugin in any of the 3 tabs in Plugin Manager, the dependencies are shown in the details panel.
One small suggestion: have the depends list all on one line instead of having each on a separate line so it takes up less vertical space.