Looks good,
I have one thought... One of the good things about moving to LV2
will be the possibility of extensions, possibly requiring new whizzy
data types / classes on the ports.
If this is the case is it a good idea to be tied down to the "enum
SLV2DataType" which means the library has to know and support the data
type (ie. be able to map "float" to SLV2_DATA_TYPE_FLOAT), and that
new data types can only be added by changing the library. If the data
type was presented just a char * to the string as given in the .ttl
file, then the plugin authors would be free to work with new data
types without having to get the core library changed. (This possibly
holds for the enum SLV2PortClass too, although that's arguably less
likely to need to change (?) )
I hope I've explained myself clearly enough! :)
Any sense in this?
On 5/26/06, Dave Robillard <drobilla@email-addr-hidden> wrote:
> On Fri, 2006-05-26 at 14:18 +0200, Lars Luthman wrote:
> > On Thu, 2006-05-25 at 23:09 -0400, Dave Robillard wrote:
> > > Hi all,
> > >
> > > I've been working on a host library for LV2 plugins.
> >
> > What's the license? GPL?
>
> Yes.
>
> -DR-
>
>
Received on Tue May 30 16:15:07 2006
This archive was generated by hypermail 2.1.8 : Tue May 30 2006 - 16:15:07 EEST