On Thu, Sep 19, 2013 at 9:27 PM, Terry Brown <[email protected]>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. > Correct. > > > 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. > > because often web app. refers to a browser front end to an app. running > > on a server, in any language. E.g. running in C-python and using > > leobridge. > I didn't know that! So there *is* a feasible way! Furthermore, this would solve a problem that I didn't mention, namely the different file-access capabilities of desktop Leo versus HTML5 Leo. > > > 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. > > Good point. I would really like to get back to the leo web interface I > was working on, but just can't at the moment. > .. > > I'd got to the point where node insertions / moves in browser A were > relayed to browser B by the server (running firefox and chrome at the > same time works well to test these setups, although I think both have > multiple distinct instance modes). Hopefully things that create / > remove / move multiple nodes could be handled in a similar way, hooking > > c.redraw() maybe. > Please keep us all informed of your progress. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
