Closed atsushieno closed 1 year ago
Building Web UI for JUCE plugin https://github.com/atsushieno/aap-juce/issues/22 is another issue that is more like an enhancement: it may be useful, but those desktop GUI is basically useless on mobiles and only visually attracting. It can be useful bait but Activity embedding would be enough for that purpose.
WIP
Looks like native UI does not show up on aap-lv2 plugins, and probably aap-juce plugins. Or in other words, only aapinstrumentpluginsample works so far.
aap-lv2 plugins and aap-juce plugins successfully provide Web UI and they show up. They seem to be stuck at aap::NonRealtimeLoopRunner
, namely handleMessage()
is not kicked.
superceded by #158.
Now that dc32932 brought in the basic implementation for GUI support from plugin Web UI down to remote plugin instance, we are in general "done" with the designing phase (#34) and switch to the implementation phase.
Here is the list of what we have done and what we need to do:
AudioProcessorEditor::createEditor
implementationMany of those compose UI issues could rather be achieved by redesigning everything that depends on androidaudioplugin-samples-host-engine... (the features it offers are awkward right now).