Just a couple of dock related thoughts. To replace the functionality of the NestedSplitter interface the dock layout needs to support multiple (named) persistent layouts of plugin docks (widgets in docks, really, plugins don't need to know about docks specifically). I used this to make Leo into things like a DB schema editor and a graph editor and a todo / calendar manager.
I had this kind of persistence mostly working in my attempt at docks, if that's a useful reference. Basically plugins register as widget providers and the layout machinery works down the list of providers asking who can provide "X" when it's restoring a layout. I assume you're allowing all docks to be tabbed docks? So essentially every "pane" becomes (optionally) a "tab-pane". This lets you have a lot of widgets "on-hand" without consuming lots of screen space. Also I'm not sure if you still have a central widget, but the that a central widget can't be dragged into a different dock relationship or receive incoming dragged docks(*) seems like it would be an unnecessarily confusing asymmetry. * I guess it could receive them for left/right/above/below, but not as a tab sibling, so still confusing. General thoughts but mainly just a reminder that NestedSplitter persists plugin widget layouts. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/20190528093752.0a9ed70a%40lakeview. For more options, visit https://groups.google.com/d/optout.
