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
A few projects now have used Thebelab in Sphinx (e.g., jupyter-sphinx, sphinx-gallery, and now myst-nb). Each one has slightly different approaches to config etc, and in some cases the thebelab logic is a bit complex under the hood (e.g. jupyter-sphinx has its own thebelab nodes that replace regular cell nodes).
I wonder if it would be beneficial to have a single sphinx-thebelab extension that others could use. This extension could be used either
as a user-facing tool. e.g. provide a .. thebelab-button:: directive along with letting users configure the class used to mark a thebelab-ready cell (similar to how sphinx-copybutton works).
as a dev-facing tool. e.g., a theme developer could use thebelab buttons in their theme that are provided by this extension
I think for the most basic Thebelab functionality, this may be overkill, but as features are added we could benefit from a single thebelab package (e.g. if somebody wanted a spinning or a loading widget while waiting for the kernel).
What do folks think? Would it be useful? Unnecessary?
cc @akhmerov who may not be pinged by these issues
The text was updated successfully, but these errors were encountered:
A few projects now have used Thebelab in Sphinx (e.g., jupyter-sphinx, sphinx-gallery, and now myst-nb). Each one has slightly different approaches to config etc, and in some cases the thebelab logic is a bit complex under the hood (e.g. jupyter-sphinx has its own thebelab nodes that replace regular cell nodes).
I wonder if it would be beneficial to have a single
sphinx-thebelab
extension that others could use. This extension could be used either.. thebelab-button::
directive along with letting users configure the class used to mark a thebelab-ready cell (similar to howsphinx-copybutton
works).I think for the most basic Thebelab functionality, this may be overkill, but as features are added we could benefit from a single thebelab package (e.g. if somebody wanted a spinning or a loading widget while waiting for the kernel).
What do folks think? Would it be useful? Unnecessary?
cc @akhmerov who may not be pinged by these issues
The text was updated successfully, but these errors were encountered: