For those who didn't get to try it, the link was to an in-browser remote desktop session running Leo with its regular PyQt interface. It's gone now, too big a hole to leave open very long.
On Mon, 13 Oct 2014 17:23:19 +0200 Fidel N <fidelpe...@gmail.com> wrote: > wow its great, isnt that what everyone is talking about? Not exactly, it's basically a remote desktop session which can be accessed from a browser, with Leo running in the session. My thought is that if you have a server which can run leoBridge, it may also be able to run a virtual desktop with the Qt gui as well. I guess the assumption is that leoBridge will run headless with minimal python libraries, so it could be run on a range of web accessible computers, and the javascript interface is needed to interact with it, and in general I'd say that's true. The assumption is that running leoBridge is a lower bar than running PyQt and a virtual desktop of some kind, and that's probably true, although I feel I'm now doomed to spend time trying to get this to run on my Raspberry PI http://www.raspberrypi.org/ :-) > Is it easy to setup? Yes, I created a user on an Ubuntu machine, to get a default set of limited rights, including not having access to my personal files... which I realize isn't the case... plug pulled :-} Anyway, I then had that user run a vncserver instance, which is not really a virtual machine as such, http://en.wikipedia.org/wiki/Virtual_Network_Computing the word virtual is a misnomer here. And run Leo on the desktop of the vncserver. Then I set up https://github.com/kanaka/noVNC to provide web access, using the ``./utils/launch.sh --vnc localhost:5901`` proxy for access to the vncserver. Anyway, it was just an experiment - if you have a web attached server which can run vnc and PyQt, you can use full Leo online anyway, but the javascript interface is needed for cases where your server can only run leoBridge. Although I think it's untested, the assumption would be that the basic Python environment available in many hosted servers could run leoBridge. Cheers -Terry > On Mon, Oct 13, 2014 at 4:34 PM, 'Terry Brown' via leo-editor < > leo-editor@googlegroups.com> wrote: > > > On Mon, 13 Oct 2014 08:59:41 -0500 > > "Edward K. Ream" <edream...@gmail.com> wrote: > > > > > On Mon, Oct 13, 2014 at 6:16 AM, Kent Tenney <kten...@gmail.com> > > > wrote: > > > > It would only require permissions for In-browser-Leo to > > > > enable collaborative editing at the level of: > > > > "I'll type in this url and open the Leo file that Edward just > > > > mentioned" > > > > > > > > which would presumably be read-only. > > > > or not: > > > > "I'll add a comment to this node in said file" > > > > > > Good point. > > > > > > > both of those seem to be core capability, as opposed to: > > > > "I'll make changes to this file while Edward is making changes > > > > to this file" > > > > > > > > Which is not only technically challenging, but of dubious > > > > utility. > > > > > > I agree. The basic capability you mention would indeed be a > > > breakthrough. > > > > So what do people see when they go here > > http://moth.nrri.umn.edu:6080/vnc.html?host=moth.nrri.umn.edu&port=6080 > > password leouser? > > > > 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 leo-editor+unsubscr...@googlegroups.com. > > To post to this group, send email to leo-editor@googlegroups.com. > > Visit this group at http://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. > > > -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
