On the back of @haishiro’s question How to create a self contained custom panel I’ve started writing the Awesome Panel Extensions Guide.
I’ve added @haishiro’s example as a reference example to the subsection on Composed Extensions
Any comments and suggestions are very welcome. As I have not seen this described in detail before, so for me it’s like discovering and inventing a new structure and terminology.
If you already have it/ understand it, then I would like to avoid reinventing the wheel.
The current roadmap is
These are things that I currently don’t know. So any comments, suggestions, links or code snippets you can share would be very much appreciated.
For me it looks like the use cases for Panel so far have been creating end products like dashboards and apps.
I see libraries of Panel Extensions as a natural, emerging use case as our use cases, code base and knowledge increases. The libraries can be private for just your work or shared across the community.
As the Panel Extensions use case is new (to anyone but Panel contributors) I think this use case is not fully supported in the current design of Panel. I’ve created a few issues on Github in this regard.
and there is new WebComponent pane that I need published some where (See PR on WebComponent) to more easily support Panel extensions with bidirectional communication.
I’ve updated the documentation based on some discussions on Github
Check it out at https://awesome-panel.readthedocs.io/en/latest/guides/awesome-panel-extensions-guide/index.html
