I have been thing a bit about the api of panel-components and the optimal api.
I have a few considerations
The api of panel-components is using a lot of lists and dictionaries to hold different kinds of .js and .css for the header and body bottom.
Every time you miss something non .js or .css in the header (like language, favicon, ...) you would need to add yet another parameter to store it.
There are a lot of existing python HTML generators out there. I am thinking that maybe the right thing to do is to lean on them by either using them or getting inspiration from them.
If possible please explain if this is not a good idea and why? Why is a new python html generator for panel needed?
I have been thing a bit about the api of panel-components and the optimal api.
I have a few considerations
There are a lot of existing python HTML generators out there. I am thinking that maybe the right thing to do is to lean on them by either using them or getting inspiration from them.
If possible please explain if this is not a good idea and why? Why is a new python html generator for panel needed?