Re: Updates to LeoVue

I guess this would be a question for Joe. I have gotten Leo Vue to "work" under heroku. The application serves a page that is identical to a page served by the local application. But it won't display the page. https://agile-fortress-75552.herokuapp.com/ As you know a lot more about node.js

Leo as a web app.

Here's a Dockerfile that let's Leo (The Python3 / PyQt4 version) run in a web browser. This is cheating, and I think I demoed this years ago without Docker, but it might be useful for someone. Would be interested to hear if anyone tries it / runs in to issues. Easier to understand if you're

Re: About separate processes and threads

> > I am enjoying this. The real reason I wrote the original post was to get > some help in understanding processes, thread and servers. > > I'll interrupt my study to ask this rhetorical question. Why do I think this > hilarious cartoon applies to Leo's >

Re: Unit Testing Nodes

> I'm using 5.7 - perhaps I'll upgrade. I assume myLeoSettings file will be > picked up? > Just as an aside, I have been running Leo via a git pull every time for three or four years now and have had to step back to an older commit only once or twice. Chris -- You received this message

Re: About separate processes and threads

Their was a book on Ada I bought a few decades ago that dealt with locks and other interprocess stuff. The author explained things by diagrams that had button, (push and pull), hatches and other things that illustrated how the various concepts worked in a graphical mechanistic fashion,

Re: About separate processes and threads

On Tue, Oct 16, 2018 at 8:55 AM Terry Brown wrote: > On Tue, 16 Oct 2018 04:36:31 -0700 (PDT) > "Edward K. Ream" wrote: > > > The original Dreaming Big Dreams thread suggested reorganizing Leo > > into more separable pieces, perhaps using a client/server > > architecture or other forms of

Re: Unit Testing Nodes

I'm using 5.7 - perhaps I'll upgrade. I assume myLeoSettings file will be picked up? (At home right now and the issue is on my work machine - will send you the info when I go to work). Thanks Vitalije for checking if the test works. At least now I know my approach will work. On Tuesday,

Re: About separate processes and threads

On Tue, 16 Oct 2018 04:36:31 -0700 (PDT) "Edward K. Ream" wrote: > The original Dreaming Big Dreams thread suggested reorganizing Leo > into more separable pieces, perhaps using a client/server > architecture or other forms of interprocess communication (IPC). Here's a presentation I just gave:

Re: Docker for LeoVue etc.

On Tue, 16 Oct 2018 05:46:00 -0500 "Edward K. Ream" wrote: > On Mon, Oct 15, 2018 at 3:23 PM Terry Brown > wrote: > > > Responding to Chris's comments re cPanel / LeoVue etc., just a PSA, > > Docker is easier and more useful than you think ;-) > > > > Thanks for this. Despite the work I did

About separate processes and threads

The original Dreaming Big Dreams thread suggested reorganizing Leo into more separable pieces, perhaps using a client/server architecture or other forms of interprocess communication (IPC). Here I'd like to present what little I know about IPC, servers and threads. The purpose is continue the

Re: Unit Testing Nodes

On Tuesday, October 16, 2018 at 12:30:22 PM UTC+2, Edward K. Ream wrote: > > > > On Tue, Oct 16, 2018 at 4:55 AM vitalije > > wrote: > >> How very strange. >> > > Yes, it's a mystery. anlifer, what appears in your log window when you > start Leo? This may be an installation-related problem.

Re: Leo options if file on disk gets updated?

On Mon, Oct 1, 2018 at 9:37 AM jkn wrote: My apologies for the delay in responding. 4) Separately, > touch mytest.leo > > 5) Change back to Leo. > nothing shown(!) > Leo doesn't continually check to see whether a .leo file has been changed. The workaround is not to do that. You could

Re: Docker for LeoVue etc.

On Mon, Oct 15, 2018 at 3:23 PM Terry Brown wrote: > Responding to Chris's comments re cPanel / LeoVue etc., just a PSA, > Docker is easier and more useful than you think ;-) > Thanks for this. Despite the work I did on #735 (how to install and run LeoVue)

Re: Unit Testing Nodes

On Tue, Oct 16, 2018 at 4:55 AM vitalije wrote: > How very strange. > Yes, it's a mystery. anlifer, what appears in your log window when you start Leo? This may be an installation-related problem. > I recall that Edward recently has added some code to make output from the > console to appear

Re: Unit Testing Nodes

Running all unit tests locally on the above Leo file(see previous message), on my machine produces following output: F == FAIL: runTest (leo.core.leoTest.GeneralTestCase) @test factorial

Re: Unit Testing Nodes

How very strange. I recall that Edward recently has added some code to make output from the console to appear in the Log pane. I don't know if that has something to do with your issue. ... I have just updated my Leo to the latest version and it works as expected. Attached to this message is