This is a continuation of two threads: Pare Leo down and make it a plugin 
<https://groups.google.com/forum/#!topic/leo-editor/deuYxDaYE5M>, and My 15 
year plan <https://groups.google.com/forum/#!topic/leo-editor/OBEcLI60vN4>. 
More so than usual, I am thinking out loud here. All comments welcome.

It is tempting to think that one could, starting with Leo's existing code 
base, integrate Leo into Emacs, vim, Eclipse and (my favorite) 
IPython/Jupyter. Indeed, if I could start over on Leo (back in 1985, say), 
I would seriously consider adding yet another mode to Emacs.  Similarly, 
given the work I did with vim emulation, it might have been better to 
attempt to embed Leo into vim, rather than the reverse.

But this is not 1985, and I am 30 years older now.  I don't have 30 more 
years ahead of me. I have no desire to create work just to keep busy. I 
certainly can not commit to multiple projects such as Leo-in-Emacs, 
Leo-in-Vim or Leo-in-Jupyter (Leo-in-CoffeeScript). Any one of these 
projects might take years.

I personally can disqualify Leo-Emacs or Leo-in-Vim immediately.  Although 
such a project might make Leo more popular, I would never use such things 
myself.  I like Leo as it is, with Qt's great widget set.

Leo-in-Jupyter (written in CoffeeScript) has more personal interest, but it 
has its own, er, "challenges".  The foremost is that Jupyter is a huge 
project run by others.  Even if Leo could be integrated into Jupyter, it 
seems unlikely that the "governors" would approve.

Lastly, I could conceive of doing a "straight" version of Leo in 
CoffeeScript.  But this runs smack into serious problems:

1. Security.  Jupyter claims to be secure, and they may be, but the 
machinery involved is complex.  I have no confidence that Leo could be made 
secure.

2. Widgets. There are many widget sets and other frameworks to choose 
from.  My brother, who knows much more about such things, has no clear 
recommendation to make.

In short, Leo in CoffeeScript would be a huge, high-risk project.

Instead, I would rather explore solving problems with Leo as it is. I have 
said many times that we have just begun to explore what is possible with 
Leo. That hasn't changed, and I expect that extending Leo as it is will 
continue to be my focus.

Edward

-- 
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.

Reply via email to