Qt contributors summit 2017 Program

Back to Qt contributors summit 2017

Monday 9.10.2017

Please add your name and session description in the lower part of the page!

Time	bcc A level lobby
9.00 - 9.30	Registration
9.30 - 10.15	Welcome session and planning

Time	Room A3/A4	Room A5/A6	Room A8
10:30 - 11:20	Qt Core discussion
11:30 - 12:20	3D (Qt 3D Studio, Qt 3D)	Deployment Challenges with QtQuick.Controls(2) applications	QtNetwork and IOT
12:20 - 13:20	Lunch!	Lunch!	Lunch!
13:20 - 14:10	Textures in QQ2	wiki.qt.io maintenance	Code Model & Refactoring
14:20 - 15:10		Open governance and Jira practices	Releasing
15:20 - 16:10	Qt Wayland
16:20 - 17:10

Tuesday 10.10.2017

On Tuesday we will have limited rooms. Enough space, but not so many rooms.

Time	Room 1	Room 2
9:00 - 9:50	C++17, C++20 and beyond	BOF Build Systems
10:00 - 10:50	Qt6 containers discussion	Discuss Qt Logging enhancements
11:00 - 11:50	DTLS & CoAP protocol	Debugging QtWebEngine
12:00 - 12:50	New QML compiler infrastructure	CI
13:00 - 13:50	Lunch!	Lunch!
14:00 - 14:50	Pretty Printing With Qt Creator	BOF Navigation API in QtLocation
15:00 - 15:50	Open-source AR with Qt	BOF Qt OpcUa
16:00 - 16:50	Summing up framework changes: The road towards Qt 6	Qt examples guidelines discussion
17:00 - 17:15	Thank you!

Session descriptions for Monday

QtCore discussion

Thiago Macieira

Review of latest changes and planning for upcoming work, including preparation for Qt 6 (other than containers). Ideas:

• hashing function update; expanding the hash seed to 64- or 128-bit
• trimmed()/left()/right() vs trim()/truncate()/chop()
• QRandomGenerator and providing a PRNG of good quality (Mersenne Twister or Chacha20)
• QIODevice for Qt 6

3D

Laszlo Agocs & others

Let's discuss the 3D story.

Improving texture support in Qt Quick

Giuseppe D'Angelo

Qt Quick offers an extremely limited support for using non-RGB(A) textures, such as compressed texture formats and/or prebaked atlases. See the discussion and the subtasks of https://bugreports.qt.io/browse/QTBUG-59855 for a discussion.

Qt wiki (wiki.qt.io) maintenance

Tero Kojo

How do we make the wiki more useful to everyone? The basics are there, and in the past wiki weeks helped boost the place, but they are not a long term solution. Also moderation needs to be discussed, we have to have it in place because of spam, but we need a bigger moderation team, so that edits don't get stuck for several days.

Notes

Open governance and Jira practices

Santtu Ahonen

How we use Jira public projects, Epics, User stories and Tasks & Bugs to track and share work targets? As far as I can tell there seems to be project specific practices and if nothing else the discussion is about sharing those practices (e.g. why we use so many Epics instead of User Stories?) and see if there is some parts where we could or should align (e.g. how to mark fixtarget releases?). This links in to The Qt Company internal use and practices for Jira use, we cannot plan our own internal Jira usage in vacuum without the contributors.

Releasing

Jani Heikkinen

Open discussion related to Releasing.

Notes

QtNetwork and IOT

QtCore and Network team

Ideas/topics to discuss:

• HTTP server
  • Present status
  • Present scope
  • Use cases?
• Protocol support (HTTP / HTTPS / WebSockets / Secure WebSockets / CoAP?)
• CoAP
  • DTLS support (who can / will do what?)
• MQTT
• ZeroMQ
• Lack of reviews
• Permanent storage for network?

Notes

Deployment Challenges with QtQuick.Controls(2) applications

Nils Jeisecke

This session should focus on the deployment challenges on platforms where Qt usually has to be part of the distributed application package (Windows, Mac).

QtQuick.Controls2 comes with a huge amount of qml files that somehow have to be handled by an installer (on Windows at least, on Mac it's all in the bundle).

• Problems with the current approach
• Simplification options for packaging (could the resource system be used?)
• Handling of precompiled modules (qmlc,jsc)
• Improvement of the documentation

Notes

Code Model and Refactoring

Marco Bubke

Many IDEs like KDevelop or Qt Creator are now based on Clang which provides much better insight in the source code and new possibilities to transform code. This makes previously impossible takes possible and sometimes easy. What are the implications? What is the meaning of source code compatibility in this new context? What are the most effective ways to support the developer?

Notes

Session descriptions for Tuesday

Qt6 containers

Thiago Macieira

Discuss whether Qt 6 containers should:

1. be copy on write or not
2. build upon the C++ Standard Library containers or continue independent

Pretty Printing With Qt-Creator

Stéphane Petithomme

The Presentation is about So-ADE Debugger, a Qt-Creator plugin extension that allows to create custom Pretty Printer in few click for Qt-Creator. It comes with a few hundreds pre-configured Pretty Printers (Boost Library, Qt, Library, Std Library, Verific Library,.. ). During the session you will learn how to customize existing Pretty Printers and create you own one to greatly improve your productivity. I am very interested about feed back and comment to further improve the plugin, which will be make open source by the conference.

BOF Qt OpcUa

Frank Meerkötter

A quick get together for people interested in OPC UA. I'd like to hear about your use-cases for Qt OPC UA. I'd also like to discuss the pros/cons of having a Qt-based implementation at all. Is there mostly interest in a C++ API? What about a QML API? What parts of OPC UA are used in the field? How to get the existing Qt OpcUa based code base off the ground? Is the approach of wrapping an existing implementation sane? Do we wrap the right implementation? Would it be a way forward to build on top of open62541?

Navigation API in QtLocation

Paolo Angelelli

Discussion about the requirements and current WIP design of the Navigation API extension to the QtLocation module. Let's use this opportunity to also discuss other missing top level functionalities of the module (AR View, street level view, map matching API, indoor mapping and routing API extensions, etc.)

DTLS & CoAP protocol

Adrien Leravat

We are contributing a CoAP protocol module for Qt, and would like to hear your inputs regarding current implementation and API. CoAP is a protocol similar to HTTP used in IoT contexts. I will explain a few use case, current status of contribution, and what's to be expected next. We can then have a look at the API and how it is designed to discuss openly these aspects.

Debugging QtWebEngine

Viktor Engelmann

One of the main obstacles in working on QtWebEngine is the ability to debug it. I will show how to overcome common problems: how to get all debug symbols, how to find your way through the many files and directories, how to step through and trace back the program flow beyond the boundaries of the threads and processes.

Open-source AR with Qt

Martin Voelkle and Stéphane Magnenat

We will present a fully-functional augmented-reality solution using natural marker images, building on Qt 5 and OpenCV. Our solution uses state-of-the-art algorithms but is not yet as fast as competing closed-source products such as Vuforia. We will present the design choices, the architecture, the Qt integration, and discuss challenges and potential improvements. A demo will conclude the presentation.

CI

Tony Sarajärvi

Open discussion related to the change from VMware to openNebula, the new infrastructure, flakiness of the system and a good amount of Q&A.

New QML Compiler infrastructure

Lars Knoll

Overview over the new QML byte code interpreter and compiler infrastructure, as well as discussions on how to move to a full tracing JIT in the longer term

Build Systems BOF

Kai Köhne

Open discussion about Qt & the different build systems.

C++17, C++20 and beyond

Ville Voutilainen

A presentation about what's in C++17 and what is forthcoming in C++20 and future standards.

Discuss Qt Logging enhancements

Arnaud Clère

Qt-based devices such as Medical Cyber-Physical Systems could be developed, verified and validated more efficiently using structured logs. We suggest Qt Logging enhancements that would facilitate both human exploration and automated analysis with Python or other tools. The session will allow gathering your feedback, examining which enhancements would be useful to Qt, and how to contribute them.

Summing up framework changes: The road towards Qt 6

Lars Knoll

Sum up the findings from the last two days. What kind of changes do we need to do in the Qt Frameworks in the mid to long term. How can those be implemented within Qt 5 and which ones will have to wait until an eventual Qt 6.

Next topic

Name of owner

Short description. Two or three sentences that get the point across to the reader. Move this text forward, so there is an example for the next person editing.

Notes