touch-packages team mailing list archive

Thread
Date

[Bug 1346975] Re: We should avoid use context property objects

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Zoltan Balogh <zoltan.balogh@xxxxxxxxxxxxx>
Date: Mon, 24 Nov 2014 13:17:57 -0000
Reply-to: Bug 1346975 <1346975@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: New => Confirmed

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

Title:
  We should avoid use context property objects

Status in Ubuntu UI Toolkit:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Confirmed

Bug description:
  Based on this doc: http://www.kdab.com/qml-engine-internals-part-3
  -binding-types/

  v4 engine binding is faster than v8 or javascript bindings. and:

  "The disadvantage is that the v4 engine can not deal with dynamic
  objects, for example those exported from C++ via setContextProperty()"

  
  What means that all objects exported to QML using setContextProperty will not produce V4 binginds.

  We are current exporting two basic objects to QML using
  setContextProperty. (units and FontUtils) , they are heavy used by our
  apps, we should change it to be a singleton.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1346975/+subscriptions