Others have stated great reasoning. So I don't want to recap but I'll add. In the cloud age "traditional platform" doesn't mean what it used to. The Leo "server" needn't be your computer, but could be a cloud based virtual machine that with guaranteed accessibility and uptime.
As a pure python dependency it should improve deployability. Less licensing nonsense than using Qt/PyQt. The pure python nature of Flexx and pure python nature of Leo's backend also means there is the potential to PyPy for a potentially large performance gain. Flexx has been testing on PyPy. And perhaps one of the more important reasons, despite the best efforts of a great many of us it seems like browser-based technology is taking over. More and more "applications" are making their way towards the browser. Take that for what it's worth but this is one of main reasons Flexx was created in the first place. On Monday, November 14, 2016 at 2:44:20 PM UTC-5, Edward K. Ream wrote: > > On Mon, Nov 14, 2016 at 1:37 PM, Chris George <techn...@gmail.com > <javascript:>> wrote: > > I envisioned the python code running on a server and a team using one >> instance of Leo to work on a project. >> >> Or myself keeping my monolithic information Leo file on a running >> instance on a server and being able to access it from anywhere, anytime, >> with any device. >> > > Thanks. This is clear enough. I'll file an enhancement soon. > > 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.
