Ok I understand now what you were refering to :) I don't have the same
strong feeling than the author. In this particular case, there is little
chance a controller would be expanded beyond key and value.
Since you are working on instruments.xml, I wonder what's happening with
this issue: http://musescore.org/en/node/19693
If we decide to change the format of instruments.xml to handle this more
complex UI, I don't see the need of a DTD/XSD right now. Did you hear from
MarkRS?
Last point, creating a first draft of the XSD could be automated with
http://www.freeformatter.com/xsd-generator.html
Lasconic
2013/5/1 ChurchOrganist <[email protected]>
> Sure - here
>
> http://www.w3schools.com/dtd/dtd_el_vs_attr.asp
>
>
>
>
> -----
> Regards
> Michael
> --
> View this message in context:
> http://dev-list.musescore.org/Instruments-xml-DTD-tp7578054p7578060.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
