[LV2] LV2 C++ Tools Additions

[Michael Fisher]

On Mon, 2012-10-15 at 18:41 -0400, David Robillard wrote:
> On Mon, 2012-09-24 at 13:59 -0500, Michael Fisher wrote:
> > On Mon, 2012-09-24 at 09:36 -0400, David Robillard wrote:
> [...]
> > > I suppose since all of LV2 is in one tarball now there's no real
> > > potential for name clashes, so you're welcome to it as much as the next
> > > person :)
> > 
> > Thanks.  I decided to go with something a little less official sounding
> > for ya.
> > 
> > D.A.P.S - Digital Audio Plugins Streamlined
> > 
> > https://github.com/mfisher31/daps/
> > 
> > pkg-config names  are  daps-plugin-x.y and daps-gtkui-x.y .  sooner or
> > later an optional support lib will come around.  that will be plain
> > daps-x.y .
> 
> Sounds good, though you should only need one number in the pkg-config
> name to allow for parallel installation.  A minor version doesn't really
> make sense.

Using only major version number now, thanks!  I actually ended up
changing the name (again).  Didn't realize it at the time but apparently
there is already project named daps.
http://daps.sourceforge.net/

So, now I'm calling it  lvtk, which is short for LV2 Toolkit.  I sure
hope that is appropriate, because http://lvtoolkit.org is operational. 

There you can find the standard source downloads, API docs (includes
examples), and a trac site.
> 
> > Fundamentally Complete: 
> >  - Worker - all function pointers connected
> >  - URID - all function pointers connected
> >  - Data Access - all function pointers connected
More has been added.  All (i think) plugin extensions are fundamentally
supported.  UI Rev 3 is supported.

Not supported yet... I have trac tickets for this.
http://lvtoolkit.org/issues/report/1

In a nutshell UI resize, portmap, port subscribe, touch, and peak data
are yet-to-be completed.

If anybody is familiar with lv2-c++-tools' GUI, you'll notice that I
changed the API a bit.  Instead of  inheriting from Gtk::Bin widget, the
new UI class should harbor a 'widget' and implement a  LV2_Widget*
widget() {} method.   A mixin can be used for this or not.  For example.
I have a GktUI mixin that creates the container widget and returns it
through the required widget method.  Then all you have to do is add
other widgets to that.

So, mixins for any other toolkit are possible.



> 


> Great
> 
> >  - Headers present for all data-only exts
> 
> Hm.  Shouldn't you just depend on the lv2 package for this?

Yep.  I should expand a little on that.  Its mainly for completeness.
I've included  *.hpp headers which include the parent lv2 header for
convenience.  I don't actually distribute official lv2 headers.

> 
> -dr
>