Auto Update Schema

[KingArgyle]

Okay, version 1.0.1 is now available on the wiki. I included Elements for SkinInstallation and PluginInstallation. These groups share the same element definitions, so if we make changes to one, it'll affect the other. This is only true for the Instllation Information.

Reven, you are correct, a program would need to be written to populate this information. A simple GUI program could be done or a series of web pages, or however the community feels best.

Keep the comments coming. I'll address the avaliable plugins Schema in the coming weeks. This was the big one that needed to get fleshed out.

A couple of areas that still need to be addressed, are plugin/skin categories, and the enumeration values for these. Also, any type of restrictions that need to be included on the fields. The clearer we are now the better off we'll be in the long run.

[KingArgyle]

Somebody may want to try this with the schema we have created for the Auto Update Plugin Detail.

XSDObjectGen:
http://apps.gotdotnet.com/xmltools/xsdobjgen/

Basically, it is an XML Binding tool from Microsoft that will generate either C# or VB.NET code given a schema. It handles all the XML Serialization and Deserialization, so that you don't have to work with the XML DOM directly. Personally, I'm not a big fan of Binding, just because you loose the power of XPath, but this does make it more accessible to a larger group of people that don't want to deal with the XML DOM and XPath.

[KingArgyle]

Just a bump, for final comments. If no further comments, I'll assume that the schema is fine as is, and start work on the available plugins/skins schema.

[jorm]

Has anyone started on the implementation of this yet?

[jrockintuitive]

I have not.

[KingArgyle]

Nope, haven't done anything with it yet. Since I didn't get any further comments on it, I figured the version out there satisfies everybody's needs. To help with implementation and interfacing to the XML files, you might want to run the XSD through the XSDObject program by Microsoft (basically JAXB for .NET).

It can be downloaded here:
http://www.microsoft.com/downloads/detai...layLang=en

[KingArgyle]

Okay, I'm dusting this topic off and bringing it back to life for a bit. I think most people at the time thought this was a good idea, but we didn't have a way to get the XML file for each plugin or skin.

Anyway, I think a real simple way to do it is to use an RSS feed from the wiki. All Skins and Plugin configuration files could have it's own seperate page that contained the Installation / Configuration xml file. It would then be a matter of pulling the appropriate XML file from the page and parsing it.

As for creating the XML file, it can be done one of several ways:

1. Use a text editor.
2. Use an XML Editor that is Schemas away (like XML Spy 2006 Home Edition)
3. Write a program to generate the file.

Anyways, just a thought.

[blader_se]

Anyway, I think a real simple way to do it is to use an RSS feed from the wiki.

This just got me wondering, it is the plugins XML files you would like to subscribe to right? So perhaps an RSS feed with the XML file added as an attachment (like podcasting attaches mp3 files) would be nice? That should be doable from within the wiki engine.

[KingArgyle]

Blader that would work as well. Basically there are a couple of things needed to get the pieces in place:

1. A way to get a listing of all the Skins and Plugins that have an Auto Update XML file.

2. A way to get a listing of files that have had the auto update xml file recently changed since the last check.

3. The link to the XML file itself. That could be done as the attachment.

I think in some ways this would be a good enhancement to go along with the Apperance Manager that Old Dog is writting. Ideally the Appearance Manager would be able to detect when a skin has been updated, know what version it is compatible with and give the user the option to download and install it.

The same could eventually happen with Plugins as well. It would give GBPVR that final piece that imho is missing. A nice user friendly way to enhance the software.

[n@boleo]

I'm with you guy, this is sometimes difficult (remembers something like "pain in the ..." in my english lessons) to maintain all of those plugins uptodate. Some have a changelog (not even update) on the WIKI, other have a separate website or simple no change history...

There is one more thing to consider, a way to show a faq or a manual. I'm thinking about MyMusic plugin witch is not working the same way from v2 to beta builds (populating the DB). Some changes needs to be made by hand and if not plugin will not work any more...