-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
[FEATURE] Add a DocumentReady event #10265
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
Comments
Noting that the work in #10266 was only for a Python/Bokeh server event, not yet for |
Right, should have checked this but a Document does not yet have the ability to register js callbacks on it. |
@philippjfr this issue got closed is there a (new?) issue for a JS init event? (I actually thought there was a different older issue about this than this one but I can't find it if so) |
@philippjfr I was wondering the same thing, I was trying to register a JS callback on this event, but didn't find any documentation that implied it didn't work until I came across this issue. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
In many cases you want your application to display something as quickly as possible. In the current design of bokeh server everything has to be initialized in the initial request. One solution to alleviate this issue would be to defer any expensive computation on initialization until after we have actually rendered something to screen. However currently there is no way to tell when the frontend is done initializing the rendered Document.
Therefore I propose adding a BokehEvent which signals when the Document is ready (or in BokehJS terminology, when it is idle).
The text was updated successfully, but these errors were encountered: