Merge lp://staging/~sergiusens/gallery-app/click-support into lp://staging/gallery-app
- click-support
- Merge into trunk
Status: | Merged |
---|---|
Merged at revision: | 919 |
Proposed branch: | lp://staging/~sergiusens/gallery-app/click-support |
Merge into: | lp://staging/gallery-app |
Diff against target: |
410 lines (+122/-57) 13 files modified
CMakeLists.txt (+7/-5) click-build.sh (+16/-0) click/CMakeLists.txt (+1/-1) click/gallery-apparmor.json (+1/-0) click/gallery-content.json (+5/-0) click/manifest.json.in (+4/-3) desktop/CMakeLists.txt (+13/-6) desktop/gallery-app.desktop.in (+5/-6) rc/qml/AlbumsOverview.qml (+1/-1) rc/qml/Utility/PhotosToolbarActions.qml (+1/-1) tests/autopilot/gallery_app/tests/__init__.py (+59/-31) tests/autopilot/gallery_app/tests/test_album_view.py (+8/-3) tests/autopilot/gallery_app/tests/test_picker_mode.py (+1/-0) |
To merge this branch: | bzr merge lp://staging/~sergiusens/gallery-app/click-support |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot | continuous-integration | Approve | |
Ken VanDine | Pending | ||
Bill Filler | Pending | ||
Review via email: mp+207515@code.staging.launchpad.net |
This proposal supersedes a proposal from 2014-01-10.
Commit message
Click support
Description of the change
launch camera with appropriate click url in Qt.openrUrlExte
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
FAILED: Continuous integration, rev:906
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
PASSED: Continuous integration, rev:906
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
FAILED: Continuous integration, rev:907
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Bill Filler (bfiller) wrote : Posted in a previous version of this proposal | # |
dropping the --fullscreen arg from the exec causes the app to not launched fullscreen on the devices anymore. it needs to be fullscreen so the top panel is hidden when a photo is viewed but no current way to do that dynamically - has to be all or nothing..
so, what we really want is to have the app determine which device it's running on and do fullscreen mode internally. it's correct to remove it from the desktop file/exec but we need to add the support in the code to run it fullscreen if !DESKTOP_MODE
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
PASSED: Continuous integration, rev:908
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Ken VanDine (ken-vandine) wrote : Posted in a previous version of this proposal | # |
Needs click hook for content-hub, I proposed a branch to fix this.
https:/
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
FAILED: Continuous integration, rev:909
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
Ken VanDine (ken-vandine) : Posted in a previous version of this proposal | # |
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
FAILED: Continuous integration, rev:910
http://
Executed test runs:
FAILURE: http://
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 : Posted in a previous version of this proposal | # |
PASSED: Continuous integration, rev:911
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
PASSED: Continuous integration, rev:912
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
PASSED: Continuous integration, rev:913
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal | # |
PASSED: Continuous integration, rev:915
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Bill Filler (bfiller) wrote : Posted in a previous version of this proposal | # |
Are there any related MPs required for this MP to build/function as expected?
Yes, lots. See the request in CI Train
Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes):
Yes
Did you perform an exploratory manual test run of your code change and any related functionality on device or emulator?
Yes
Did you successfully run all tests found in your component's Test Plan (https:/
YES
If you changed the UI, was the change specified/approved by design?
N/A
If you changed the packaging (debian), did you subscribe a core-dev to this MP?
N/A
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:916
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:916
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:916
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:916
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
FAILED: Continuous integration, rev:905 jenkins. qa.ubuntu. com/job/ gallery- app-ci/ 628/ jenkins. qa.ubuntu. com/job/ gallery- app-trusty- amd64-ci/ 53 jenkins. qa.ubuntu. com/job/ gallery- app-trusty- armhf-ci/ 53 jenkins. qa.ubuntu. com/job/ gallery- app-trusty- armhf-ci/ 53/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ gallery- app-trusty- i386-ci/ 53 jenkins. qa.ubuntu. com/job/ generic- mediumtests- trusty/ 2253 jenkins. qa.ubuntu. com/job/ generic- mediumtests- trusty- touch/2138/ console jenkins. qa.ubuntu. com/job/ autopilot- testrunner- otto-trusty/ 1976 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- amd64/2255 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- amd64/2255/ artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- armhf/2138 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- armhf/2138/ artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ generic- mediumtests- runner- mako/4598/ console s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 2998
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/gallery- app-ci/ 628/rebuild
http://