Plugin Version property

[GoogleCodeExporter]

Proposal:

Plugins should have an independent version property. This should be in a format 
that allows versions to be compared. I would suggest that using the four 
integer parts would be idea Major.Minor.Revision.Build where the last two are 
optional and assumed to be 0 for comparison purposes. Whilst few plugin 
developers would use fourth optional part (build) some may wish to have that 
added granularity. Personally I would certainly use major,  minor and revision.

Initially this should be listed in a new column in the plugin's list between 
name and description.

Benefit:

At first this would simply provide a cleaner way for plugin developers to list 
their plugin versions in LCDHost. 

Medium term it would allow layouts to save the version of the plugin used to 
create them and LCDHost to warn if a layout is loaded in a client with a plugin 
that is either missing or out of date.

Long term LCDHost could automatically check plugin versions daily or weekly and 
inform users if an update is available.

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

[GoogleCodeExporter]

Original comment by linkdata...@gmail.com on 20 Jan 2011 at 2:39

• Changed state: Accepted

[GoogleCodeExporter]

Absolutely. This needs to be one of the basic exports of a plugin. However, for 
flexibility I think two values. One string for developer use that is simply 
shown as-is, and one integer (build number or whatever) which monotonically 
increases and can be used for automated version checking.

Original comment by linkdata...@gmail.com on 22 Jan 2011 at 3:43

[GoogleCodeExporter]

Implemented at the lowest layers, but not yet shown or used.

Original comment by linkdata...@gmail.com on 25 Jan 2011 at 1:51

• Changed state: Started

[GoogleCodeExporter]

This appears to be displayed nicely now in the plugins tab.

Closed-Fixed.

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

• Changed state: Fixed