QtWebEngine/WorkShop 2016 January: Difference between revisions
Jump to navigation
Jump to search
(Raise questions regarding QtWebKit - QtWebEngine swtich) |
(Added Memory Optimizations) |
||
| Line 14: | Line 14: | ||
** What about performance and memory? Is it a problem for developers? | ** What about performance and memory? Is it a problem for developers? | ||
** What about QtAssistant? Is there any plan to use QtWebEngine in QtAssistant? What are the blockers? | ** What about QtAssistant? Is there any plan to use QtWebEngine in QtAssistant? What are the blockers? | ||
* Memory Optimizations: Is there anything we can do to safe memory on constrained devices? | |||
Revision as of 13: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 QtWebKit instead of QtWebEngine?
- 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 QtAssistant? Is there any plan to use QtWebEngine in QtAssistant? What are the blockers?
- Memory Optimizations: Is there anything we can do to safe memory on constrained devices?