On 6/19/2013 1:35 PM, Terry Brown wrote:
For the next 2.25 weeks I'm going to be traveling, Reykavik and St.
Petersburg (Russia, not Florida :-). So there may not be much more to
report for a while, but I've started what looks like a promising
attempt at a web interface to Leo. Very much based on a path of least
resistance for my skill set.
So far you can drag nodes around the tree, cut and paste and insert
them, and edit the headline text. And tell the server to save the
outline. The architecture is:
Python's BaseHTTPServer running the 'server'.
New code ('leoweb.py') communicating with the browser.
jQuery and jQuery-UI handling the interface (authored in coffeescript).
And the critical link - leoBridge as the backend for leoweb.py.
So in an odd way this is a database driven Leo, using Leo as the
backend database :-) I'm trying to minimize the dependencies,
currently they're essentially zero, seeing jQuery and jQuery-UI are
publicly hosted.
Still some work on the core to do, i.e. handling expansion /
contraction properly. Then body text editing, which should be
reasonably straight forward. Then... and this is where this can become
so much more than just another on line outliner, minibuffer commands.
Which of course is a huge security issue, but never mind that for now.
Because of the path of least resistance requirement I'm not trying to
implement a Leo UI, i.e. another version of Leo's UI code of which
there is currently the nullGui and Qt versions, and used to be the Tk
version. This might evolve in that direction, or not, I'm not sure.
The event loop is in the user's browser in javascript and not on
the server in python. But it would be a shame not to be able to do
some of the things that require knowledge of body editor cursor position
and selected text, for example, so we'll see what happens.
So currently it's essentially a new, coffee/javascript based editor of
Leo outlines with the power of leoBridge to call on.
Cheers -Terry
Sounds awesome. I had been kicking around the idea of a javascript leo
outline *viewer* (not editor) that would pull .leo files from
gist.github.com, and display them, as a quick way of sharing outlines
with others, as, to (mis-)quote Edward, "Leo doesn't do email very
well". This sounds like just the thing... assuming you open up the
codebase, it probably wouldn't be hard to hack in a "grab from gist"
method to pull in .leo outlines, giving us a sort of pastebin for .leo
outlines.
-->Jake
--
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
