Re: Pyenchant does *not* work for Windows 64-bit systems

[Edward K. Ream]

On Mon, Feb 5, 2018 at 3:28 PM, lewis  wrote:

> Maybe that was me? I may have assumed the Win64 problems only affected
> pyenchant
>
>
2.0
>

​Well, I really don't remember, and it doesn't matter :-)

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: Pyenchant does *not* work for Windows 64-bit systems

[lewis]

Maybe that was me? I may have assumed the Win64 problems only affected 
pyenchant 2.0

Lewis 

On Monday, February 5, 2018 at 11:40:27 PM UTC+11, Edward K. Ream wrote:
>
> Contrary to a recent assertion, there seems to be no way to get pyenchant 
> working on Windows 64-bit systems.
>
> See pyenchant issue 42,  and 
> a related conda issue 
> . It looks like 
> lots of people are unhappy about this, including me.
>

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

Improvements to the VR and VR2 plugins

[Edward K. Ream]

Rev 7591d02 partially fixes #643 
: phonon/movie 
playback does not work with PyQt 5.6. The new code plays .mp3 files, but 
because of a Qt bug does not play .mp4 files(!) This kind of thing does not 
inspire confidence in Qt...

In addition, the VR2 plugin always loads, even if docutils can not be 
loaded.

#643 will remain open pending the resolution of the Qt bug.  There is no 
milestone for the remainder of the bug.

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.

Work flow re issues

[Edward K. Ream]

The convention that the first comment of an issue should be edited freely 
to keep it up to date has been a spectacular success.  Imo, it has 
increased my energy level significantly.

There are two more improvements that come to mind:

1. Backup.

Some issues have first comments that represent a significant amount of 
work.  I shall be making backup entries, probably in LeoDocs.leo, to ensure 
that editing blunders don't lose data permanently.

2. Editing discussions within issues.

It is natural to respond via email to discussions, but the GitHub issue 
tracker doesn't handle such threads very well.  Markdown is not supported 
in email replies, and email replies look worse than other comments.

The solution is to edit threads within issues.  I have just done so for Summary 
of installing zerorpc on Windows 
.  I like the result. 
The Q is short and clear.  Don't panic: Your email client will retain the 
entire conversation, should you ever want it, which is highly unlikely ;-)

Imo, it's best to make the edits in the comment that started a thread. That 
way the OP will be retained and markdown can be used. 

In future I will edit all important issue conversations.  Feel free to make 
edits yourself.

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: Distribute only 64-bit executables?

[Edward K. Ream]

On Monday, February 5, 2018 at 11:22:30 AM UTC-6, Edward K. Ream wrote:

> 1. Every distribution option doubles the amount of testing required for a 
release. 

The following does indeed work when invoked in a python 3 interpreter, but 
maybe only on 64-bit systems:

import PyQt5.QtCore as C
import PyQt5.QtMultimedia as M
import os, sys
app=C.QCoreApplication(sys.argv)
path = 'c:/users/edreamleo/GayaneBalletSuite.mp3'
assert os.path.exists(path), repr(path)
url= C.QUrl.fromLocalFile(path)
content= M.QMediaContent(url)
player = M.QMediaPlayer()
player.setMedia(content)
player.play() 

The following works from within Leo:

import PyQt5.QtCore as C
import PyQt5.QtMultimedia as M
import os
path = 'c:/users/edreamleo/GayaneBalletSuite.mp3'
assert os.path.exists(path), repr(path)
url= C.QUrl.fromLocalFile(path)
content= M.QMediaContent(url)
player = M.QMediaPlayer()
player.setMedia(content)
g.app.permanentScriptDict['player'] = player # <--- new
player.play()

*Important*: a reference to the player must be retained, as shown in the 
penultimate line.

This is today's new idea, so maybe the new code *would *work on a 32-bit 
system.  But I don't want to test everything twice ;-)

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.

Distribute only 64-bit executables?

[Edward K. Ream]

I am thinking of installing only 64-bit software on my Windows machine, and 
to release only 64-bit pyinstaller builds.  Here are my thoughts:

1. Every distribution option doubles the amount of testing required for a 
release.  In practice, not all options are tested.

2. Afaik, pyenchant is the only package requiring a 32-bit build. The tail 
is wagging the dog.

3. True, 32-bit builds should run on 64-bit machines, so 32-bit builds 
should be more portable.  But I have my doubts.

Your comments, please.

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: ENB: Installation plans

[Edward K. Ream]

On Mon, Feb 5, 2018 at 10:55 AM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:


The first thing I installed was an installer (Scoop[1]) and a package
> installer (Chocolatey[2]).
>


> [1] http://scoop.sh/
> [2] http://chocolatey.org/
>

​Thanks for this. Your timing is excellent.  Matt, do you have any thoughts?

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: ENB: Installation plans

[Terry Brown]

On Mon, 5 Feb 2018 11:55:04 -0500
Offray Vladimir Luna Cárdenas  wrote:

> [1] http://scoop.sh/
> [2] http://chocolatey.org/

There's also https://ninite.com/ for a more GUI based approach.  Would
be nice to get Leo in there alongside Notepad++, Eclipse, etc.

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: ENB: Installation plans

[Offray Vladimir Luna Cárdenas]

Hi,

I don't use in my machines since Windows since 1999, and if I have to
buy a computer with it (which is the default) one of the first things I
do is to erase Windows and replace it with (Manjaro) Gnu/Linux. But my
sister recently bought a Windows laptop and she need to run some
(government provided!) software for her work, which only runs on
Windows. So I started to assist her on installing this machine with the
programs she was used to on Linux. The first thing I installed was an
installer (Scoop[1]) and a package installer (Chocolatey[2]). After
that, all installations are just one command away of distance, without
worrying too much. Scoop and Chocolatey have important diferences, but I
think that a Leo package could be created for that systems, so Leo
installation on windows becomes just a one liner.

[1] http://scoop.sh/
[2] http://chocolatey.org/

Hope it helps,

Offray



On 04/02/18 12:31, Edward K. Ream wrote:
> This is an Engineering Notebook post.  There are some questions
> below.  Any advice from Terry, Matt or others will be welcome.
>
> In the last two days I've lost my fear of multiple installations. 
> Here are my plans:
>
> *Windows 10*
>
> 1. Replace 32-bit miniconda with 64-bit miniconda.  This may solve
> some npm and pyinstaller problems.
>
> 2. (Maybe) Install a full 64-bit Python 3 Anaconda /in addition to/
> (or instead of??) the miniconda environments.
>
> I am considering using Anaconda because of an annoying problem. 
> Starting a new console starts off in the /default/ miniconda
> environment.  Alas, activate python3, which at present gets done
> automatically when opening a new console, takes about two seconds. 
> This delay quickly becomes unbearable.
>
> So the idea is that opening a console will put me in the full Anaconda
> environment, not the miniconda environments.
>
> Or maybe the full Anaconda environment is enough, and I can use conda
> to create new environments??
>
> *Ubuntu*
>
> I'll wait until I have the Windows install resolved before
> experimenting on Linux.
>
> I do know enough not to touch the system install of Python ;-)
>
> At present I have 64-bit Anaconda installed for both Python 2 and 3.
>
> *Summary*
>
> All comments and suggestions are welcome.
>
> I am happy to delay Leo 5.7b2 until all these issues are resolved.
>
> 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.

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

hello world with zerorpc now runs on windows

[Edward K. Ream]

This is a significant milestone.

The info item #701: Summary of installing zerorpc on Windows 
 tells how to install 
both the python and node.js versions zerorpc.  It's not trivial. The trick 
is to do `npm install --global --production --windows-build-tools` which 
installs a free copy of Visual C++ Build Tools 2015! *Note*: This must be 
done in PowerShell with admin privileges.

This issue also explains how to run a demo with a "Hello World" demo with a 
python server and a javascript client. These now work!

The enhancement item #684: Create a browser gui for Leo 
 contains the demo 
mentioned above, as well as the converse demo: a javascript server and a 
python client.  I haven't tried this other demo script, but I expect no 
particular difficulties.

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: Pyenchant does *not* work for Windows 64-bit systems

[Edward K. Ream]

On Monday, February 5, 2018 at 7:19:56 AM UTC-6, Edward K. Ream wrote:

> it may be time to look at nltk , a natural language 
tool kit for python.

I have just created #700: create a spell checker based on nitk 
. It has a 5.8 
milestone, but it may happen for 5.7b2.

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: Pyenchant does *not* work for Windows 64-bit systems

[Edward K. Ream]

On Monday, February 5, 2018 at 6:40:27 AM UTC-6, Edward K. Ream wrote:
>
> Contrary to a recent assertion, there seems to be no way to get pyenchant 
> working on Windows 64-bit systems.
>

I think it may be time to look at nltk , a natural 
language tool kit for python.

This stack overflow question 
 
asks how to create a spell checker based on nltk. The answer references this 
page . I think it may be time to 
abandon pyenchant.

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.

Pyenchant does *not* work for Windows 64-bit systems

[Edward K. Ream]

Contrary to a recent assertion, there seems to be no way to get pyenchant 
working on Windows 64-bit systems.

See pyenchant issue 42,  and a 
related 
conda issue . It 
looks like lots of people are unhappy about this, including me.

At present, I am using a 64-bit Anaconda3 system, with python2 and python3 
environments.  This complicates Leo's distribution problems considerably, 
for several reasons:

1.  I have no way of spell checking LeoDocs.leo!  I suppose I could do the 
checking on Linux...

2. I don't see any way of getting pyinstaller to create a distro that 
includes pyenchant.

I suppose I could install an Anaconda/miniconda 32-bit system to solve #1.  
That might also solve #2, but I'm thinking it may cause further problems 
for Matt.

Any thoughts?

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.