View source for Qt Contributor Summit 2023 - Program

==Sessions==
Please, add your sessions/talks/presentations to the table below.

→ <small>'''If you have any issues while editing the page, please contact Pedro Bessa directly at pedro.bessa@qt.io'''</small>

Make sure to include a title, state your name, define its format, and write a short description.

'''Topic''': write a brief title for your topic of discussion.

'''Speaker''': Add the name of speaker(s) or session facilitator.

'''Format''': is it a discussion, presentation, workshop or something else?

'''Summary''': include here a brief summary of that is to be discussed.

It doesn't need to be a final version of what will be presented, but it's good to have an idea of the presentation's scope and general lines.<br />
{| class="wikitable"
|+
!Topic
!Speaker
!Format
!Summary
|-
|TaskTree
|Jarek Kobus
|Presentation
|The [https://doc-snapshots.qt.io/qtcreator-extending/taskingsolution-module.html TaskTree] can automatically manage the chain (or tree) of asynchronous tasks of mixed types.
The recipe on how to run the conglomerate of tasks is described in a declarative way in C++.

The recipes are enclosed in copyable value-type objects and may be run many times, or be part of more general recipes.

The TaskTree is currently broadly used in QtCreator, e.g. for executing Locator filter, Clang tool, Autotests, and much more...

The TaskTree's implementation is [Https://github.com/qt-creator/qt-creator/tree/master/src/libs/solutions/tasking separated from the QtCreator specific code] and may already serve as a general purpose solution outside of QtCreator.
|-
|Qt - Connected First
|Vladimir Minenko
|Discussion (with some presentations)
|Since a while there are multiple additions to Qt wthattarget more efficient development of apps talking to different web services as well as implementing distributed architectures. As of July 2023, it ranges from the new [https://doc.qt.io/qt-6/qtgrpc-index.html Qt gRPC] module and the "revived" [https://doc.qt.io/qt-6/qthttpserver-index.html Qt HTTP Server] to ongoing works on various helpers for REST in Qt (see [https://bugreports.qt.io/browse/QTBUG-112276 QTBUG-112276] and issues linked to it). Not mentioning the [https://doc.qt.io/QtInterfaceFramework/ Qt Interface Framework] and [https://doc.qt.io/qt-6/qtdbus-index.html Qt D-Bus] as IPC components in Qt.

But what should we do next or differently in this domain? Introduce an integration of GraphQL? Invest more time in OpenAPI instead of GraphQL?

In this session we will give an overview of what is going on and available, but most importantly we want ,to discuss and hear your views and opinions
|-
|Evolving QIcon and theming
|Volker Hilsheimer
|Discussion
|QIcon delegates the loading and rendering of icons to platform-specific icon engines, ultimately producing a pixmap. Theme support is very much based on the [https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html freedesktop spec], which hasn't moved much since 2006 years. In more recent years, [https://learn.microsoft.com/en-us/windows/apps/design/style/segoe-fluent-icons-font Microsoft] and esp Apple have added [https://developer.apple.com/videos/play/wwdc2022/10158 rich support for icons] to their platforms.
QIcon and the theme-abstraction as it is today doesn't map well to those capabilities. The implementation has improved in the context of [https://bugreports.qt.io/browse/QTBUG-102346 QTBUG-102346], but the design is in general too limited to support multiple system themes, layered icons with variable properties, and icon coloring and tinting with palette or hierarchical color support.


Let's discuss how we can evolve QIcon, QIconEngine, and the theming infrastructure we have, so that we can give application developers access to the platform's capabilities, and perhaps emulate what we can on other platforms.

Since it's related, we might also talk about QtSvg, support for vector graphics animations and animated emojis.
|-
|QtWayland Remaining Issues
|David Edmundson
|Discussion
|The Wayland API does not map nicely to patterns used on every other platform in various aspects of window management. We need to fix popups, find a direction for the native API and look at what other unsolved issues we have in the QPA that we either need to fix here or upstream.
|-
|Getting more external contributors
|David Edmundson
|Presentation
|Having the QtProject developed by a wide range of developers is an important part of getting the most of being an open source project. There's a lot of really simple things we can all do as developers to both attract new developers and build them into future maintainers. I can present some experiences from contributing to many other open source projects of what works well from both the contributor and maintainer point of view.
|}
[[Category:QtCS2023]]