ubuntu-sdk-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

Additionally, as can be seen here, the qml types info for several other
modules already include the UbuntuColors component:

osomon@bribon:/usr/lib/x86_64-linux-gnu/qt5/qml$ grep -rn \"UbuntuColors\"
Ubuntu/PerformanceMetrics/plugins.qmltypes:75:        name: "UbuntuColors"
Ubuntu/Components/plugins.qmltypes:1710:        name: "UbuntuColors"
Ubuntu/Content/plugins.qmltypes:300:        name: "UbuntuColors"
Ubuntu/Test/plugins.qmltypes:143:        name: "UbuntuColors"


** Also affects: qtdeclarative-opensource-src (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1583985

Title:
  qmlplugindump for any module importing Ubuntu.Components always
  exposes UbuntuColors

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Not sure whether that’s a bug in the qmlplugindump tool itself, or in the UITK.
  When invoking qmlplugindump on any module that imports Ubuntu.Components, the resulting typeinfo always exposes the UbuntuColors component:

      Component {
          prototype: "QObject"
          name: "UbuntuColors"
          exports: ["UbuntuColors 1.3"]
          exportMetaObjectRevisions: [3]
          isComposite: true
          isCreatable: false
          isSingleton: true
          Property { name: "lightAubergine"; type: "QColor"; isReadonly: true }
          Property { name: "midAubergine"; type: "QColor"; isReadonly: true }
          Property { name: "darkAubergine"; type: "QColor"; isReadonly: true }
          Property { name: "warmGrey"; type: "QColor"; isReadonly: true }
          Property { name: "coolGrey"; type: "QColor"; isReadonly: true }
          Property { name: "orangeGradient"; type: "QQuickGradient"; isPointer: true }
          Property { name: "greyGradient"; type: "QQuickGradient"; isPointer: true }
          Property { name: "orange"; type: "QColor"; isReadonly: true }
          Property { name: "lightGrey"; type: "QColor"; isReadonly: true }
          Property { name: "silk"; type: "QColor"; isReadonly: true }
          Property { name: "darkGrey"; type: "QColor"; isReadonly: true }
          Property { name: "slate"; type: "QColor"; isReadonly: true }
          Property { name: "red"; type: "QColor"; isReadonly: true }
          Property { name: "green"; type: "QColor"; isReadonly: true }
          Property { name: "blue"; type: "QColor"; isReadonly: true }
          Property { name: "purple"; type: "QColor"; isReadonly: true }
          Property { name: "porcelain"; type: "QColor"; isReadonly: true }
          Property { name: "ash"; type: "QColor"; isReadonly: true }
          Property { name: "graphite"; type: "QColor"; isReadonly: true }
          Property { name: "inkstone"; type: "QColor"; isReadonly: true }
          Property { name: "jet"; type: "QColor"; isReadonly: true }
      }

  This can be easily reproduced by invoking e.g.:

      qmlplugindump -v -noinstantiate Ubuntu.Web 0.2 > test.qmltypes

  I’ve seen the same happen when dumping the qml types for
  Ubuntu.UnityWebApps (see https://code.launchpad.net/~osomon/unity-
  webapps-qml/qmltypes/+merge/295242).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1583985/+subscriptions