QtWebEngineRoadMap: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
(clean-up)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
''The project is still young, so we don’t have such a thing as a very clear roadmap, but here are the use cases we’ve identified and features we plan on looking into at one point or another:''
''The project is still young, so we don't have such a thing as a very clear roadmap, but here are the use cases we've identified and features we plan on looking into at one point or another:''


==Known/Foreseen use cases==
== Known/Foreseen use cases ==


* The usual Web Browser stuff (Embedded platforms, <span class="caps">KDE</span>…)
* The usual Web Browser stuff (Embedded platforms, KDE…)
* Presenting and integrating web contents (Hybrid apps, ported web apps…)
* Presenting and integrating web contents (Hybrid apps, ported web apps…)
* Headless testing and so on (think also <span class="caps">SVG</span> rendering/printing to pdf, etc)
* Headless testing and so on (think also SVG rendering/printing to pdf, etc)


==Features==
== Features ==


* Graphical integration, with QtQuick and Widgets, forwarding of events, etc
* Graphical integration, with QtQuick and Widgets, forwarding of events, etc
Line 19: Line 19:
** authentication
** authentication
** custom CAs
** custom CAs
* Extending access rights for apps.

Latest revision as of 13:11, 24 March 2016

The project is still young, so we don't have such a thing as a very clear roadmap, but here are the use cases we've identified and features we plan on looking into at one point or another:

Known/Foreseen use cases

  • The usual Web Browser stuff (Embedded platforms, KDE…)
  • Presenting and integrating web contents (Hybrid apps, ported web apps…)
  • Headless testing and so on (think also SVG rendering/printing to pdf, etc)

Features

  • Graphical integration, with QtQuick and Widgets, forwarding of events, etc
  • JS bridge of sort (exposing QObject to the JS context, invoking JS on the web contents side, etc)
  • Network integration. Unclear how to do it and to what extent it should integrate. Some of the common use cases
    • custom schemes
    • loading policies
    • proxy settings
    • cookies
    • disk cache
    • authentication
    • custom CAs