Consider removing JPG plugin in favor of GBM

[Lewis Rosenthal]

I have long used the GBM (Generalised Bitmap Module) plugin, which covers a much wider range of image formats than JPG. As Lucide has issues with "plugin overlap" it is necessary to disable the included JPG plugin in order to make full use of the GBM plugin.

It may be time to just remove the JPG plugin from the distribution entirely and point people to the GBM. Frpm the GBM description:

GBM (Generalised Bitmap Module) is a library for handling many different bitmap file formats. It comes with a set of useful command line tools for doing bitmap manipulations and format conversion. In this version BMP, JPG, JP2, PNG, TIF, PBM, PGM, PPM, PNM, XPM, JBG and RAW support is additionally included.

​http://hobbes.nmsu.edu/h-search.php?key=gbmos2pm160_gbm176_lu143_moz147_bin_wpi

Related: #236

[Gregg Young]

We could probably just disable the JPG plugin if the GMB plugin is installed.

[Lewis Rosenthal]

This would have to be a check at every startup, while loading plugins. That's a more elegant approach, of course. It should mean that ultimately, we provide a mechanism for preferring one plugin over another.

Ideally, we should be able to prefer a given plugin for a specific file type or list of file types over a conflicting plugin, which would obviate the need to disable anything. I thought we had a ticket open for preferring one plugin over another, but I can't find it, now.

[Lewis Rosenthal]

As plugins will become modular, and as installation of the JPEG plugin is already optional (as defined in the existing WIS), I am closing this ticket as WONTFIX. We can always provide a JPEG plugin. Maintaining it now is even easier than before.