On Tue, Apr 15, 2008 at 04:32:49PM +0000, Ted Gould wrote:
On Tue, 2008-04-15 at 15:12 +0200, Marcin Floryan wrote:
I was playing with some extensions recently and started wondering that it would be nice if the extension files (inx) could be made into properly formatted XML documents with their own namespace and an XSD to come with it. This should make creating new ones easier as well as validating them. I should be able to carry out all necessary work but wanted to know if you guys think it is sensible...
YES!!! PLEASE!!!
Perfect - then I'm on it.
Here is as far as I got with the XSD when I was doing it. It has been sitting on my Desktop taunting me... It should give you a little bit of a head start, but feel free to change it.
OK. Thanks - I have already started on a draft XSD but any other clues much appreciated - in particular how to best handle i18n underscores ;-) Perhaps we should enforce (where it makes sense) to use underscores since I suppose we always want GUI text translatable.
I would also love it if someone could set up a "make check" test to verify all the INX files in the build. That way we could be sure that we're not shipping any bad files, but also that we keep the XSD up-to-date.
If pointed in the right direction I should be able to do that as well. I suppose writing a simple script/app should be simple enough. Perhaps just some python.
Regards, -- Marcin Floryan http://marcin.floryan.pl/ [GPG Key ID: 0D5581C5]