This morning I fixed up my GUI plugins to use leoQt:
nodetags
nodewatch
printing
sftp
The following plugins still have PyQt4 specific imports:
attrib_edit
nav_qt
notebook
projectwizard
stickynotes
screen_capture
ctagscompleter
screencasts
screenshots
richtext
threadutil
codewisecompleter
bzr_qcommands
quickMove
stickynotes_plus
active_path
backlink
ftp
leomylyn
leoscreen
bigdash
Of particular interest are /nav_qt/ and /stickynotes/, both of which are
*enabled by default* in leoSettings.leo -- making a bad user experience
for PyQt5 users out of the box. Those two plugins at least should be
fixed up soon, before we can start suggesting users try Leo with PyQt5.
Also, backlink.py at least has a huge amount of Tkinter code, which can
likely be excised ;)
Dufriz, if you disable all of the above plugins, Leo *should* load for
you in PyQt5. YMMV, though ;)
Hope this helps,
-->Jake
On 8/10/2014 9:55 AM, Edward K. Ream wrote:
On Sun, Aug 10, 2014 at 6:06 AM, Dufriz <[email protected]> wrote:
I just want to report that I installed Python 3.4.1 and PyQt5
(PyQt5-5.3.1-gpl-Py3.4-Qt5.3.1-x64) on Windows 8.1, to try Leo on it.
Leo starts with no problems but there is a list of error messages in the
background log windows as well as in Leo's own log pane, caused by the fact
that the PyQt4 module is not found.
Thanks for this report. Plugins should use the leo.core.leoQt module.
I thought there was an @file leoQt.py node in LeoPyRef.leo, but there
wasn't, so I just now pushed it.
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
