Re: Might be interesting for Leo WebApp

> > I just stumbled upon a web outliner: >> >> https://dynalist.io/ >> > Even without source code, it has good ideas about its use and how it > presents its tutorial in the live demo. > 2 things from https://dynalist.io/why that immediately jump out at me as very good ideas: - `[[`

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: File changes outside of Leo

Thanks, Edward. This has been really tricky to track down, but that helps narrow it down. This is *not* a Leo issue, but perhaps Leo's code can help me figure out what's going on. Rob... On Thursday, November 1, 2018 at 10:46:03 AM UTC-4, Edward K. Ream wrote: > > On Fri, Oct 19, 2018 at 4:34

The "skeleton" branch contains recent work on LeoWapp

I am switching to a new branch because of some strange interaction with the leowapp.py plugin and .leo files. Given the nature of the work, I probably should have done this sooner. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

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: File changes outside of Leo

On Fri, Oct 19, 2018 at 4:34 PM Rob wrote: So, two questions for the Leo gurus: > >1. What does Leo `see` in the files that triggers the message and the >dialog? > > Iirc, Leo looks at the actual modification dates. This is done at idle time. For all the details, see the

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: Proposal: eliminate --script and --script-window command-line options

On Thursday, November 1, 2018 at 2:29:27 AM UTC-5, Edward K. Ream wrote: I was shocked yesterday by how baroque Leo's --script logic is > Part of this complexity arises from a failure to refactor code. Yesterday I added the app.createBrowserGui. It took much longer than expected due to logic

Proposal: eliminate Leo's run-unit-tests externally commands

If we can eliminate --script, we probably can also eliminate Leo's various commands that execute unit tests in a separate process. This page tells how to run unit tests externally using Leo's bridge. Note in

Proposal: eliminate --script and --script-window command-line options

Don't panic. This is only a proposal. I was shocked yesterday by how baroque Leo's --script logic is, and further surprised about how much easier it is to bypass --script with an external python script that uses Leo's bridge. Btw, this page