If Kivy is the solution (with what I would actually agree very much),
please say what you want to get before you start working on it, because I
think I could give some useful info and scripts that already work from Leo.
I have been working
On Thu, Sep 19, 2013 at 9:27 PM, Terry Brown terry_n_br...@yahoo.comwrote:
There are two reasons why Leo is unlikely ever to be a web app.
By web app. you mean in-browser app., I'm assuming.
Correct.
1. There are somewhere around a million lines of Python code in Leo's
core
and
On Thursday, September 19, 2013 7:55:22 PM UTC-5, Differance wrote:
2. Creating a Leo outline widget is extremely complex. Even starting
with a
working javascript outliner, one has to deal with events (commands)
coming
from Leo scripts rather than from the user.
I wonder how
There are two reasons why Leo is unlikely ever to be a web app.
1. There are somewhere around a million lines of Python code in Leo's core
and plugins. Thus, a *solid* python in javascript system is required.
This isn't likely to happen.
2. Creating a Leo outline widget is extremely complex.
On Thu, Sep 19, 2013 at 6:19 PM, Edward K. Ream edream...@gmail.com wrote:
There are two reasons why Leo is unlikely ever to be a web app.
1. There are somewhere around a million lines of Python code in Leo's core
and plugins. Thus, a *solid* python in javascript system is required. This
On Thu, 19 Sep 2013 15:19:06 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
There are two reasons why Leo is unlikely ever to be a web app.
By web app. you mean in-browser app., I'm assuming.
1. There are somewhere around a million lines of Python code in Leo's core
and plugins.
