Re: Docker for LeoVue etc.

[Edward K. Ream]

On Tue, Oct 16, 2018 at 8:49 AM Terry Brown  wrote:

> It would be best to make a Docker image for Leo, but running GUI
> > apps. is
>
> I'm not sure why I wrote "best", I probably meant to say "easy".
>

My bad.  You actually wrote "east", and I turned that into "best".

I'm wondering though if I can add Leo to a container running Apache
> Guacamole, making Leo a containerized web app., probably more of a
> novelty than anything.
>

I encourage all such experiments.  This is the year I come up to speed on
web technologies.

Never heard of Guacamole until now. The front page
 explains what a "clientless remote desktop
gateway" means:

- We call it *clientless* because no plugins or client software are
required.
- Guacamole client is an HTML5 web application...
  As long as you have access to a web browser, you have access to your
machines.
- Desktops accessed through Guacamole need not physically exist.

So in this context the software acts as a "gateway" to machines and/or
operating systems. The video on the front page shows multiple machines
being accessed from whatever machine is running the browser.  Right? It's
pretty nifty.

The downloads page says:

"Apache Guacamole is split into two subprojects: "guacamole-client", the
HTML5 web application which serves the Guacamole client to users, and
"guacamole-server", the remote desktop proxy which the web application
communicates with."

I assume that a machine must be running the guacamole server to be
accessible via the client.

Edward

-- 
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.

Re: Supporting pytest

[Edward K. Ream]

On Sunday, October 14, 2018 at 9:56:52 AM UTC-5, Edward K. Ream wrote:

We should decide where tests belong.
>

For testing, I have added two top-level test functions to leoApp.py:

def test1():
assert True

def test2():
assert False

Running tests on explicit files does work as expected

c:\leo.repo\leo-editor\leo\core>pytest leoApp.py

or

c:\leo.repo\leo-editor\leo>pytest core\leoApp.py

or

c:\leo.repo\leo-editor\leo>pytest core\leoApp.py::test1

However, I have not figured out how to run tests on all leo*.py files in 
the leo folder.  There are .ini settings and/or command-line options that 
supposedly do this, but I have not been able to get them to work on 
Windows.  I'll investigate on Linux.

Anybody have any suggestions?

Edward

-- 
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.

Re: Supporting pytest

[Edward K. Ream]

On Wednesday, October 17, 2018 at 6:07:28 AM UTC-5, Edward K. Ream wrote:

> ​However, I have not figured out how to run tests on all leo*.py files in 
the leo folder. 

It appears that all tests must start with test_, at least in some 
situations.  (Yes, I know about -k, but haven't gotten that to work 
reliably).

I added the following top-level function to leoApp.py:

def third_test():
assert True

The following does *not* discover the test:

c:\leo.repo\leo-editor\leo>pytest core\leoApp.py::third_test

In short, the pytest options and command-line arguments seem way too 
finicky.  Any advice would be appreciated.

Edward

-- 
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.

Re: About separate processes and threads

[Edward K. Ream]

On Tue, Oct 16, 2018 at 4:07 PM vitalije  wrote:

I don't have much time to write right now, but here is a list of (IMHO)
> essential facts one should keep in mind when dealing with concurrency:
>

A great summary.  Many thanks for this.  I've bookmarked this reply and
will study the features you mention.

Imo, a client-server architecture is required when dealing with multiple
languages.  For example, Jupyter supports "kernels" in various languages.
Iirc all the infrastructure is in python and javascript, but kernels
can/must be written in other languages.

Edward

-- 
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.

Re: Docker for LeoVue etc.

[Terry Brown]

On Wed, 17 Oct 2018 03:30:46 -0500
"Edward K. Ream"  wrote:

> I assume that a machine must be running the guacamole server to be
> accessible via the client.
> 
> Edward

No, it needs to be running a remote access protocol like VNC
(vnc-server, not vnc-client) or RDP.  And it needs to be accessible to
a machine running the guacamole server network wise.  VNC/RDP is fairly
trivial to install, not true of guacamole.

So normally machine A is running the guacamole server, it can connect
to machines B, C, and D which are running VNC / RDP.  And someone
connects to A from E using a browser, and can then view B / C / D.

If you (a) had network connectivity from E to C, and (b) had vnc-client
software installed on E, you could access C from E without guacamole.
But (a) and (b) are often not true and (a) is sometimes insurmountable,
so guacamole is useful.

My Docker container makes A and B the same machine, running a VNC
server as well as guacamole.  Which is probably typical of people using
guacamole to access their personal desktops via the web, but guacamole
is designed to provide a gateway to whole offices / institutes of
machines, not just one.

Cheers -Terry

-- 
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.

Re: Leo options if file on disk gets updated?

[jkn]

Hi Edward

On Tuesday, October 16, 2018 at 11:55:15 AM UTC+1, Edward K. Ream wrote:
>
> 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 file an enhancement 
> request, but I would reject it ;-)
>
> Given that Leo does easily (via the menu) allow you to reload a file, I am 
curious what your reason for rejecting would be?

Thanks
jon

 

> Leo *does* warn you if you try to open two separate of the same .leo 
> file.  If you ignore the warning then you, and only you, are responsible 
> for what happens.
>
>  

> Edward
>

-- 
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.

Re: Updates to LeoVue

[Joe Orr]

Oops! I removed vue-tabs because there are tabs in bootstrap-vue. Forgot to 
remove a couple of includes. I just uploaded a fix.

Joe

On Monday, October 15, 2018 at 10:36:10 AM UTC-4, Chris George wrote:
>
> Ugh. The entire node/npm thing is a dog's breakfast. I have problems, as 
> usual.
>
> Linux Mint 18 KDE
> node v10.12.0
> npm 6.41
>
> Running npm run build or npm run dev gets me these errors. This was after 
> having to manually install a handful of dependencies that npm couldn't 
> satisfy.
>
> ERROR in ./src/main.js
> Module not found: Error: Can't resolve 'vue-nav-tabs' in 
> '/external/chris/working/Websites/leovue/src'
>  @ ./src/main.js 65:18-41
>
> ERROR in ./src/main.js
> Module not found: Error: Can't resolve 'vue-nav-tabs/themes/vue-tabs.scss' 
> in '/external/chris/working/Websites/leovue/src'
>  @ ./src/main.js 69:0-44
>
> Any hints or tips would be much appreciated.
>
> Chris
>
> On Sunday, October 14, 2018 at 4:34:17 PM UTC-7, Joe Orr wrote:
>>
>>
>>
>>>- clicking on "Feature Introduction" and "Chunking" items in ToC 
>>>starts a download of the .md file for that node. The other items seem to 
>>> be 
>>>okay
>>>
>>> That's weird, does it on FF in Mac too. But the page does display after 
>> you get rid of the download dialog. I'll look into it. For now I'm really 
>> only supporting Chrome though. 
>>
>>
>>>- there's no vertical scroll bar in the rendered pane, so without a 
>>>mouse wheel I can't see the whole page. PageDn doesn't work at first 
>>>because keyboard focus is in the pane that was clicked (ToC).
>>>
>>> I removed the scrollbars (but not scrolling) scrolling because they 
>> looked crappy in Windows. I could put them back as an option... Arrow keys 
>> should work, but with mouse wheel or track pad it works better.
>>
>>>
>>>- wow. just wow.
>>>
>>> Glad you like it! If you have any good sample files, you can try them 
>> out. All you need to do is put them online with an index file that points 
>> to the CDN.
>>
>>>
>>>- Install too complicated: yeah. I'm going to keep chipping away at 
>>>that.
>>>- Install and using LeoVue requires a webserver - maybe there's 
>>>something in Tiddly Desktop that can be adapted (
>>>https://tiddlywiki.com/static/TiddlyDesktop.html)
>>>
>>> LeoVue depends on Vue, which requires files to be served not from 
>> filesystem.
>>
>> Joe
>>  
>>
>

-- 
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.

Re: Updates to LeoVue

[Joe Orr]

On Tuesday, October 16, 2018 at 9:06:59 PM UTC-4, Chris George wrote:
>
> 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 etc. than me I was hoping you might 
> have an idea.
>
> A big stumbling block to get this working was the lack of a start script 
> in packages.json or a server.js file. I am slowly working towards it 
> working as I keep googling and tinkering but I have been stuck here for a 
> while.
>
>
> You copied the source files, not the compiled files. The source index.html 
doesn't load LeoVue, that is added by the build process.

Check this page out:
https://kaleguy.github.io/leovue/#/t/13/

Unless you're planning to edit the code in LeoVue you don't need the repo 
and you don't need node, you can just use the CDN. All you need is
1. webserver that serves static files, can use S3, GH-Pages etc
2. Index.html from dist or docs or exampes repo
3. Leo file

I'll add some instructions for running off of S3, but also easy thing to do 
if you don't want to use the CDN, create an empty git repo, copy the docs 
folder from LeoVue to the git repo, turn on GH-Pages for the docs folder, 
edit the Leo file as you like.

Joe 

-- 
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.

Re: Updates to LeoVue

[Chris George]

Well, that is just way too easy.

I guess I should have followed up on figuring out what a CDN was before I
went off trying to get the entire shooting match to work on Heroku.

On the plus side, I now know something about node.js and express.js that I
didn't know before. :-)


Chris

On Wed, Oct 17, 2018 at 3:10 PM Joe Orr  wrote:

>
>
> On Tuesday, October 16, 2018 at 9:06:59 PM UTC-4, Chris George wrote:
>>
>> 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 etc. than me I was hoping you might
>> have an idea.
>>
>> A big stumbling block to get this working was the lack of a start script
>> in packages.json or a server.js file. I am slowly working towards it
>> working as I keep googling and tinkering but I have been stuck here for a
>> while.
>>
>>
>> You copied the source files, not the compiled files. The source
> index.html doesn't load LeoVue, that is added by the build process.
>
> Check this page out:
> https://kaleguy.github.io/leovue/#/t/13/
>
> Unless you're planning to edit the code in LeoVue you don't need the repo
> and you don't need node, you can just use the CDN. All you need is
> 1. webserver that serves static files, can use S3, GH-Pages etc
> 2. Index.html from dist or docs or exampes repo
> 3. Leo file
>
> I'll add some instructions for running off of S3, but also easy thing to
> do if you don't want to use the CDN, create an empty git repo, copy the
> docs folder from LeoVue to the git repo, turn on GH-Pages for the docs
> folder, edit the Leo file as you like.
>
> Joe
>
> --
> 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.
>

-- 
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.