Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

QtWebEngine/WorkShop 2019 March: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
When: 2019-03-19 - 2019-03-20
When: 2019-03-19 - 2019-03-20


Agenda / Things to discuss
Agenda
== Agenda ==
 
=== Tuesday ===
 
* Qt 5.13 API Review
* Qt 5.13 API Review
* [[QtWebEngine/UseCases|WebEngine Use Cases]]
* Qt 5.14 planning
* Qt 5.14 planning
* Qt 6 planning
** API for Client Certificate in QML
** See also [https://bugreports.qt.io/browse/QTBUG-63235 QTBUG-63235]
** Add WebEngineDownloadItem::url
* Printing API
 
* New Chromium Update (73)
 
* Quick Popup Window
 
* Autotests
** Policy?
** In particular, download tests
 
=== Wednesday ===
 
* Qt 6 planning - See also [https://bugreports.qt.io/browse/QTBUG-63235 QTBUG-63235]
** Module / Library Names?
** Module / Library Names?
** Print API cleanup
** Print API cleanup
* WebEngine Use Cases
** setUrlRequestInterceptor should use std::function?
* Misc
* Backlog grooming
** MSVC / Clang
 
=== Summary ===
 
What to do better next time?
* Breakout sessions
** Tuesday afternoon was not too well used
** 'Call for ideas' earlier on
 
* Backlog grooming
** Good to have an overview! But too long (exhausting)
** Split up by domains
** Do more regularly anyway?

Latest revision as of 09:29, 21 March 2019

When: 2019-03-19 - 2019-03-20

Agenda

Agenda

Tuesday

  • Qt 5.13 API Review
  • Qt 5.14 planning
    • API for Client Certificate in QML
    • Add WebEngineDownloadItem::url
  • Printing API
  • New Chromium Update (73)
  • Quick Popup Window
  • Autotests
    • Policy?
    • In particular, download tests

Wednesday

  • Qt 6 planning - See also QTBUG-63235
    • Module / Library Names?
    • Print API cleanup
    • setUrlRequestInterceptor should use std::function?
  • Backlog grooming

Summary

What to do better next time?

  • Breakout sessions
    • Tuesday afternoon was not too well used
    • 'Call for ideas' earlier on
  • Backlog grooming
    • Good to have an overview! But too long (exhausting)
    • Split up by domains
    • Do more regularly anyway?