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
Currently each application imports and uses from awesome_panel_extensions.site import site.
The the site.create_application adds a lot of code/ overhead to each application.
This also "forces" us to use pn.serve and I believe panel serve is simpler to use and more supported.
Request
Get rid of site.create_application and @site.add.
Solution
I would suggest a solution where each application is registered in a .yaml file in the exact same way as the awesome_list.yml file.
This file should be used to populate the App Gallery.
We would also have to find a way to populate the menu and info section of each page. Or alternatively give up on that part.
Additional Context
We could also just get the long site.create_application part out of each app. Move the registration to the awesome_panel_extensions package or even better a dedicated awesome_panel package. That would make the app simpler but still make it possible to provide meta information and a menu to each app.
The text was updated successfully, but these errors were encountered:
MarcSkovMadsen
changed the title
Get rid of awesome_panel_extensions site dependency.
Move site.create_application out of each application
Dec 18, 2021
MarcSkovMadsen
changed the title
Move site.create_application out of each application
Remove site.create_application from each application
Dec 18, 2021
Currently each application imports and uses
from awesome_panel_extensions.site import site
.The the
site.create_application
adds a lot of code/ overhead to each application.This also "forces" us to use
pn.serve
and I believepanel serve
is simpler to use and more supported.Request
Get rid of
site.create_application
and@site.add
.Solution
I would suggest a solution where each application is registered in a
.yaml
file in the exact same way as the awesome_list.yml file.This file should be used to populate the App Gallery.
We would also have to find a way to populate the menu and info section of each page. Or alternatively give up on that part.
Additional Context
We could also just get the long
site.create_application
part out of each app. Move the registration to theawesome_panel_extensions
package or even better a dedicatedawesome_panel
package. That would make the app simpler but still make it possible to provide meta information and a menu to each app.The text was updated successfully, but these errors were encountered: