Comment 6 for bug 319121

I understand now why this behavior exists, but I'm wondering if there couldn't be some way to auto-detect whether the plugins would work. For example, there have been a series of updates lately. The first one did appear to be major, but the other ones seemed to be smaller. In fact, the list of available plugins was identical between updates--at least for the plugins I care about. So the fact that I could simply re-enable them suggests that whatever API changes were made didn't affect those particular plugins.

I don't know C#, but something like the following wouldn't be too hard in Ruby or Python. Maybe C# is capable of something like this:

1. On the first run after the version number changes, Do introspects each plugin to discover whether the API calls it makes are still valid (this assumes that incompatible API changes result in changes to the API method names).
2. If the inspection passes, do nothing.
3. If it fails, disable the failing plugin(s) and pop up a dialog explaining that plugins x, y, and z are incompatible with the current version of Do and have thus been disabled.

I think that such an approach would be better from a usability perspective while still addressing API changes.