Tag: merged edit of another user |
|
| (6 intermediate revisions by 6 users not shown) |
| Line 2: |
Line 2: |
| Event main page: [[Qt Contributors Summit 2026]] | | Event main page: [[Qt Contributors Summit 2026]] |
|
| |
|
| ''<small>→ If you have any issues editing this page, please send your proposal directly to volker.hilsheimer@qt.io</small>''
| | == Call for Proposals == |
|
| |
|
| == Session proposals: ==
| | Propose topics you would like to talk about by filling this form: |
|
| |
|
| Add topics you would like to talk about here. We will review the proposals closer to the event to create the schedule.
| | https://qt-project.atlassian.net/jira/software/c/projects/QTCS/form/1003 |
|
| |
|
| {| class="wikitable"
| | For the list of proposed topics, see |
| !Topic
| | |
| !Speaker
| | https://qt-project.atlassian.net/jira/software/c/projects/QTCS/list |
| !Format
| | |
| !Summary
| | We will open the list of topics for voting, and create the schedule based on the results close to the event. |
| |-
| |
| |''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 [https://www.qt.io/blog/c26-reflection-qrangemodel hackathon project] to see how much we can implement what moc does using Reflections. This was a [https://git.qt.io/vohilshe/cpp26metaobject 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.
| |
| |-
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |}
| |
Event main page: Qt Contributors Summit 2026
Call for Proposals
Propose topics you would like to talk about by filling this form:
https://qt-project.atlassian.net/jira/software/c/projects/QTCS/form/1003
For the list of proposed topics, see
https://qt-project.atlassian.net/jira/software/c/projects/QTCS/list
We will open the list of topics for voting, and create the schedule based on the results close to the event.