I guess you’ll have seen Albert’s blog post about the Qt Contributor Summit, if not do it.
I thought it would be interesting to recap a bit. As he put it, most discussions revolved around how to iterate every part of Qt into Qt 6. It’s exciting, a little bit scary but exciting.
One bit especially interesting is the graphics stack. Back in Qt 5.0, Qt took the liberty of limiting the graphics stack to OpenGL, but the world has changed since: On Windows the only proper stack is Direct3D 12, Apple introduced Metal and recently deprecated OpenGL and Vulkan is coming rather strong. It looks like embracing these systems transparently will be one of the most exciting tasks to achieve. From a KDE & Plasma perspective I don’t think this is scary, OpenGL is here to stay on Linux. We will get a Framework based on a more flexible base and we can continue pushing Plasma, Wayland, Plasma Mobile with confidence that the world won’t be crumbling. And with a bit of luck, if we want some parts to use Vulkan, we’ll have it properly abstracted already.
Furthermore, here’s some of the re-caps some people (mainly Thiago ^^’) uploaded after the sessions:
- Third-party and security policy: http://lists.qt-project.org/pipermail/development/2018-June/032862.html
- Serialisation session notes http://lists.qt-project.org/pipermail/development/2018-June/032870.html
- Date/time session http://lists.qt-project.org/pipermail/development/2018-June/032875.html
- clang-format usage before contributing http://lists.qt-project.org/pipermail/development/2018-June/032918.html
- Qt Remote Objects https://wiki.qt.io/QtCS2018_RemoteObjects
- unified data model API in QtCore http://lists.qt-project.org/pipermail/development/2018-June/032890.html
- unique_ptr and Qt (not from QtCS but discussed there too) http://lists.qt-project.org/pipermail/development/2018-June/032829.html
I think it was a great conference, thanks to Tero and The Qt Company for putting it together. And thanks to the sponsors for making it possible. 🙂
See you all again, Qt-ies!