-
Notifications
You must be signed in to change notification settings - Fork 7
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
Problem with imageJ api using imjoy-core in React #82
Comments
Hi, you should do 'const ij = await api.createWindow({src: "https://ij.imjoy.io"})' as documented in the docs. |
Im getting api property from imjoy instance, api variable doesnt exist. And I've also used imjoy.api to get Jupyter-Engine-Manager plugin, which worked. |
You should get Alternatively, if you can also use the ImJoyBasicApp: https://github.com/imjoy-team/imjoy-core/blob/master/docs/integration.md#load-imjoy-basic-app A complete example here: https://github.com/imjoy-team/imjoy-core/blob/e586a9fb8bd8195acd9a61d0b5928259f076ea17/src/simple-app-example.html Once you have the imjoy setup ready, you can do Also see here: https://imjoy.io/docs/#/api?id=apicreatewindow |
Im trying to make a simple image operation with imageJ, but ImageJ.JS argument isnt working when connecting to imjoy api.
This code gives me error Uncaught (in promise) Plugin not found: ImageJ.JS and logs null. It works if I call Jupyter-Engine-Manager plugin instead.
I've tried many different ways of using this api, including passing
{src:"https://ij.imjoy.io/"}
as argument, changinggetPlugin
tocreateWindow
andgetWindow
. None of them worked. Also tried using just javascript and html by using this imjoy script:<script src="https://lib.imjoy.io/imjoy-loader.js"></script>
and callingloadImJoyCore
, which it also didnt work.When I tried replicating the code in Chrome DevTools, in ij.imjoy.io, using imjoy instance in window, it worked as expected, even by using the same method as the function above (
...getPlugin("ImageJ.JS"...
)I should also say im running the application in my localhost, not in production.
The text was updated successfully, but these errors were encountered: