2005-06-21, 13:07
well i know what you mean. the simpler form of the changlog:
would save some time but is still extra work for the coder. the benefit is clearly that its much better structured.
best way to go is to make the date and info tag optional imo.
well yes, you should have the latest version, but if the script is very old, will it still work with your copy of xbmc? i think the tag is good.
i finished a first draft version xsd file for the xml which will be used to validate the xml. it places the following restrictions on the xml file:
the tags: name,author,category,description,version,xbmc_revision and execute have to exist and there has to be exactly one of them.
the tag changelog is optional.
category can only be one of a list of predifined ones.
description can have a maximum of 450 characters (just a guess of me should probably be higher)
the revision can have maximum 4 fraction digits (think thats what xbmc uses)
the changelog can either be text or have to as many change tags as wanted in them.
change tags have the tags date and info in them.
date has to be a valid date (yyyy-mm-dd).
version has to be a decimal number.
i'll post the xsd as soon as i have completed and tested it.
please post any comments that you have.
Quote: <changelog>
<change>
<date>1968-03-27</date>
<info>added fancy new logo</info>
<info>updated language file</info>
</change>
<change>
<date>1968-03-27</date>
<info>fixed some bugs</info>
</change>
</changelog>
would save some time but is still extra work for the coder. the benefit is clearly that its much better structured.
best way to go is to make the date and info tag optional imo.
Quote:xbmc revision is a bit pointless since everyone is "assumed" to have latest version anyways
well yes, you should have the latest version, but if the script is very old, will it still work with your copy of xbmc? i think the tag is good.
i finished a first draft version xsd file for the xml which will be used to validate the xml. it places the following restrictions on the xml file:
the tags: name,author,category,description,version,xbmc_revision and execute have to exist and there has to be exactly one of them.
the tag changelog is optional.
category can only be one of a list of predifined ones.
description can have a maximum of 450 characters (just a guess of me should probably be higher)
the revision can have maximum 4 fraction digits (think thats what xbmc uses)
the changelog can either be text or have to as many change tags as wanted in them.
change tags have the tags date and info in them.
date has to be a valid date (yyyy-mm-dd).
version has to be a decimal number.
i'll post the xsd as soon as i have completed and tested it.
please post any comments that you have.