07-16-2016, 08:10 AM | #1 |
Connoisseur
Posts: 64
Karma: 10
Join Date: Sep 2015
Location: Yerevan, Armenia
Device: none
|
QT 5.7
Yesterday our programmers did tests to check if they can migrate to QT5.7 (Win64, MSVS 14 (Community 2015), QT 5.7, Python 3.6, Cmake 3.6)
We have some programs – not for sell, for internal use. Just for fun, I asked them to test if Sigil 0.9.6 is also ready. The answer was that it seems that it will be OK (with the help of info about porting - http://doc.qt.io/qt-5/qtwebenginewid...tingguide.html ), but partly only because of “QwebElement“ used in Sigil but unavailable in QT5.7. Of course, I can't ask them to do tests with changing the inner code of Sigil))) ---------- Spoiler:
--------- |
07-16-2016, 08:56 AM | #2 |
Grand Sorcerer
Posts: 27,465
Karma: 192992430
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
If porting Sigil's QtWebkit dependencies to QtWebEngine were trivial (or if trading QtWebKit's bugs/deficiencies for QtWebEngine's bugs/deficiencies resulted in an overall positive gain) we would have already done it.
That Cmake can successfully generate Sigil makefiles (or VS projects) with Qt5.7 is no guarantee that smooth sailing lies ahead. I know from personal experience that it doesn't! It makes far, far more sense to custom compile Qt5.6/7.x with QtWebKit added back in (which is fairly trivial--even on Windows) and use the time gained to determine if a port to QtWebEngine is feasible, or even wise in the long run. No modification to Sigil's code is necessary for that route. Last edited by DiapDealer; 07-16-2016 at 11:54 AM. |
Advert | |
|
Thread Tools | Search this Thread |
|