Qt contributors summit 2018 Program: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 114: Line 114:
''Ville Voutilainen''
''Ville Voutilainen''


Discussion on how we could and should leverage capabilities of C++14 and C++17 in Qt framework - considering possibility of setting C++17 as the minimum compiler requirement for Qt 6. Look into areas where we can provide interoperability between Qt types and C++ standards types (especially as we can have a binary break with a major version of Qt). Identifying possible items to help improving performance (e.g. allocators), adding functionality and reducing maintenance load.  
Discussion on how we could and should leverage capabilities of C++14 and C++17 in Qt framework - considering possibility of setting C++17 as the minimum compiler requirement for Qt 6. Look into areas where we can provide interoperability between Qt types and C++ standards types (especially as we can have a binary break with a major version of Qt). Identifying possible items to help improving performance (e.g. allocators), adding functionality and reducing maintenance load. What about upcoming C++20?


=== Plenary: Topic? ===
=== Plenary: Topic? ===

Revision as of 06:52, 29 May 2018

Back to Qt contributors summit 2018

Table of topics

Please add a longer session description with topic owner in the lower part of the page!

Day 1

Time Room 1 Room 2 Room 3
9:00 - 10:00 Keynote: Path towards Qt 6
10:00 - 11:00 A B C
11:00 - 12:00 Qt 3D Studio Runtime and APIs, 2.0 and beyond B C
12:00 - 13:00 Lunch
13:00 - 14:00 Plenary session: Graphics vision 2020
14:00 - 15:00 Dates, Times, Zones and Calendars C
15:00 - 16:00 A Qt for Python C
16:00 - 17:00 Plenary session: Overview of Qt 6 changes

Day 2

Time Room 1 Room 2 Room 3
9:00 - 10:00 Plenary session: Leveraging C++17
10:00 - 11:00 A B C
11:00 - 12:00 CI status and ruminations about flaky tests B C
12:00 - 13:00 Lunch
13:00 - 14:00 Plenary session: Topic?
14:00 - 15:00 A B C
15:00 - 16:00 A B C
16:00 - 17:00 Final session: Conclusions

Session descriptions

Please give a quick over-view and say who'll be getting the discussion going.

Keynote: Path towards Qt 6

Lars Knoll

Look into the currently ongoing development items in Qt and intended timeline and practicalities for development of Qt 6.

Plenary: Graphics Vision 2020

Various people

Towards a unified 2D-3D world. Let's discuss the direction for Qt Quick, the scenegraph, Qt 3D Studio with Qt 3D underneath, and the related tools like Qt 3D Studio and Qt Design Studio.

Plenary: Overview of Qt 6 changes

Lars Knoll

Summarizing the findings during the first day and previously identified needs for larger changes in various Qt modules.

Plenary: Leveraging C++17

Ville Voutilainen

Discussion on how we could and should leverage capabilities of C++14 and C++17 in Qt framework - considering possibility of setting C++17 as the minimum compiler requirement for Qt 6. Look into areas where we can provide interoperability between Qt types and C++ standards types (especially as we can have a binary break with a major version of Qt). Identifying possible items to help improving performance (e.g. allocators), adding functionality and reducing maintenance load. What about upcoming C++20?

Plenary: Topic?

Final session: Conclusions

Lars Knoll, Tuukka Turunen

Summarizing the findings during the summit.

Qt 3D Studio Runtime and APIs, 2.0 and beyond

Laszlo Agocs, Andy Nichols

Let's take a look at what ships in Qt 3D Studio 2.0 when it comes to C++ and QML APIs, and how these - and the underlying engine - will evolve in H2/2018 and beyond. Also serves as an intro to the Graphics Vision session that follows afterwards.

CI status and ruminations about flaky tests

Ville Voutilainen

Brief look at what the CI task force has done, with focus on flaky tests, how to find them, and what to do about them going forward.

Qt for Python

Cristián Maureira-Fredes

The technical preview of this new project is almost here, and we would like to give a brief overview of Qt for Python. We are focusing this discussion on a couple of crucial points of the current and future development aspects.

  • Code generation,
  • API compatibility (Qt and Python),
  • Features,
  • etc

Dates, Times, Zones and Calendars

Edward Welbourne

C++20 is slated to build, on std::'s <chrono>, a coherent (and well-designed) date/time system that does time-zones well and supports a way of doing calendars. We have a QAbstractCalendar contribution in the pipe-line.

  • What becomes of that, QTimeZone and Q(Date|Time)+ once (most of a decade from now) Qt is able to use C++20's shiny new library features ?
  • What should we do for Qt6 to prepare the way for that future transition ?