Qt contributors summit 2017 Program

From Qt Wiki
Revision as of 12:09, 22 August 2017 by Peppe (talk | contribs) (More talks)
Jump to navigation Jump to search

Back to Qt contributors summit 2017

Monday 9.10.2017

Time bcc A level lobby
9.00 - 9.30 Registration
9.30 - 10.15 Welcome session and planning
Time Room A3 Room A4 Room A5 Room A6
10:30 - 11:20
11:30 - 12:20
12:20 - 13:20  Lunch!  Lunch!  Lunch!  Lunch!
13:20 - 14:10 Textures in QQ2
14:20 - 15:10 Qt Core discussion
15:20 - 16:10 The road towards Qt 6 (part 1)
16:20 - 17:10 The road towards Qt 6 (part 2)

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
10:00 - 10:50
11:00 - 11:50 Qt CoAP protocol
12:00 - 12:50
13:00 - 13:50  Lunch!  Lunch!
14:00 - 14:50
15:00 - 15:50 BOF Qt OpcUa
16:00 - 16:50
17:00 - 17:15 Thank you!

Session descriptions for Monday

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.

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


Session descriptions for Tuesday

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?

Qt 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.

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