Planning for Leo 6.2

[Edward K. Ream]

I have spent much of this week planning for Leo 6.2.

Summary: 6.2 will continue to add the best features from pyzo, emacs, vim and VS code.

Issue labels

Revised issue labels help me sort it all out. The Info label now has subcategories: BuildInfo, DevInfo, ReleaseInfo and UserInfo. These categories exclude Delegated items.

As before #1064 summarizes all of Leo's labels.  The new categories have simplified this and other issues.

6.2 priorities

The 6.2:First and 6.2:Next and 6.2:Later filters give a rough idea of my priorities.  If you are particularly interested in a "later" item, let me know.  Or better, do it yourself :-)

Conflicting ideas about bridges

I am conflicted about bridges between Leo and other editors.  I am excited about the VS code bridge (leointeg), but in general I am leery of such projects, as discussed in #1409 and #906.

I'll use bridges like leointeg when and if they appear, but in general I'll simply add features from other IDE's directly to Leo.

The integration of Leo and pyzo is a special case.  See #1384. Leo already can use pyzo's docks within Leo itself.  It would be foolish to avoid closer integration between Leo's legacy docks and the new pyzo docks.  The key task is to make some Leo commands available to pyzo.  If we actually used a pyzo bridge (to run pyzo separately from Leo) pyzo's Logger and History Viewer docks can be "repurposed" to act somewhat like Leo's minibuffer.  But when using pyzo's docks directly in Leo, we can execute Leonine commands (inside pyzo) using the minibuffer.  So yes, it's complicated :-)

Summary

Various bridges between Leo and other IDE's continue to be intriguing.  However, my primary focus will be to "steal" as many features as I can from Pyzo, Emacs, Vim and VS Code.

I have reorganized Leo's issues and labels to clarify all the choices.

Edward