Subject: Re: [linux-audio-dev] saving plugin settings
From: Paul Winkler (slinkp23_AT_yahoo.com)
Date: Sun Sep 16 2001 - 02:30:40 EEST
On Sat, Sep 15, 2001 at 10:06:43AM -0400, Taybin Rutkin wrote:
> <?xml version="1.0"?>
> <Ladspa>
> <port port-number="4" value="1.00000"></port>
> <port port-number="5" value="0.71929"></port>
> <port port-number="6" value="0.24469"></port>
> <port port-number="7" value="0.61662"></port>
> <port port-number="8" value="0.14312"></port>
> <port port-number="9" value="0.29824"></port>
> </Ladspa>
Looks fine, but why "port-number"? Since this is an attribute of the
port tag, there's nothing ambiguous about what it's a number of ... is
there? e.g.
<?xml version="1.0"?>
<Ladspa>
<port number="4" value="1.00000"></port>
<port number="5" value="0.71929"></port>
<port number="6" value="0.24469"></port>
<port number="7" value="0.61662"></port>
<port number="8" value="0.14312"></port>
<port number="9" value="0.29824"></port>
</Ladspa>
It would be cool (i.e. the XML would be more human-readable) if we
could do something like
<port name="Frequency (Hz)" value="0.001404"/>
... but I don't think we can guarantee that will work, as there's
nothing AFAIK that guarantees the PortNames will be unique or even
non-empty.
One more tip that makes it more compact without (IMHO) hurting human
readability - I know in XHTML you can do this, therefore I think it's
valid XML as well:
<?xml version="1.0"?>
<Ladspa>
<port number="4" value="1.00000" />
<port number="5" value="0.71929" />
<port number="6" value="0.24469" />
<port number="7" value="0.61662" />
<port number="8" value="0.14312" />
<port number="9" value="0.29824" />
</Ladspa>
-- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com
This archive was generated by hypermail 2b28 : Sun Sep 16 2001 - 02:30:04 EEST