Qt Contributors Summit 2026 - Program: Difference between revisions
Added session proposal about Qt Bridge for C# |
Merge edit by Oleksandr Kunichik Tag: merged edit of another user |
||
| Line 19: | Line 19: | ||
|''Add a short paragraph about the scope of the proposed talk.'' | |''Add a short paragraph about the scope of the proposed talk.'' | ||
|- | |- | ||
|Qt Bridge Rust | |Qt Bridge 4 Rust | ||
|Matthias Rauter | |Matthias Rauter | ||
|Presentation + Discussion | |Presentation + Discussion | ||
| Line 41: | Line 41: | ||
|A tale of my journey building a niche text editor using Qt widgets, the edges of the Qt's rich text rendering and editing APIs, and perhaps tossing some ideas of what can be improved. | |A tale of my journey building a niche text editor using Qt widgets, the edges of the Qt's rich text rendering and editing APIs, and perhaps tossing some ideas of what can be improved. | ||
|- | |- | ||
| | |What Qt Looks Like to an AI | ||
| | |Oleksandr Kunichik | ||
|Presentation + Discussion | |Presentation + Discussion | ||
| | |Benchmarking AI coding agents on a real paused Qt 6/Android app. The failures map directly onto Qt design choices: MOC invisibility, QML-root signal trap, under-represented JNI API. Closes with five concrete asks for qmllint/qmlls/docs to make Qt more AI-legible. | ||
|- | |- | ||
| | | | ||
Latest revision as of 09:28, 19 June 2026
Event main page: Qt Contributors Summit 2026
→ If you have any issues editing this page, please send your proposal directly to volker.hilsheimer@qt.io
Session proposals:
Add topics you would like to talk about here. We will review the proposals closer to the event to create the schedule.
| Topic | Speaker | Format | Summary |
|---|---|---|---|
| Topic Title | Add Your Name(s) | Discussion/Presentation/Workshop/Lightning talk/... | Add a short paragraph about the scope of the proposed talk. |
| Qt Bridge 4 Rust | Matthias Rauter | Presentation + Discussion | A short presentation of what we have in the Rust Qt Bridge. An overview over the API and the use cases we cover.
Discussion about what to improve and how to contribute and collaborate. |
| Qt & CRA | Alex Blasche | Presentation + Discussion | A presentation how CRA compliance impacts Qt development teams and contributors. |
| C++26 and moc | Volker Hilsheimer | Presentation + Discussion | After Reflections landed in gcc-trunk I followed up on my hackathon project to see how much we can implement what moc does using Reflections. This was a promising exercise, even though a few things were not quite possible yet.
Let's have a look at what - based on that experiment - the code for a meta-object enabled type in Qt could look like. |
| Tickling the boundaries of Qt Widgets Text Editing | Igor Khanin | Presentation + Discussion | A tale of my journey building a niche text editor using Qt widgets, the edges of the Qt's rich text rendering and editing APIs, and perhaps tossing some ideas of what can be improved. |
| What Qt Looks Like to an AI | Oleksandr Kunichik | Presentation + Discussion | Benchmarking AI coding agents on a real paused Qt 6/Android app. The failures map directly onto Qt design choices: MOC invisibility, QML-root signal trap, under-represented JNI API. Closes with five concrete asks for qmllint/qmlls/docs to make Qt more AI-legible. |