Mark plugins incompatible with the current Xcode version

[guillaumealgis]

I intend to add a feature similar to #303 where installed plugins are marked as incompatible (or any other adjective, I'm open to suggestions :) ) when they do not include the right UUID for the currently running Xcode.

We'll also probably need a way to show the user what this means. Maybe adding a line of text to the plugin description like "This plugin is not compatible with your version of Xcode. Last supported version was Xcode 6.0.0.".

It would have been better to mark all incompatibles plugins and not just the installed ones, but given that the DVTPlugInCompatibilityUUIDs info is unavailable without downloading the plugin, I don't have any practical idea of how to do this.

Opening this issue to track progress.

[guillaumealgis]

I'm also considering adding a special action (maybe clicking the button while pressing the alt key?) to "force install" the plugin, by adding the Xcode UUID ourselves to the plist.
That way users would have a practical way to "live on the edge" without having to wait for the plugin maintainer to update the plist with the new UUID.

This would have the same outcome as @ForkPanda's script in #390, with much more fine-grained control.

If you're interested in this feature, please 👍 /👎 this comment so I can know whether this is a good idea, thanks!

[jurre]

It's an interesting idea (force install), I wanna think about it a bit before voting

[ForkPanda]

Greaaaaaaaaaaaaat idea. :)