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

Add API for out-of-process clients #24

Open
special opened this issue May 26, 2019 · 0 comments
Open

Add API for out-of-process clients #24

special opened this issue May 26, 2019 · 0 comments
Labels
api API design and changes enhancement New feature or request help wanted Extra attention is needed

Comments

@special
Copy link
Contributor

special commented May 26, 2019

QBackendProcess, Crimson.QBackend.Connection, and any other artifacts of the QML API from before instantiable types (and connection at import time) don't work anymore, and can't work. The connection still fully supports clients/backends in separate processes; it doesn't care at all.

Those should be removed and cleaned up, and we should figure out other API for QML applications that aren't launched by Go / backend/qmlscene. The QML plugin currently gets connection info from a context property, commandline argument, or environment variable.

One thought is that it's possible to configure/setup the backend from QML as long as that happens before the main Crimson.QBackend import is ever used. That's not too hard with the use of a Loader from the root object..

There should also be better/documented Go-side API for this.

@special special added enhancement New feature or request help wanted Extra attention is needed api API design and changes labels May 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api API design and changes enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant