Merge lp:~lukas-kde/unity8/convergedIndicators into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Albert Astals Cid on 2015-12-02 |
| Approved revision: | 2050 |
| Merged at revision: | 2087 |
| Proposed branch: | lp:~lukas-kde/unity8/convergedIndicators |
| Merge into: | lp:unity8 |
| Diff against target: |
443 lines (+76/-40) 16 files modified
plugins/Unity/Indicators/CMakeLists.txt (+2/-1) plugins/Unity/Indicators/actionrootstate.h (+1/-1) plugins/Unity/Indicators/indicator.cpp (+2/-3) plugins/Unity/Indicators/indicator.h (+1/-1) plugins/Unity/Indicators/indicatorsmanager.cpp (+31/-15) plugins/Unity/Indicators/indicatorsmanager.h (+4/-1) plugins/Unity/Indicators/indicatorsmodel.cpp (+5/-5) plugins/Unity/Indicators/indicatorsmodel.h (+1/-1) plugins/Unity/Indicators/menucontentactivator.h (+1/-1) plugins/Unity/Indicators/modelprinter.h (+1/-1) plugins/Unity/Platform/CMakeLists.txt (+2/-0) plugins/Unity/Platform/platform.cpp (+13/-4) plugins/Unity/Platform/platform.h (+7/-1) qml/Components/VolumeControl.qml (+2/-2) qml/Shell.qml (+2/-2) tests/plugins/Unity/Indicators/CMakeLists.txt (+1/-1) |
| To merge this branch: | bzr merge lp:~lukas-kde/unity8/convergedIndicators |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Albert Astals Cid (community) | 2015-11-20 | Approve on 2015-12-02 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-12-02 | |
|
Review via email:
|
|||
Commit Message
Indicators convergence: use the "phone" profile everywhere
Description of the Change
Indicators: use the "phone" profile everywhere
Objective: functionality available does not change when switching the UI mode. Cf. https:/
There are 2 notable exceptions:
1) session indicator: enabled conditionally, typically when running in a multisession/
2) battery/power indicator: we still use the "desktop" profile on a PC as we can't (yet) control the brightness
Additionally, cleanup the code a bit.
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in plugins/
1 conflicts encountered.
- 2047. By Lukáš Tinkl on 2015-11-30
-
merge trunk, resolve conflicts
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Text conflict in plugins/
> 1 conflicts encountered.
Fixed
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2047
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
Some questions:
* The "indicator-
* Why move m_iface creation to init()?
* Do we want to keep the qDebug from init()
* If m_iface and m_seatIface are only to be in init() maybe we can make them function variables instead of class members and save some memory?
* Why do we need "property variant muteActionObject: indicators.
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Some questions:
>
> * The "indicator-
> get in the "phone" profile?
Right, that's probably not needed now that we'll always use the "phone" mode
> * Why move m_iface creation to init()?
To decouple the DBUS related stuff from the constructor
> * Do we want to keep the qDebug from init()
Nope, I'll make it a qCDebug()
> * If m_iface and m_seatIface are only to be in init() maybe we can make them
> function variables instead of class members and save some memory?
Good point yeah
> * Why do we need "property variant muteActionObject:
> indicators.
> ("silent-mode")" if the profile is always "phone"?
Yup, still not sure about the fate of the sound-indicator, for example currently the "Silent mode" when running on a PC doesn't mute the sound at all...
- 2048. By Lukáš Tinkl on 2015-12-01
-
address review issues
remove debug, use local variables, nuke unneeded keyboard quirk
| Lukáš Tinkl (lukas-kde) wrote : | # |
All the issues pointed out should be addressed
- 2049. By Lukáš Tinkl on 2015-12-01
-
drop unused include
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2049
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
Triggered a CI rebuild.
| Albert Astals Cid (aacid) wrote : | # |
After testing this i see i get an empty "indicator-
So unless we're going to fix it i guess you should bring back the blackilist with a big "TODO FIXME".
What do you think?
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2049
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2050. By Lukáš Tinkl on 2015-12-02
-
reinstate the keyboard-indicator filtering
looks like this is always loaded
| Lukáš Tinkl (lukas-kde) wrote : | # |
> After testing this i see i get an empty "indicator-
> suggestion that it'd be gone because we are in "phone" mode is wrong and we
> just load all the indicators installed in the PC.
>
> So unless we're going to fix it i guess you should bring back the blackilist
> with a big "TODO FIXME".
>
> What do you think?
Ye, I re-added the filter
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2050
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
Yes
* Did CI run pass? If not, please explain why.
Yes, Vivid
* Did you make sure that the branch does not contain spurious tags?
Yes

FAILED: Continuous integration, rev:2046 jenkins. qa.ubuntu. com/job/ unity8- ci/6802/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 5387 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- xenial- touch/217/ console jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/1513 jenkins. qa.ubuntu. com/job/ unity8- qmluitest- xenial- amd64/215/ console jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/1408 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/1408 jenkins. qa.ubuntu. com/job/ unity8- xenial- amd64-ci/ 215/console jenkins. qa.ubuntu. com/job/ unity8- xenial- i386-ci/ 214/console jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-touch/ 4259 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 5401 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 5401/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 25468 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- xenial- touch/68/ console jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- xenial- armhf/216 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- xenial- armhf/216/ artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 25467
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/6802/ rebuild
http://