Plugin Versions embedded (& checked) in layout files

[GoogleCodeExporter]

Layouts should save information about the plugins they use (i.e. not about all 
plugins loaded on the current LCDHost, but only those whose classes are in use 
by the layout).

The data should include the plugin's name, dll file name, version string and 
build number.

This data should be checked (the build number & dll file name) and compared 
with the available plugins to ensure (a) the required plugins are present and 
(b) their version is equal to or greater than the current version.

Missing a plugin or having one that is out of date will cause an alert to 
appear on screen (message box, or as a hint accross the top of the LCDHost 
window, like Internet Explorer does with its hints).

Optional Extra (for bonus points):

Ideally, plugins would in fact define additional information about 
compatibility so that if v12 is NOT backwardly compatible with layouts made by 
v11, this could be correctly detected. I suspect the plugin would only need one 
additional integer, compatible_from_build, which if absent is assumed to be 
from zero (i.e. backwards compatibility with all previous builds).

Original issue reported on code.google.com by a...@bridgesuk.com on 25 Feb 2011 at 6:18

[GoogleCodeExporter]

Original comment by a...@bridgesuk.com on 25 Feb 2011 at 6:19

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm closing this as Closed-WontFix as the new auto-updating system makes this 
issue redundant.

Original comment by a...@bridgesuk.com on 9 May 2011 at 12:45

• Changed state: WontFix