Merge lp:~robru/gwibber/margins into lp:gwibber
Status: | Merged |
---|---|
Approved by: | Ken VanDine |
Approved revision: | 1425 |
Merged at revision: | 1424 |
Proposed branch: | lp:~robru/gwibber/margins |
Merge into: | lp:gwibber |
Diff against target: |
35 lines (+3/-4) 2 files modified
qml/StatusUpdateTileDetails.qml (+1/-1) qml/ThreadView.qml (+2/-3) |
To merge this branch: | bzr merge lp:~robru/gwibber/margins |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ken VanDine | Approve | ||
Review via email: mp+154259@code.launchpad.net |
Commit message
Add some margins in places to make the app more sexy and less cluttered.
Description of the change
Alright Ken, here's my very first dabble with Qml. It's modest, alright, but it fixes some visual margin glitches that were annoying me, so I'd say this makes everything sexier.
One thing that would be super handy for getting me (and the community) up to speed would be if you could put some comments in things! I had to guess which file contained the widgets I was looking for, and it was all rather frustrating to figure out which was the right widget to accept certain properties. It turns out you can't just slap random margins onto things and have it work, like I'm used to from CSS. In fact, I wrote dozens of lines of "bottomMargin: units.gu(2)" or "height: childrenRect.height + units.gu(2)" in various places, and most had no discernable effect at all. So it seems Qml's layout model is quite sensitive to having the margins be in the "right" places, but so far I haven't figured out which ones are the right ones. It's all just guesswork...
Based on what I saw, it did seem as though you had a fairly logical layout for how your widgets were organized, but yeah, documentation would be nice.
Thanks Ken!
Looks great!