No Nuitka movement; QWebEngine mail; actually used ppqt2

No new info from Kay. Had hoped for a fresh shot at compiling Cobro, but nothing today.

After several days of silence on the QWebEngine email list, a Jocelyn Turcotte replied to my query about a timeline for missing function. Some of the reply is a bit disturbing.

You can find some of that information at: http://doc.qt.io/qt-5/qtwebenginewidgets-qtwebkitportingguide.html

Actually this porting guide raised some new questions. One that I passed back to her was this: According to a passing reference in its doc, QWebEnginePage is supposed to support a contextMenuEvent() method. However, QWebEnginePage derives from QObject, not QWidget. QObject doesn't have a contextMenuEvent(). QWidget does, but QWebEnginePage doesn't inherit from it. So it is not clear that it can actually support QEvent calls of any kind! At least, not using the normal QEvent overrides like contextMenuEvent or keystrokeEvent.

Some of the features like private browsing should already be available in Qt 5.5.

Good, but that's 6 months away. And -- which features are committed to that release?

We currently have an internal development board at https://trello.com/b/5G9c1rkb/qtwebengine that you can follow and you can use the Qt bug tracker to vote and report issues or missing important features.

I looked at at this "board"; it is not a proper forum but more a virtual corkboard where developers post "cards" with the tasks they are doing. No sorting or searching and no obvious place for comments.

I have to note that QtWebEngine isn't a 1-to-1 replacement of QtWebKit, principally because some very advanced features can't be set in stone through a public API without risking huge future maintenance efforts as Chromium evolves under our feet. It is quite a dragon to ride.
The public API aims at solving the general use case of embedding web contents in Qt applications, but if you are developing a more powerful application I encourage you to look at the code and dig further to get access to functionalities that you need, keeping in mind that the further you dig, the more likely you'll have to update your code between QtWebEngine updates.

Well, that remark provoked a quick reply from another user, expressing disappointment that QWebEngine was punting on being a complete Webkit replacement, leaving developers with a choice of a "more powerful" API that is frozen (doesn't support HTML5, for example) and a less-featured one that can't be used for anything sophisticated. (Supposing a custom context menu is sophisticated.)

And finally: there was a book I'd post-processed that got kicked back to me for minor fixes in October. I finally got around to finishing that, and I used ppqt2 to do the editing. Worked fine.