In the "Rules of the Internet" (www.rulesoftheinternet.com), Rule 34 says "There is porn of it, no exceptions". This means that if anything exists, there is a porn version of it somewhere, and if there isn't, there soon will be.
The rules need to be updated to include Rule 34j, which states "There is a client-side javascript version of it". In other words, for all software, there is a corresponding javascript program that is rapidly evolving to achieve the same thing. Terry, what you're doing is brilliant and long overdue. The whole computing world is headed into the cloud, and if Leo is to stay relevant, it needs to go there as well. What I would ask is does your JS Leo allow concurrency? What a Cloud Leo desperately needs is the ability to have n people editing it concurrently and seeing where each other are at, just like with Google Docs. I am hanging out to see how this evolves. Cheers David On Thu, Jun 20, 2013 at 5:35 AM, Terry Brown <[email protected]>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 > > > -- > 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. > > > -- 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.
