About Leo and vs code

[Edward K. Ream]

I would like to say just a few words about Leo's future as it relates to vs code.

1. Leo will remain a stand-alone pure python app indefinitely. It would be a huge mistake to deprecate Leo as a stand-alone app. Leo's existing plugins, such as Terry's todo.py and backlink.py plugins have no direct counterpart in the vs code world.

2. vs code is likely to be an increasingly big part of Leo's world. Imo, this is a very good thing. A Leo plugin for vs code promises to introduce many more people to Leo than ever before.

Implications

Further improvements to Leo's gui will likely be less important in the future. Instead, it will likely be more productive to add Leonine features to vs code. However, this is a debatable point. I'm not strongly committed to it.

The more work is done on leoInteg, the more strongly Leo's core features come into view. I'll do everything I can to sharpen the focus.

Leo issue #1613 has high priority.

Summary

Leo will remain a pure python app indefinitely.

leoInteg promises to introduce many more people to Leo.

leoInteg might reduce the importance of editor-related improvements to Leo.

It remains to be seen how much work I'll do with leoInteg.

Edward