Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Mon, Nov 14, 2016 at 1:44 PM, Edward K. Ream wrote: ​> ​ I'll file an enhancement soon ​. It is #338 . EKR​ -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group

Re: Python Anywhere

2016-11-14 Thread john lunzer
One last thing. I realize this would be a big move and detract from core development. Almar Klein is the creator of Flexx. Almar also is the creator of Pyzo which is a Python IDE which currently uses PyQt as the GUI Toolkit. Unless I'm mistaken I believe the inte

Re: Python Anywhere

2016-11-14 Thread john lunzer
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

Re: Python Anywhere

2016-11-14 Thread john lunzer
? > The JupyterLab demo looked pretty good. > > Cheers -Terry > > -- > *From:* Edward K. Ream > > *To:* leo-editor > > *Sent:* Monday, November 14, 2016 1:30 PM > *Subject:* Re: Python Anywhere > > > > On Sun, Nov 13, 2016 at 12:39 PM

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Mon, Nov 14, 2016 at 1:37 PM, Chris George 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

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Mon, Nov 14, 2016 at 1:36 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > As far as I know there's no "Qt in a browser window" stack. So if Flexx is > a Python event callback style interface that renders in a browser, it could > be a useful start. Because it would allo

Re: Python Anywhere

2016-11-14 Thread Chris George
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. The code runs on the server, the

Re: Python Anywhere

2016-11-14 Thread 'Terry Brown' via leo-editor
dward K. Ream To: leo-editor Sent: Monday, November 14, 2016 1:30 PM Subject: Re: Python Anywhere On Sun, Nov 13, 2016 at 12:39 PM, john lunzer wrote: 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&#

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Sun, Nov 13, 2016 at 12:39 PM, john lunzer wrote: 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'm trying to understand what the benefits are. If only the gui changes, Leo will still be tied to a tr

Re: Python Anywhere

2016-11-14 Thread john lunzer
Flexx uses Phosphor as well (it's pulled in which is why it is not a dependency). On Monday, November 14, 2016 at 2:08:00 PM UTC-5, Offray Vladimir Luna Cárdenas wrote: > > On the Web GUI front end, Jupyter project is working on Jupyter Lab, using > Phosphor. Maybe is worth checking: > > https:

Re: Python Anywhere

2016-11-14 Thread Offray Vladimir Luna Cárdenas
On the Web GUI front end, Jupyter project is working on Jupyter Lab, using Phosphor. Maybe is worth checking: https://github.com/jupyterlab/jupyterlab Cheers, Offray On 14/11/16 11:22, Edward K. Ream wrote: On Mon, Nov 14, 2016 at 10:10 AM, john lunzer > wrote:

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Mon, Nov 14, 2016 at 10:10 AM, john lunzer wrote: > Web-based front-end simply means that the GUI runs in a browser. > > My understanding of Flexx is that you can use it in the same way that you > would use PyQt. I do not believe it places restrictions on the rest of your > Python code. > > I

Re: Python Anywhere

2016-11-14 Thread john lunzer
Web-based front-end simply means that the GUI runs in a browser. My understanding of Flexx is that you can use it in the same way that you would use PyQt. I do not believe it places restrictions on the rest of your Python code. I do agree that the language on the docs site is a bit obtuse. If y

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Mon, Nov 14, 2016 at 9:42 AM, Edward K. Ream ​> ​ Do I feel a slight tremor under my feet? >From the PyScript docs: ​QQQ​ PyScript is a tool to write JavaScript using (a subset) of the Python language. ​ ​ All relevant ​ ​ builtins, and the methods of list, dict and str are supported. Not su

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Mon, Nov 14, 2016 at 9:26 AM, Edward K. Ream wrote: > On Sun, Nov 13, 2016 at 12:39 PM, john lunzer wrote: > > I believe that Flexx could be >> used effectively to achieve >> ​[a browser front end]. >> > > ​Do I feel a slight tremor under my feet? > F

Re: Python Anywhere

2016-11-14 Thread Edward K. Ream
On Sun, Nov 13, 2016 at 12:39 PM, john lunzer wrote: 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

Re: Python Anywhere

2016-11-13 Thread john lunzer
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

Re: Python Anywhere

2016-11-08 Thread Edward K. Ream
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 restri

Python Anywhere

2016-11-06 Thread Chris George
Pulled this quote from LeoToDo.txt "There are two reasons why Leo is unlikely ever to be a web app. 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. 2. Creating a L