-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any support for "compound panels"? #48
Comments
Thank @deeplook for opening and this and the screencast! Yes it should eventually support restoring workspaces programmatically, so it becomes possible to script the UI in Python even more (by supporting the underlying Lumino layout format, or hooking into the lab workspace restoration). |
Some more stuff here: jupyterlab/jupyterlab#12644 (comment) |
I might be able to take a look at this in the near term. I'm thinking the rough python API would be something like: app = JupyterFrontEnd()
app.shell.workspace.data = {"layout-restorer:whatever": {}}
app.shell.workspace.metadata = {"layout-restorer:whatever": {}} Presumably these would also be observable as individual traitlets. Going deeper into the model is probably not advisible as the children tabpanels come and go. This would allow:
This would work... poorly in retro/notebook 7 of course, though... |
Hm, one thought here: this might require a new |
I think it's not existing yet, but it would be very nice to have some workspace-like support for panels. This would allow to create panel sets with some predefined layout as in the attached example from the start. At the moment I can create these only as a sequence filling up (and cluttering) the space, and I have to drag and drop them heavily to achieve some desired layout. I have used HBox/VBox hierachies before, but this is just so much more dynamic. ;)
The text was updated successfully, but these errors were encountered: