XMLWordPrintable

Details

    Description

      What is the benefit? Why is this valuable?

      Customers don't want to change code for different product variants. Our offering on theming is weak at the moment.

      What are common use cases?

      Any product development where there are different variants of the UI

      Technical information

      Typically a theme is a set of variables that control common things like used color in certain type or such customization. When the 'magic numbers' from the code are changed to variables that are defined in an array, new product variants can be easily done by creating new copy of the array. There is a engine PB entry for this as well, if these actions can be merged, it would be good for everyone: https://qt.productboard.com/entity-detail/features/15367291

      • Controls
        • have Style (app global)
        • Project is always using 'a theme' -> default operation
        • Attributes for components are derived from the theme
          • by default controls (qtquick) don't have all properties
      • Basic theme settings
        • Radius
        • Background color
        • Color
      • Solution should be on-par with CSS
        • can we do styling in CSS ?

      Update:

      Theme management done on DS

      • Variables used to retrieve palettes' theme settings from Figma
      • Variables are then used in QML instead of fixed colors and values
      • Manage the forms in DS as well

      • Vikas (commitment)

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            algerman Aleksei German
            productboard Productboard
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes