On Thu, Apr 20, 2006 at 10:51:20PM +0200, Tim Goetze wrote: > The 0.3.0 CAPS release actually comes with an rdf file supposed to > label the enumerated int ports (the Cabinet model switches and the > SweepVF filter modes).
Argh! I already had 0.3.0, but apparently the gentoo ebuild fails to install the rdf file. I'll file a gentoo bug. I merged yours with mine and yep, it works - now I get both categorization and useful dropdown widgets on those four plugins. Yay! btw, the guy that wrote yours didn't apparently understand how the categories work. I had it mostly right by copying other files, but I just now stumbled on where the taxonomy is actually defined, it's at: /usr/share/ladspa/rdf/ladspa.rdfs ... which apparently comes with liblrdf. > Re: caps.rdf in general -- > > Paul, your permission assumed I'll recycle some of your python code, > to be run when making the CAPS 'dist' target. A better caps.rdf will > thus be in 0.3.1 (coming to a theatre near you sometime this year). Of course. It should be possible to stub out the rdf for enumerated parameters by looking at the "ports:" output of analyseplugin. That might be handy. > Steve, are the dc:creator, dc:rights, dc:title tags necessary? Paul's > caps.rdf simply copies the data found in caps.so -- is it possible to > simply eliminate this redundancy? dc (dublin core) metadata is generally optional. I just put those in without thinking because it was easy to parse out. I like having at least the title, it makes the rdf much more human-readable. -- Paul Winkler http://www.slinkp.com
