Opened 15 years ago

Closed 15 years ago

#1158 closed enhancement (fixed)

Improving plugin autodetection

Reported by: Jari Häkkinen Owned by: Nicklas Nordborg
Priority: major Milestone: BASE 2.9
Component: web Version: 2.8.3
Keywords: Cc:


The auto detection of plug-ins can be improved. As it is now starting an import plug-in for items (like samples and extracts) there are two matches, the batch importers and the annotations importer (one configuration each). The first dialogue allows the user to auto detect both plug-in and file format. If I select the plug-in but leaves the file format as auto detect, then the parameters are automatically read from a matching configuration. If I select both to be auto-detect another dialogue explains that multiple matches occurs. This is correct, but now if I select a plug-in I am enforced to also select a file format (configuration) even though there is only one available for each plug-in. I am forced to select a plug-in but also to select a file format otherwise no configured parameters are used in the following dialogue.

I suggest that the step where I am forced to select a plug-in should still allow auto-detect for the file format. This obviously works if I select a plug-in already in the first dialogue where I am not forced to select file format.

Change History (2)

comment:1 by Nicklas Nordborg, 15 years ago

Milestone: BASE 2.9
Owner: changed from everyone to Nicklas Nordborg
Status: newassigned

In other words...

  • If there is only one configuration for a plug-in this config should be selected instead of the 'auto-detect' option.
  • The 'none' alternative for plug-ins that can run without configuration should not be visible after an auto-detection

comment:2 by Nicklas Nordborg, 15 years ago

Resolution: fixed
Status: assignedclosed

(In [4621]) Fixes #1158: Improving plugin autodetection

Note: See TracTickets for help on using tickets.