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

need to simplify/unify/document connection establishment #79

Closed
atsushieno opened this issue Apr 20, 2021 · 3 comments
Closed

need to simplify/unify/document connection establishment #79

atsushieno opened this issue Apr 20, 2021 · 3 comments

Comments

@atsushieno
Copy link
Owner

I'm in the process of writing native-oriented client app now, and it is getting complicated to find out the right way to establish connection to service, namely how to set up shared memory buffers in the right order. Since it's been changing, it was definitely left undocumented which is not good at all. It has to be changed.

@atsushieno
Copy link
Owner Author

Expected outcome:

  • How-to documentation on query plugin services, bind service, instantiate plugin, prepare buffers, activate, process, deactivate, terminate, and unbind service. Some native parts are already summarized on README.
  • documenting them means we will have the relevant API parts sorted out.

atsushieno added a commit to atsushieno/aap-midi-device-service that referenced this issue Apr 20, 2021
There was a lot of cumbersome androidaudioplugin API that needs to be
addressed and cleaned up... logged as atsushieno/aap-core#79
@atsushieno
Copy link
Owner Author

Worked on some API simplification, namely, removal of SharedMemoryExtension from public native API surface, is done in r0.6.22.

@atsushieno
Copy link
Owner Author

I'm done with aap-juce adoption too (both plugin and hosting). Now that it is only about the public plugin API matter (libandroidaudioplugin is not public), I can close this particular issue.

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