Some of our applications are relying on Qt Script and Qt Webkit. So I just
had a look at the replacements (Qt Webengine and Qt QML).

The documentation says "... WebEngine ... doesn't give direct access to the
network stack and the HTML document through C++ APIs". 
Does this mean there is no way to access the DOM anymore? This would be
fatal for us. Accessing the DOM is essential for all of our applications
that use QWebView. Is there some replacement/workaround?

Also we use the QScriptEngineDebugger but there seems to be no debugger for
QJSEngine. Is there some replacement/workaround?

Are there other significant differences that I should consider?

-- 
Kind Regards
Bernhard Lindner

> -----Ursprüngliche Nachricht-----
> Von: development-bounces+private=bernhard-lindner...@qt-project.org
> [mailto:development-bounces+private=bernhard-lindner.de@qt-
> project.org] Im Auftrag von Knoll Lars
> Gesendet: Dienstag, 3. Februar 2015 08:34
> An: development@qt-project.org
> Betreff: [Development] Deprecating modules with 5.5
> 
> Hi,
> 
> I’d like to mark a few modules as deprecated with 5.5, and most likely
> remove them from the binary packages with 5.6. These modules are:
> 
> * Qt WebKit
> * Qt Declarative (Qt Quick 1)
> * Qt Script
> 
> All of these modules are by now a couple of years old, don’t receive
updates
> above the bare minimum and have a replacement that is actively being
> developed in Qt 5.
> 
> Cheers,
> Lars
> 
> _______________________________________________
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

<<attachment: winmail.dat>>

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to