Mir & UnityNextUI weekly Mar22, 2013

[Kevin Gunn]

Hi all,
hope all finds you well.
Please find the Mir/UnityNextUI team weeklies
br,kg

*UnityNext & Mir Weekly Report**
*Mar 22, 2013*
*

*Current Team Theme*

  * Integrate UnityNext onto Mir
      o Improve UnityNext testing & code cleanup post MWC
      o Mir build out to support UnityNext
  * As always  live action here
      o https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui-iteration-0
      o https://blueprints.launchpad.net/ubuntu/+spec/client-1303-mir-phone-iteration-0

*Acheived this week**
*

  * Mir
      o Couple of large chunks of work merged proposed
          + Input event handling up to client
          + buffer age (e.g. to handle stale buffer queueing)
          + enabling in-process EGL clients
      o Some design work/discussion around "edge" type (aka dock)
      o Additional progress on Nexus4 hwc1.1 integration
      o Several good old fashioned bug fixes & cleanup work
  * UnityNext UI
      o Continued creating various tests for UnityNext including hud
        testing with mock components for better isolated testing
          + for those that like details...you can browse the code here
            http://bazaar.launchpad.net/~unity-team/unity/phablet/files/head:/tests/
            <http://bazaar.launchpad.net/%7Eunity-team/unity/phablet/files/head:/tests/>
          + On a relatednote, we'd like to have some "auto-magic" tool
            to determine coverage for the qml code- however nothing
            really exists, we'll have to just manually trackfor now, but
            open to any help here  
      o Began a handful of good oldfashioned bug fixes
      o Notification class/object layout proposed, but requires rework,
        redirect focus on renderer instead
      o Continued work on dynamic application support for the App Lens

*Shooting for next week*

  * Mir
      o Continue logging work
      o Continue work on surface ordering / states
      o Continue remaining work on surface types
  * UnityNext UI
      o Work through manual account of testing & address any remaining
        items of significance
      o Take2 on getting Notification skeleton in place - target render
        the bubble, with a test code as the mock notification
      o Continue app lens work
      o Continue addressing the TODO/FIXMEs (more MWC debt)
      o (might have to work on) usability testing options for the design
        team

*Risks and Issues*

  * Need a tool for qml test coverage

*Noteworthy/Something cool*

  * ditto!... http://www.youtube.com/watch?v=1-DA5YqsH7I

**
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20130322/86e8eead/attachment.html>