QtWebEngine/WorkShop 2016 January: Difference between revisions
Jump to navigation
Jump to search
(Added Memory Optimizations) |
m (Fix names of modules and tools) |
||
| Line 10: | Line 10: | ||
* Work to be done on 5.7 | * Work to be done on 5.7 | ||
* Why vendors/customers still use | * Why 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 | ** 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 safe memory on constrained devices? | ||
Revision as of 23:54, 10 February 2016
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 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 safe memory on constrained devices?