On Tue, May 3, 2016 at 9:55 AM, 'Terry Brown' via leo-editor < [email protected]> wrote:
> [sent this to a github issue discussion by mistake] > In general, I prefer that most discussions happen in public. Note: just posting thing for general qt4/5 import reference, I think > the WebKit related issues may be more about deprecation than imports. > > Just found this: > > https://github.com/spyder-ide/qtpy > > QtPy: Abtraction layer for PySide/PyQt4/PyQt5 > > QtPy (pronounced 'cutie pie') is a small abstraction layer that lets > you write applications using a single API call to either PyQt or > PySide. > It provides support for PyQt5, PyQt4 and PySide using the PyQt5 layout > (where the QtGui module has been split into QtGui and QtWidgets). > > Basically, you write your code as if you were using PyQt5 but import > Qt modules from qtpy instead of PyQt5. > The leo.core.leoQt module does the same thing. Adding another layer exposes Leo to bugs in that layer, and would add a dependency. Having said that, QtPy might serve as a reference. Edward P.S. Iirc, it doesn't seem like VR1, the original viewrendered plugin, should need to import QWebKit. If not, #281 <https://github.com/leo-editor/leo-editor/issues/281> may have some merit after all. EKR -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
