QtWebEngine/WorkShop 2016 January: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Kkoehne moved page QtWebEngine - WorkShop 2016 January to QtWebEngine/WorkShop 2016 January: Let's centralize all pages about webengine as subpages under QtWebEngine) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 9: | Line 9: | ||
* Work to be done on 5.7 | * 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 | |||
Latest revision as of 09:19, 12 September 2017
Topics:
- Ways of working
- Suggestion: Drop trello, leverage https://bugreports.qt.io/secure/RapidBoard.jspa?rapidView=16
- Documentation
- 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