Qt Contributor Summit 2023 - Program: Difference between revisions
WindJunkie (talk | contribs) (Added the "Qt - Connected First" talk proposal) |
(Add session about QIcon and theming) |
||
Line 41: | Line 41: | ||
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 | 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, 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. | |||
|} | |} | ||
[[Category:QtCS2023]] | [[Category:QtCS2023]] |
Revision as of 07:43, 19 July 2023
Sessions
Please, add your sessions/talks/presentations to the table below.
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.
Topic | Speaker | Format | Summary |
---|---|---|---|
TaskTree | Jarek Kobus | Presentation | The 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 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 Qt gRPC module and the "revived" Qt HTTP Server to ongoing works on various helpers for REST in Qt (see QTBUG-112276 and issues linked to it). Not mentioning the Qt Interface Framework and 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 freedesktop spec, which hasn't moved much since 2006 years. In more recent years, Microsoft and esp Apple have added 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, 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.
Since it's related, we might also talk about QtSvg, support for vector graphics animations and animated emojis. |