Timeline for production version

executablebooks / thebe

Turn static HTML pages into live documents with Jupyter kernels.

https://thebe.readthedocs.io

BSD 3-Clause "New" or "Revised" License

386 stars 68 forks source link

Timeline for production version #746

Closed Vislesha closed 2 months ago

Vislesha commented 3 months ago

Hi Team: Any timeline for a production version of this library? Thanks!

stevejpurves commented 2 months ago

Hi @Vislesha this library is currently in use in executablebooks/myst-theme in a "production" setting and usage in that library is driving the development direction, but a the same time serving a few different use cases from drop-on-page usage for simple html, to react integration and exposing jupyerlite/pyodide as a backend.

Can you give some more details on how you'd be using the library, or what you'd like to see before you started using it? i.e. which aspects/features you are interested in.

Vislesha commented 2 months ago

Hi @stevejpurves, thank you for the clarification.

Our requirement is slightly different than the ones shown in Thebe React example or Jupyter style notebooks. It may be almost similar to mySt books, but its integrated in a web application and also with custom layout capability.

What we are building is a user composable reporting framework with a widget-based (rather than cells) approach similar to dashboards. Users can dynamically create a report with multiple widgets in a bootstrap style grid system along with its associated code.
Users should be able to see the dynamically executed code output in the widget with the help of jupyeterlite/pyodide
Users can be able to create/edit the widgets along with its markdown and python code depending on the access permissions users have. I am wondering if this library can be used to accomplish the above requirements!

Thanks

Vislesha commented 2 months ago

Hi @stevejpurves , any comments on the above!

stevejpurves commented 2 months ago

Hi @Vislesha - yes, it can help with those features but to achieve it I would focus on thebe-core and using that part of the library for connection & session management.

That part of the library tries to be pretty framework agnostic, and mainly just wraps the JupyterLab services for you and provides some abstractions around notebooks and cells. thebe-lite is a drop in alongside thebe-core to take a closer look at that run the core demo npm run demo:core that is in https://github.com/executablebooks/thebe/tree/main/apps/demo-core

Vislesha commented 2 months ago

Thanks for the clarification, @stevejpurves! We started a PoC as per your above comments.

stevejpurves commented 2 months ago

great - one thing to add that I should have earlier is that rendering of markdown cell content is not something that thebe has out of the box support for but that would be best acheived by using the myst parser from mystmd https://github.com/executablebooks/mystmd/tree/main/packages/myst-parser having a markdown cell abstraction in thebe-core might be useful though so please let me know how your PoC goes, and whether there are things to upstream as a result of it -- happy to chat more sometime

Vislesha commented 2 months ago

Hi Steve, thanks for the revert! Yes, I believe having a simple markdown component in thebe itself would be very useful, without all the bells and whistles that mystdm has like support for LateX etc. Will keep you posted and will be glad to have a chat once our PoC comes to a shape.