Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: GUI support implementation (take 2.) #158

Open
2 of 5 tasks
atsushieno opened this issue May 20, 2023 · 3 comments
Open
2 of 5 tasks

meta: GUI support implementation (take 2.) #158

atsushieno opened this issue May 20, 2023 · 3 comments

Comments

@atsushieno
Copy link
Owner

atsushieno commented May 20, 2023

It takes over #150, now with Surface Control based GUI (starting a7b2449).

Now we consider these options:

  • native UI based on SurfaceControlViewHost: it requires Android 11 (50%-ish devices in the world as of writing it).
  • Web UI: supports widest range of devices, implementation is a bit tricky.

while killing these options:

  • System Alert Window: works with earlier API versions, but requires special permission on Settings app, kinda tricky and buggy to support as it runs without host's ownership.
  • Activity based UI: switching apps would kill the DAW side. Activity embedding is supported on even narrower range of devices. (We can change our mind at any time; it's just to take instanceId and determine whether it controls existing instance or create new.)

Here is the updated list of tasks we need to work on:

@atsushieno
Copy link
Owner Author

atsushieno commented Jun 10, 2023

Also there are some bugs I observed so far:

  • crashes if I go back to PluginList, revisit PluginDetails, and try to open native UI again.

atsushieno added a commit that referenced this issue Jun 10, 2023
context: issue #158 (not readlly completed doc updates yet) (not readlly completed doc updates yet) (not readlly completed doc updates yet) (not readlly completed doc updates yet)
@atsushieno
Copy link
Owner Author

atsushieno commented Jul 4, 2023

Most of these tasks will be handled post-0.7.7 release as (to my understanding) #153 needs to be resolved (i.e. new default plugin landing app) should take place. Current app is based on static applier that is not suitable to reflect parameter changes.

@atsushieno
Copy link
Owner Author

  • aap-juce-vital crashes when aaphostsample tries to open it (OutOfMemoryError for WTF reason) - since aap-juce-simple-host has no problem with it, it is more likely an issue in androidaudioplugin-ui-compose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant