I've been working on this, still not clear quite how big a task it will be, but
I think quite significant. I actually have a version which works, opening all
the tabs (Log, Find, etc.) in a tabbed dock etc., but I'm sure it would break a
bunch of unit tests etc., and plugins. Things like Ctrl-F in body selecting
the Find widget work quite easily.
But I'm not sure if I want to proceed from that version, which inherits a
confounding between the log widget and the tab pane, or try and clean up the UI
start up a bit. For very reasonable hysterical raisins(*) the separation
between the *log* widget, where logging output goes, and the tabbed pane that
holds the log, find, spell, nav etc. is unclear. .createTab() is a method of
the log class, and I keep running into the circularity of wanting to create a
tab to put the log and other tools in, but until you've created the log you
can't create a tab... obviously the current system works, with finishCreate()
style methods, but I'm not sure if I want to add to the many levels present, or
try something else.
I also need to research more how QMainWindow .save/restoreState() works. It
creates an opaque type, and the naive approach of calling save, moving a
splitter, then calling restore with the output from the save call does not
work. Presumably something needs to be done with the restoreDockWidget method.
Although I'll persist for now with the `if g.qtdock:` approach to develop new
code alongside old, if this project is successful I think a lot of old code
will be able to be stripped out - cross that bridge if / when we get to it.
(*) historical reasons, but hysterical raisins is much funnier :-)
Cheers -Terry
From: Edward K. Ream <[email protected]>
To: leo-editor <[email protected]>
Sent: Friday, September 30, 2016 6:15 AM
Subject: Re: Qt docking as a replacement for NestedSplitter "Easteregg" menu.
On Mon, Sep 26, 2016 at 1:42 PM, 'Terry Brown' via leo-editor
<[email protected]> wrote:
https://github.com/leo-editor/ snippets/blob/master/examples/ layout/qtdock.py
is a Py 2.7 / Qt 4 demo of Qt docking as it might apply to Leo, with comments
in the doc. string. I think it's definitely worth switching to this, so now
it's simply a matter of finding time :-)
The demo is impressive. A lot of results with not much code. I'll look
forward to future progress.
EKR--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
