Re: LeoWapp plans

> > Matt, I'm not sure how this will affect your distro work. I do know that > the following pulls in a lot of packages: conda install flexx -c > conda-forge > It looks pretty straightforward, but maybe I'll wait until we know if flexx is more than an experiment before adding it as a

Re: LeoWapp plans

On Thu, 1 Nov 2018 20:41:48 -0700 (PDT) Matt Wilkie wrote: > > I think "Flexx uses tornado" was a crossing of threads (ha ha ha), > > I don't think it does. > > I know nothing about web sockets or the frameworks discussed in this > thread, but the docs say >

Re: LeoWapp plans

On Thu, Nov 1, 2018 at 10:41 PM Matt Wilkie wrote: > I think "Flexx uses tornado" was a crossing of threads (ha ha ha), I >> don't think it does. >> > > I know nothing about web sockets or the frameworks discussed in this > thread, but the docs say >

Re: LeoWapp plans

> > I think "Flexx uses tornado" was a crossing of threads (ha ha ha), I > don't think it does. > I know nothing about web sockets or the frameworks discussed in this thread, but the docs say *"Flexx further depends on the

Re: LeoWapp plans

On Thursday, November 1, 2018 at 10:04:08 AM UTC-5, Edward K. Ream wrote: With every step I take on this project, the goal seems to get closer faster > than expected. > I expect to complete the so-called skeleton in a day or three. When that happens, devs will be able to prototype LeoWapp

Re: LeoWapp plans

On Thursday, November 1, 2018 at 5:53:39 AM UTC-5, Edward K. Ream wrote: Rev 64742bc16 in dev demonstrates the main idea. > > Starting Leo with `leo --gui=browser` successfully goes through Leo's > startup logic and calls BrowserGui.runMainLoop, which in turn runs all > Leo's unit tests and

Re: LeoWapp plans

On Thu, Nov 1, 2018 at 5:53 AM Edward K. Ream wrote: > The skeleton will provide explicit redirection methods for each and every member of the high-level api... > the BrowserGui class [will be] a subclass of LeoGui, not NullGui. This will force the BrowserGui class to implement all methods of

Re: LeoWapp plans

On Wednesday, October 31, 2018 at 3:22:44 PM UTC-5, Edward K. Ream wrote: This is close to my present plans, which is to create what might be called > a skeleton browser gui. > Rev 64742bc16 in dev demonstrates the main idea. Starting Leo with `leo --gui=browser` successfully goes through

Re: LeoWapp plans

On Wed, Oct 31, 2018 at 11:27 AM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > I would try something like this for a minimal prototype: > >- Express a minimal Leo tree (with clones) as a Inspire Tree (yes I >know I have chosen a particular tech for interface). >- See how

Re: LeoWapp plans

Hi, I would try something like this for a minimal prototype: * Express a minimal Leo tree (with clones) as a Inspire Tree (yes I know I have chosen a particular tech for interface). * See how can I send changes to the Inspire Tree from a web interface (maybe using events). *

Re: LeoWapp plans

On Wed, Oct 31, 2018 at 10:17 AM vitalije wrote: For websocket to work there must be some thread which would check socket > and call appropriate methods/functions when websocket has been open, > closed, or new message has arrived. This thread should also take your > outgoing messages and send

Re: LeoWapp plans

I think "Flexx uses tornado" was a crossing of threads (ha ha ha), I don't think it does. Flexx completely hides the websockets part, it's more like React (I think, having used that once), but basically signals / listeners / actions / reactions. It actually takes a while to understand what part

Re: LeoWapp plans

> > Does that mean you think the flexx framework is a good idea? Or do you > mean that Tornado itself would be the framework? > I don't know about flexx. But you wrote above that flexx uses tornado for websockets. I conclude from that tornado is lower level than flexx. And I have implemented

Re: LeoWapp plans

On Wednesday, October 31, 2018 at 9:28:02 AM UTC-5, Terry Brown wrote: I mentioned this elsewhere, but just want to say Flexx is different in > that it translates Python to javascript, although not really, really > it lets you write javascript using Python syntax. So its intent is > that you

Re: LeoWapp plans

On Wednesday, October 31, 2018 at 9:30:37 AM UTC-5, Edward K. Ream wrote: The first version of the script hard-coded the path to unittest.leo: c = controller.openLeoFile(r'c:\leo.repo\leo-editor\leo\test\unittest.leo') However, we can use the bridge's g.app.loadDir to generalize the code:

Re: LeoWapp plans

On Wednesday, October 31, 2018 at 5:32:33 AM UTC-5, Edward K. Ream wrote: 2. Create a hack that runs all unit tests. I expect all gui-related tests > to fail. > Leo's own --script logic is byzantine. It's simpler just to run the following test file from python itself: import

Re: LeoWapp plans

I mentioned this elsewhere, but just want to say Flexx is different in that it translates Python to javascript, although not really, really it lets you write javascript using Python syntax. So its intent is that you don't write javascript, and if you do it that way, you probably won't be able to

Re: LeoWapp plans

On Wed, Oct 31, 2018 at 6:05 AM vitalije wrote: > I was thinking to suggest tornado but there were already lots of > suggestions, so I decided rather not to. > Your timing is spot on. Earlier I would not have been able to handle more suggestions. > > Tornado has websockets integrated and it

Re: LeoWapp plans

I was thinking to suggest tornado but there were already lots of suggestions, so I decided rather not to. Tornado has websockets integrated and it is quite easy to use them. Tornado supported until recently Python 2.7 and earlier versions of Python 3. So it used to have some back-ported

Re: LeoWapp plans

On Wednesday, October 31, 2018 at 5:32:33 AM UTC-5, Edward K. Ream wrote: flexx looks like exactly what LeoWapp needs, but I won't commit to flexx > until much later, if at all. > I forgot to mention two things: 1. Studying vue.js is high on my list. An important goal of LeoWapp is to

LeoWapp plans

Terry, Speed and Offray recommend flexx, web.py and web2py frameworks respectively. The "don't do stuff twice" principle does not apply to study :-) I have just committed study outlines for websockets and flexx to leo-editor-contrib . Having