Merge lp:~mterry/qtmir/no-touch-no-lifecycle into lp:qtmir
| Status: | Merged |
|---|---|
| Approved by: | Gerry Boland on 2015-11-04 |
| Approved revision: | 394 |
| Merged at revision: | 400 |
| Proposed branch: | lp:~mterry/qtmir/no-touch-no-lifecycle |
| Merge into: | lp:qtmir |
| Diff against target: |
527 lines (+56/-165) 15 files modified
CMakeLists.txt (+1/-1) debian/control (+2/-2) src/modules/Unity/Application/application.cpp (+7/-25) src/modules/Unity/Application/application.h (+1/-3) src/modules/Unity/Application/application_manager.cpp (+2/-12) src/modules/Unity/Application/application_manager.h (+1/-2) src/modules/Unity/Application/com.canonical.qtmir.gschema.xml (+2/-0) src/modules/Unity/Application/desktopfilereader.cpp (+12/-0) src/modules/Unity/Application/desktopfilereader.h (+1/-0) tests/modules/Application/application_test.cpp (+16/-0) tests/modules/ApplicationManager/application_manager_test.cpp (+0/-117) tests/modules/DesktopFileReader/desktopfilereader_test.cpp (+3/-0) tests/modules/common/fake_desktopfilereader.h (+1/-0) tests/modules/common/mock_desktop_file_reader.h (+7/-0) tests/modules/common/qtmir_test.cpp (+0/-3) |
| To merge this branch: | bzr merge lp:~mterry/qtmir/no-touch-no-lifecycle |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Gerry Boland | 2015-09-29 | Approve on 2015-11-04 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-10-30 | |
|
Review via email:
|
|||
Commit Message
Support new isTouchApp property to ApplicationInfo
Now that qtmir won't decide policy for suspending anymore, we don't need all the lifecycleException handling in qtmir either. That can move to unity8.
But since the GSettings key for that was registered under the qtmir namespace (and there's no technical reason to migrate settings), I left the schema and classes dealing with GSettings alone, for future use.
Description of the Change
Support new isTouchApp property to ApplicationInfo
Now that qtmir won't decide policy for suspending anymore, we don't need all the lifecycleException handling in qtmir either. That can move to unity8.
But since the GSettings key for that was registered under the qtmir namespace (and there's no technical reason to migrate settings), I left the schema and classes dealing with GSettings alone, for future use.
* Are there any related MPs required for this MP to build/function as expected? Please list.
https:/
https:/
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
I'm on that team
| Gerry Boland (gerboland) wrote : | # |
I dislike the API you've added. The requestedState property is what shell uses to set a process to be suspended or not. It is confusing for shell to request a suspended state in one place, and in another place disallow suspending. Shell should just make the correct request first time.
Sure we've had this lifecycle exceptions policy in qtmir, but as you've moved that into unity8, there is no reason I can see for this "canSuspend" concept in qtmir any more.
- 386. By Michael Terry on 2015-10-01
-
Drop canSuspend and RunningInBackground state
- 387. By Michael Terry on 2015-10-01
-
Merge from trunk
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:387
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
- 388. By Michael Terry on 2015-10-01
-
Support RoleIsTouchApp
- 389. By Michael Terry on 2015-10-01
-
minor fixes
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:388
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:389
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Gerry Boland (gerboland) wrote : | # |
This code change looks good to me.
Do we want to police apps from enabling this flag? How would we do that? There's no real way we can prevent an app from setting this. And if it results in a lifecycle exemption, many might set it!!
Perhaps having it so only Touch apps can be launched on the phone, while it is undocked, is enough motivation for app devs not to abuse this?
| Gerry Boland (gerboland) wrote : | # |
Also, I'd love to kill the GSettings schema. I think only MZanetti's TweakGeek app relies on it ATM.
| Michael Terry (mterry) wrote : | # |
> Do we want to police apps from enabling this flag?
From setting X-Ubuntu-
That's one of the benefits of re-using this flag. :)
> Also, I'd love to kill the GSettings schema.
Fair... The default right now is just the music-app. I don't know whether it's safe to remove that yet. Presumably that uses content-hub now? Or wants to in the future, I'd hope.
Anyway, that can be a separate MP.
| Gerry Boland (gerboland) wrote : | # |
/«BUILDDIR»
ASSERT_
Please use ASSERT_FALSE
- 390. By Michael Terry on 2015-10-15
-
Merge from trunk
- 391. By Michael Terry on 2015-10-15
-
Use ASSERT_TRUE/FALSE
| Michael Terry (mterry) wrote : | # |
> Please use ASSERT_FALSE
Done.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:391
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
- 392. By Michael Terry on 2015-10-27
-
Merge from trunk
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:392
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
- 393. By Michael Terry on 2015-10-30
-
Bump shell application version
- 394. By Michael Terry on 2015-10-30
-
Bump shell application version harder
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:393
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:394
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Gerry Boland (gerboland) wrote : | # |
Tested on device, I see no behavioural regression, +1 from me.

FAILED: Continuous integration, rev:385 jenkins. qa.ubuntu. com/job/ qtmir-ci/ 466/ jenkins. qa.ubuntu. com/job/ qtmir-vivid- amd64-ci/ 162/console jenkins. qa.ubuntu. com/job/ qtmir-vivid- armhf-ci/ 162/console jenkins. qa.ubuntu. com/job/ qtmir-vivid- i386-ci/ 44/console jenkins. qa.ubuntu. com/job/ qtmir-wily- amd64-ci/ 199/console jenkins. qa.ubuntu. com/job/ qtmir-wily- armhf-ci/ 199/console jenkins. qa.ubuntu. com/job/ qtmir-wily- i386-ci/ 44/console
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/qtmir- ci/466/ rebuild
http://