Merge lp:~rpadovani/webbrowser-app/fixBookmarkDesign into lp:webbrowser-app
| Status: | Merged |
|---|---|
| Approved by: | Olivier Tilloy on 2015-02-04 |
| Approved revision: | 882 |
| Merged at revision: | 912 |
| Proposed branch: | lp:~rpadovani/webbrowser-app/fixBookmarkDesign |
| Merge into: | lp:webbrowser-app |
| Diff against target: |
239 lines (+102/-66) 3 files modified
src/app/webbrowser/HistorySectionDelegate.qml (+3/-1) src/app/webbrowser/HistoryView.qml (+98/-64) src/app/webbrowser/upstreamcomponents/ListItemWithActions.qml (+1/-1) |
| To merge this branch: | bzr merge lp:~rpadovani/webbrowser-app/fixBookmarkDesign |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-02-24 | |
| Olivier Tilloy | 2015-01-24 | Approve on 2015-02-04 | |
|
Review via email:
|
|||
Commit Message
Fixed design of multiselection in history view
Description of the Change
Fixed design of multiselection in history view
| Olivier Tilloy (osomon) wrote : | # |
After applying the change, this is how it looks on my desktop (utopic): http://
There are a few things that need adjusting still, wrt the visual spec:
- icons in the top toolbar are scaled up, they shouldn’t be
- icons in the top toolbar need to have a left and right margin to be aligned with the rest of the items on screen
- the horizontal line that underlines each section header should be aligned to the left with the checkboxes, and to the right it should have a 2GU margin
- the text of the section headers should also be aligned to the left with the checkboxes (i.e. a 2GU left margin)
- there should be 2GUs between the horizontal line and the first item in a section (there currently is only one)
- there should be 2.5GUs between the last item in a section and the text of the following header
| Riccardo Padovani (rpadovani) wrote : | # |
> After applying the change, this is how it looks on my desktop (utopic):
> http://
>
> There are a few things that need adjusting still, wrt the visual spec:
> - icons in the top toolbar are scaled up, they shouldn’t be
Sorry about this, I'm on vivid and it works well, I think it's due this commit[0] in the sdk, probably hasn't been backported yet. Anyway, I reworked the Icon, so now should be ok.
> - icons in the top toolbar need to have a left and right margin to be aligned
> with the rest of the items on screen
Fixed
> - the horizontal line that underlines each section header should be aligned
> to the left with the checkboxes, and to the right it should have a 2GU margin
fixed
> - the text of the section headers should also be aligned to the left with the
> checkboxes (i.e. a 2GU left margin)
fixed
> - there should be 2GUs between the horizontal line and the first item in a
> section (there currently is only one)
Fixed
> - there should be 2.5GUs between the last item in a section and the text of
> the following header
About this, I didn't find any way to find if a section it's the first, so I set a negative margin to the listview to compensate the topmargin the first section has. There is a better way to implement that?
[0]https:/
- 876. By Riccardo Padovani on 2015-01-26
-
addressed osomon's comments
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:876
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Francis Ginther (fginther) wrote : | # |
The jenkins node for the amd64 build failed, I've restarted a new ci run.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:876
http://
Executed test runs:
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Riccardo Padovani (rpadovani) wrote : | # |
The failure seems unrelated to the branch (maybe is due [0]?).
Anyway, if [1] lands the test shouldn't fail again.
[0] https:/
[1] https:/
| Olivier Tilloy (osomon) wrote : | # |
The test failure is unrelated indeed.
This looks much better now. A bunch of additional minor remarks:
- When in multi-selection mode, the checkbox is shifted a bit to the right (between 0.5 and 1 GU), and is not aligned with the section header
- According to the visual spec, the background of the toolbar seems to be white
- When in multi-selection mode, scrolling the list up makes it overlap with the toolbar. Can the toolbar be made to appear on top of the list?
- When an entry is selected, it’s highlighted, but it’s not in the visual spec
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:876
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Riccardo Padovani (rpadovani) wrote : | # |
> This looks much better now. A bunch of additional minor remarks:
>
> - When in multi-selection mode, the checkbox is shifted a bit to the right
> (between 0.5 and 1 GU), and is not aligned with the section header
Wow, I didn't notice this! I spend some time to understand the difference, but I fixed it now
> - According to the visual spec, the background of the toolbar seems to be
> white
Fixed
>
> - When in multi-selection mode, scrolling the list up makes it overlap with
> the toolbar. Can the toolbar be made to appear on top of the list?
Fixed
> - When an entry is selected, it’s highlighted, but it’s not in the visual
> spec
I fixed that, but there is a little color change, because you asked[0] a response when there user click on something, so there is a color change on mouseArea.pressed.
Atm, I don't have an idea to avoid this color change... Suggestions?
[0]https:/
- 877. By Riccardo Padovani on 2015-01-28
-
Addressed some issues raised by oSoMoN
| Olivier Tilloy (osomon) wrote : | # |
That looks great now, very close to the visual design spec.
For the implementation of the buttons in the topBar, couldn’t you use the ToolbarButton standard component (http://
If not, you should probably make them an AbstractButton that contains both Icon and a Label (instead of Text), and have the font size defined by the 'fontSize' property (http://
- 878. By Riccardo Padovani on 2015-01-28
-
refactoring topbar in history page
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:877
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
- 879. By Riccardo Padovani on 2015-01-28
-
Fixing actions
| Riccardo Padovani (rpadovani) wrote : | # |
You're totally right, now the code is cleaner!
But, for some reasons, onTriggered doesn't work, so I had to use MouseArea... Hope it's good in any case!
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:879
http://
Executed test runs:
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Olivier Tilloy (osomon) wrote : | # |
Ah, sorry for suggesting the use of ToolbarButton, it is apparently deprecated (or meant to be anyway, I don’t see any reference to it being obsolete in the online docs, but I clearly remember a conversation with the UITK folks in which they said it shouldn’t be used anymore).
I now remember that I wrote a custom ToolbarAction component (src/app/
See how to use it here: http://
- 880. By Riccardo Padovani on 2015-02-01
-
Replaced ToolbarButton with ToolbarAction
| Riccardo Padovani (rpadovani) wrote : | # |
Updated :-)
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:880
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Olivier Tilloy (osomon) wrote : | # |
Thanks!
Sorry if it looks like I’m picking nits here, but the anchor changes in ListItemWithAct
- 881. By Riccardo Padovani on 2015-02-03
-
Removed modifications from ListItemWithAct
ions.qml
| Riccardo Padovani (rpadovani) wrote : | # |
No, you're totally right, I shouldn't modify upstream component if isn't strictly needed (as for color).
I removed the anchors edit and implemented it in HistoryView.qml
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:881
http://
Executed test runs:
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Olivier Tilloy (osomon) wrote : | # |
That looks great now, thanks!
One last tiny suggestion, and it will be good to merge: in topBar, the item that contains the actions doesn’t need to be a Rectangle, as it has nothing to actually draw, it could be replaced by an Item. And instead of setting its width and height, just use anchors.
- 882. By Riccardo Padovani on 2015-02-04
-
Addressed osomon's comment about anchors and rectangle/item
| Riccardo Padovani (rpadovani) wrote : | # |
Done :-)
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:882
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:882
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

FAILED: Continuous integration, rev:875 jenkins. qa.ubuntu. com/job/ webbrowser- app-ci/ 1389/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 971 jenkins. qa.ubuntu. com/job/ generic- mediumtests- vivid/446 jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- amd64-ci/ 147 jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- armhf-ci/ 147 jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- armhf-ci/ 147/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- i386-ci/ 147 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 860 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 969 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 969/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 17414 jenkins. qa.ubuntu. com/job/ autopilot- testrunner- otto-vivid/ 367 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-amd64/ 538 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-amd64/ 538/artifact/ work/output/ *zip*/output. zip
http://
Executed test runs:
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/webbrowser- app-ci/ 1389/rebuild
http://