On Tue, Jun 15, 2010 at 3:59 PM, Gabriel M. Beddingfield <gabrbedd@gmail.com> wrote:


On Tue, 15 Jun 2010, Jeremy wrote:

I.e. the plugin provides both an internal and external UI, and the host
application picks which one.  You can already do that.

I was under the impression that external UIs use some form of IPC to
communicate, while internal UIs use callbacks to the host.

Yes.

Otherwise, every host has to have a Qt-external-window setup, an FLTK-external-window setup, a GTK-external-window
setup, etc.  Kind of defeats the purpose of having the external UI, doesn't it?

-gabriel


wait, isn't the

LV2UI_Descriptor->port_event() and LV2UI_Write_Function() interface toolkit agnostic?

Wouldn't it be possible to have toolkit agnostic host-facilitated communication?
Jeremy