I think it is more likely that a browser-based *front-end *can be achieved, rather than trying to host Leo itself in the browser. In this way you could host *your* Leo from your home/work computer or a cloud instance. The thought of this is pretty exciting to me.
I believe that Flexx <http://flexx.readthedocs.io/en/latest/> could be used effectively to achieve this. The main benefit I see is that it is a pure python library which has the implication of not requiring PyQt as a dependency, potentially improving deployability. It is very much in development so I would guard against any heavy development with it quite yet. As a clarification, I'm not saying that anyone *should* work on such a front-end, but that I believe this library would *enable* one to. On Tuesday, November 8, 2016 at 9:58:54 AM UTC-5, Edward K. Ream wrote: > > On Sunday, November 6, 2016 at 10:17:52 PM UTC-6, Chris George wrote: > > 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. >> ... >> > It looks like at least the first restriction on making a web enabled Leo >> has fallen. >> >> http://www.pythonanywhere.com/ >> > > I doubt it. I have been aware of PythonAnywhere for some time. It may > allow hosting a python app on the web, but it almost surely will not host > PyQt. And there are likely other serious problems . If #1 were truly > solved, it would be earth-shaking news. I haven't felt the earth shake ;-) > > EKR > -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
