[LAD] Portable user interfaces for LV2 plugins

Pedro Alves alves.ped at gmail.com
Fri Mar 4 21:45:19 UTC 2011

On Friday 04 March 2011 19:38:28, David Robillard wrote:
> The plugin UI provides whatever widget it is natively implemented in.
> The host requests whatever widget type it is natively implemented in.

Why widget type/toolkit at all?  If you want to abstract, 
why not abstract at a lower level?  Make the plugin claim 
its written for a GL context or X or Win32 or Cocoa (or
whatever is used on MacOS), and return the relevant context
id.  Make the host do the same thing.  Make the library mix and
match at that level (or libraries: it's not like a host
is changing between X and Win32 at runtime), and gain
toolkit independence.

Pedro Alves

More information about the Linux-audio-dev mailing list