QtCS25 - UnifiedStyling: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Session Summary== | ==Session Summary== | ||
==Session Owners== | ==Session Owners== | ||
* Presenter: Richard | |||
* Notes: Volker | |||
==Notes== | |||
// slides go here | |||
* Use a QML document to describe the various aspects of a design system in a UnifiedStyle element with nodes | |||
** singleton | |||
** loads the style from a matching QML document | |||
* child nodes select the type of control, following the element type hierarchy | |||
** propagation | |||
** e.g. `control` describes the design of all controls, `textField` then overrides attributes for text fields | |||
** for each description, can use state-specific designs (e.g. hovered, pressed) | |||
** consistent pattern for styling control elements (e.g. handles) | |||
** animations between states are work in progress | |||
* Theming (e.g. dark/light mode) | |||
** override relevant control attributes depending on which color scheme is active (but can also have custom themes) | |||
* Figma integration | |||
** default colors can be defined as properties | |||
* Widgets | |||
** for widgets we generate a C++ header file that describes the properties for a QStyle implementation | |||
** header file size explodes right now, so room for optimization | |||
** goal is to bring the basic design to both frameworks | |||
** Widgets might be too limited for certain things, e.g. animations - probably an acceptable trade-off | |||
** should not restrict the framework based on widget limitations | |||
* support for custom controls/widgets | |||
** create UnifiedProperties element in custom control, select a pre-defined control type | |||
** API work in progress | |||
[[Category:QtCS2025]] | [[Category:QtCS2025]] | ||
Revision as of 13:00, 8 May 2025
Session Summary
Session Owners
- Presenter: Richard
- Notes: Volker
Notes
// slides go here
- Use a QML document to describe the various aspects of a design system in a UnifiedStyle element with nodes
- singleton
- loads the style from a matching QML document
- child nodes select the type of control, following the element type hierarchy
- propagation
- e.g. `control` describes the design of all controls, `textField` then overrides attributes for text fields
- for each description, can use state-specific designs (e.g. hovered, pressed)
- consistent pattern for styling control elements (e.g. handles)
- animations between states are work in progress
- Theming (e.g. dark/light mode)
- override relevant control attributes depending on which color scheme is active (but can also have custom themes)
- Figma integration
- default colors can be defined as properties
- Widgets
- for widgets we generate a C++ header file that describes the properties for a QStyle implementation
- header file size explodes right now, so room for optimization
- goal is to bring the basic design to both frameworks
- Widgets might be too limited for certain things, e.g. animations - probably an acceptable trade-off
- should not restrict the framework based on widget limitations
- support for custom controls/widgets
- create UnifiedProperties element in custom control, select a pre-defined control type
- API work in progress