Qt contributors summit 2018 Program

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	Qt Widgets	Dates, Times, Zones and Calendars	Qt3D use cases in automotive and the problems with it
15:00 - 16:00	Qt Quick (and qml and controls)	B	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	Code Review Tool and Workflow	Qt for WebAssembly	C
11:00 - 12:00	CI status and ruminations about flaky tests	BOF Clang tooling and code model	Qt Wayland future directions
12:00 - 13:00	Lunch
13:00 - 14:00	Plenary session: Topic?
14:00 - 15:00	Pointer Handlers Update	B	C
15:00 - 15:30	A	Qt for Python	C
15:30 - 16:00	A	Jira/bugreports	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?

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 ?

Qt for WebAssembly

Morten Sørvig

The Qt for WebAssembly platform port is currently in Tech Preview and is scheduled for inclusion in Qt 5.12. In this session we'll discuss what the Qt support for this platform should look like.

Qt Widgets

Richard Gustavsen, Frederik Gladhorn, Gabriel de Dietrich

What is new with Qt Widgets, where do we need updates and development, are the styles up to date?

Whither QStyleSheetStyle in Qt 6?

Qt Quick

Frederik Gladhorn

What is the direction for QML, Qt Quick and Qt Quick Controls 2? Where do we have gaps and what is the most important goal to achieve?

Pointer Handlers Update

Shawn Rutledge

Discussion of how it has gone with the 5.10-5.11 Tech Preview and what is left to be done before transition to supported API in 5.12.

• Renaming: Gesture Handlers?
• Make sure API is sustainable
• Implement missing functionality
• Drag & Drop

Code Review Tool and Workflow

Frederik Gladhorn

We have been wanting to update Gerrit, but progress seems slow. Let's discuss our workflow and consider the pros and cons of other tools.

Qt3D use cases in automotive and the problems with it

Vladimir Minenko, Ilya Gluschenko, Nikita Krupitska, Volker Krause, others

There are a few typical cases for the use 3D in the automotive projects. Most of them are about visualisation of cars, parts of interior, dials and gauges in a retro styles. Assets for those 3D models are usually developed in 3rd party tools (like Maya or Blender) or even converted from CAD data, then composited in scene manually (for now, in absence of a released version of Qt 3D Studio). These use cases expose multiple problems or a lack of features in Q3D.

BOF Clang tooling and code model

Ivan Donchevskii

ClangCodeModel is finally the default code model starting with Qt Creator 4.7. Other Clang-based tooling is also on it's way. Let's discuss what is good, what requires polishing and what are we missing.

Jira/bugreports

Alex Blasche

Quite a few changes are ongoing to streamline Jira usage. This includes things like open requirements mgmt, automatic handling of "Need more info" bugs and general project adjustments. The session should also give opportunity to bring up personal issues from the audience which may have been creeping up.

Qt Wayland Future Directions

Johan Helsing

Let's discuss the future of Qt Wayland. Important topics: deprecation of old shells, client-side APIs, window decorations, important bugs, pain points with the current compositor API.