← Back to team overview

ubuntu-phone team mailing list archive

Unity API status update

 

Scopes

We finally landed departments and with that bumped the scopes API
version to 0.5. With that the somewhat bigger outstanding todo items for
RTM are:

- Settings: implementation is half way through, expecting to land next week.
- Image cache: will be specific to Unity 8 shell, so no general UITK
component. Implementation ongoing, landing expected by end of this week.
- Go binding: updated late last week to be compatible with newest scopes
API version. However, department support is still missing, expected for
end of this week.
- Category expansion: designs are in place, implementation not yet started.
- Location information: as scopes won't be able to directly access
location service, they can request location to be passed along other
query parameters. Users will be able to restrict location access via
scope settings page. Problem/solution well understood, but
implementation hasn't started yet.
- Click scope: locally installed apps and app store are now separate
scopes. Department support and highlighting apps in store scope
implemented and expected tomorrow.
- Payment service: Most parts have landed by now but are still disabled
by default. Final design review still outstanding.
- Scopes: still quite some work left to get local music and video scopes
according to specs. Will also work on implementing more scopes like YouTube.


Indicators/Settings

First iteration of transfer indicator landed to unblock development
components depending on it. After another two to three days of UI and
backend polishing we're planning to finally enable the transfer
indicator early next week.

Flight mode and wifi AP settings are both in silo for testing.
Displaying dual SIM information in indicator and providing hotspot
functionality are currently under development.


Mediascanner

Extended to also scan images, that is jpg. Since Mediascanner won't be a
trusted service for RTM, we're disabling dbus API for time being. To
address the performance issues we'll refactor the qml plugin to run its
own thread(s).


Thomas