You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating a custom ipyWidget for Jupyter notebooks and blocked on the right architecture for my widget
These are the order of action I want to be performed:
In python kernel: Call a method of my widget class, say myWidget.ExtractData()
In python kernel: Somehow call a JavaScript method in frontend
*Currently I update the shared state field and listen for state change on frontend (JS) side and execute that function
In widget frontend: Execute some task (~2 sec)
In widget frontend: Somehow return the computed value back to python kernel
*Currently I update another shared state field and listen for state change on python kernel side
In python kernel: Receive the data sent by JS method (in frontend) and return that data from this myWidget.ExtractData() function
*Not able to implement this. Currently I am reading the data directly from the shared state of the widget, which is not the expectation
Q1: Is it possible to implement this expectation?
Q2: If yes, please suggest me some advise, docs or examples where such scenarios are explained/implemented
The text was updated successfully, but these errors were encountered:
I am creating a custom ipyWidget for Jupyter notebooks and blocked on the right architecture for my widget
These are the order of action I want to be performed:
myWidget.ExtractData()
*Currently I update the shared state field and listen for state change on frontend (JS) side and execute that function
*Currently I update another shared state field and listen for state change on python kernel side
myWidget.ExtractData()
function*Not able to implement this. Currently I am reading the data directly from the shared state of the widget, which is not the expectation
Q1: Is it possible to implement this expectation?
Q2: If yes, please suggest me some advise, docs or examples where such scenarios are explained/implemented
The text was updated successfully, but these errors were encountered: