On Sat, Apr 22, 2006 at 02:47:33PM -0400, Dave Robillard wrote: > > You could do pluginUri#portShortName, it's a fairly common convention (eg. > > in HTML). But youre only allowed a small set of characters after the #. > > > > > I think the regexp you mentioned there is fine, though I think we should > > > add one separator character other than underscore for various reasons. > > > ":" maybe? > > > > I'd rather not, I'm not sure its legal in Pd (they get bitten by the port > > name thing too), and its not in C. Pure selfinterest, but My LADSPA code > > is about 50% generated from XML, and I use short names internally for C > > symbols. > > Well, at least one kind of separator character is required (for big > plugins). If it can't be ":", then I don't know what, but there needs > to be something. Maybe "."? If you want to keep it as a valid C > identifier I guess we're pretty much screwed, aside from defining __ to > be interpreted as a sort of heirarchialish separator.
I'm missing the need for heirachicalness. : is probably not safe in OSC either. > I'm fully in support of putting any and all metadata outside the C file, > but the unique identifier isn't metadata, it should be in the code. A > trivial OSC controlled plugin host (which would make a good bundled > example client for the SDK) would need it. It's only /a/ unique identifier. We can't loose the index number as thats the efficent way you access the LADSPA_Data pointers. Only one can be canonical. - Steve