QtWebEngine/WorkShop 2016 January: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
m (Fix names of modules and tools)
m (Kkoehne moved page QtWebEngine - WorkShop 2016 January to QtWebEngine/WorkShop 2016 January: Let's centralize all pages about webengine as subpages under QtWebEngine)
 
(2 intermediate revisions by 2 users not shown)
Line 10: Line 10:
* Work to be done on 5.7
* Work to be done on 5.7


* Why vendors/customers still use Qt WebKit instead of Qt WebEngine?
* Why do vendors/customers still use Qt WebKit instead of Qt WebEngine?
** What is missing? Which missing features are the most important for the customers?
** What is missing? Which missing features are the most important for the customers?
** What about performance and memory? Is it a problem for developers?
** What about performance and memory? Is it a problem for developers?
** What about Qt Assistant? Is there any plan to use Qt WebEngine in Qt Assistant? What are the blockers?
** What about Qt Assistant? Is there any plan to use Qt WebEngine in Qt Assistant? What are the blockers?


* Memory Optimizations: Is there anything we can do to safe memory on constrained devices?
* Memory Optimizations: Is there anything we can do to save memory on constrained devices?
 
* CI & autotests
 
* Chromium updates

Latest revision as of 09:19, 12 September 2017

Topics:

  • WebEngine / SceneGraph integration
  • Features for 5.8
  • Work to be done on 5.7
  • Why do vendors/customers still use Qt WebKit instead of Qt WebEngine?
    • What is missing? Which missing features are the most important for the customers?
    • What about performance and memory? Is it a problem for developers?
    • What about Qt Assistant? Is there any plan to use Qt WebEngine in Qt Assistant? What are the blockers?
  • Memory Optimizations: Is there anything we can do to save memory on constrained devices?
  • CI & autotests
  • Chromium updates