Rev 342ce7b in devel: prototype of Leo's unified Qt gui

48 views
Skip to first unread message

Edward K. Ream

unread,
Jun 7, 2019, 7:24:04 AM6/7/19
to leo-editor
This rev only changes how Leo handle's command-line args:

- Leo ignores --no-docks, and issues a warning.
- Leo changes --gui=qt to --gui=qttabs, and issues a warning.

That's all this rev does. However, this should be an excellent prototype for the code simplifications to be done in the "unity" branch.

As always, please report any problems.

Edward

Edward K. Ream

unread,
Jun 7, 2019, 12:56:00 PM6/7/19
to leo-e...@googlegroups.com
On Friday, June 7, 2019 at 6:24:04 AM UTC-5, Edward K. Ream wrote:

This rev only changes how Leo handle's command-line args:

- Leo ignores --no-docks, and issues a warning.
- Leo changes --gui=qt to --gui=qttabs, and issues a warning.

Hmm. Perhaps the "unity" branch isn't needed.  This branch was supposed to remove all legacy code.  But that seems drastic:

- Removing legacy code will not substantially simplify Leo.
- The g.app.dock switch is, for now, an excellent marker that distinguishes legacy code from new code.

Instead, I am considering a "cruft" branch that would merely do the following:

- Remove code needed for --gui=qt.
- Remove commands that we all agree should go.
- Remove some other ancient cruft that is never used.

Surely these three items can be done without any fear of future regrets.

All comments welcome.

Edward
Message has been deleted

Edward K. Ream

unread,
Jun 8, 2019, 6:42:34 AM6/8/19
to leo-editor


On Friday, June 7, 2019 at 6:24:04 AM UTC-5, Edward K. Ream wrote:
This rev only changes how Leo handle's command-line args:

- Leo ignores --no-docks, and issues a warning.

Belay that.  Rev 1e94f74 reinstates --no-docks.  Leo 6.0 final will support --no-docks.

This ends the dithering on this subject.

Edward
Reply all
Reply to author
Forward
0 new messages