| 2016-06-08 20:30:37 |
Pat McGowan |
description |
This will need better definition but starting as a placeholder
The intended model for app specific events that do not fit well with the existing function based indicators is to use the launcher api in libunity to pass information tot he launcher icon for the app. Ideally this would be available via QML, HTML/javascript and C++. |
This will need better definition but starting as a placeholder
The intended model for app specific events that do not fit well with the existing function based indicators is to use the launcher api in libunity to pass information tot he launcher icon for the app. Ideally this would be available via QML, HTML/javascript and C++.
Existing docs at https://wiki.ubuntu.com/Unity/LauncherAPI |
|
| 2016-06-09 14:40:50 |
Michael Zanetti |
description |
This will need better definition but starting as a placeholder
The intended model for app specific events that do not fit well with the existing function based indicators is to use the launcher api in libunity to pass information tot he launcher icon for the app. Ideally this would be available via QML, HTML/javascript and C++.
Existing docs at https://wiki.ubuntu.com/Unity/LauncherAPI |
In order to provide an API for applications to interact with the Launcher, as set of tasks is required:
* reimplement old unity7 API in the launcher to keep X11/XMir apps supported. The libertine container needs to bridge those calls from inside the container to outside. (Existing docs at https://wiki.ubuntu.com/Unity/LauncherAPI)
* because of the application lifecycle, a new API is required that works in a different/more persistent way so that states are preserved when the application goes away. Some of them (count emblem, progress bar, and Alert) are are already implemented, some others (Quicklists) are still missing.
* AppArmor profiles need to be updated so that applications can call those methods from within confinement. So far they are only called from trusted helpers, like the push-client.
* Nicer APIs need to be created so that those actions can be called from C++/Qt, QML and HTML/JS. |
|
