Qt Contributor Summit 2025 - Program: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
Line 85: Line 85:
|Google are introducing a memory-safe replacement for Freetype called Fontations which is written in Rust. In general, many of their core components are being ported to Rust. If we would like to use this or other such components in Qt, we would need a build system capable of compiling the code. This will likely be needed by Qt Web Engine as well in near future.
|Google are introducing a memory-safe replacement for Freetype called Fontations which is written in Rust. In general, many of their core components are being ported to Rust. If we would like to use this or other such components in Qt, we would need a build system capable of compiling the code. This will likely be needed by Qt Web Engine as well in near future.
|-
|-
|QtTest: state of the module and best practices
|QtTest: state of the module and the way forward
|Tor Arne Vestbø, Eddy
|Tor Arne Vestbø, Eddy
|Presentation & Discussion
|Presentation & Discussion
|An update on where we are and a chance to ask how to get the best out of the test system.
|An update on where we are and where we want to go
|-
|-
|
|

Revision as of 14:16, 17 March 2025

Event main page: Qt Contributor Summit 2025

Please, add your sessions/talks/presentations to the Table of Session Details at the end of the page.

If you have any issues while editing this page, please contact Pedro Bessa directly at pedro.bessa@qt.io

Our Program

May 7th: Welcome Event (Evening, Time TBA)

May 8th: Contributor Summit Sessions + Dinner

May 9th: Hacking Day


Please note times are subjected to change.

Thursday, May 8th
Time (CEST) Room
Morning Registrations, Welcoming, Keynotes
Time (CEST) Room Room Room Common area
Afternoon Sessions, Lunch and Coffe Break
Evening Dinner at the Event Venue

Table of Session Details

Add your talk here:

Topic Speaker Format Summary
Topic Title Add Your Name(s) Discussion/Presentation/Workshop/... Add a short paragraph about the scope of the proposed talk.
Compile once. Run everywhere (2025 edition) Cristian Adam Presentation Compiling and deploying of C++ applications on Windows, Linux, macOS for x86_64 and arm64 can be challenging. By using Cosmopolitan Libc we could have an alternative.
QProperty and QBindable, take 2 Ulf Hermann Discussion There are new proposals on what to do with them, and we haven't come to a conclusion last time around
State of Qt on Windows Wladimir Leuschner Presentation Status of WoA, Windows SDK integration, Custom titlebars, Windows Store deployment.
qml API review Fabian Kosmale Discussion API reviews are already an arduous endeavour for our C++ API. On the QML side, we have the additional issue that textual diffs of qmltypes are used, but qmltypes are nowadays mostly meant for tooling, not to facilitate API review. Let's discusss how we can improve this
State and Direction of Qt's Build System Jörg Bornemann Presentation & Discussion What happened in Build System land, what are current challenges and future plans.
State and Direction of Qt's i18n and l10n framework Masoud Jami Presentation & Discussion Recent work on i18n/l10n related tools and future plans.
Fontations in Qt: Adding Rust to the build system Eskil Abrahamsen Blomfeldt Discussion Google are introducing a memory-safe replacement for Freetype called Fontations which is written in Rust. In general, many of their core components are being ported to Rust. If we would like to use this or other such components in Qt, we would need a build system capable of compiling the code. This will likely be needed by Qt Web Engine as well in near future.
QtTest: state of the module and the way forward Tor Arne Vestbø, Eddy Presentation & Discussion An update on where we are and where we want to go