Merge lp:~tpeeters/ubuntu-ui-toolkit/100-SectionBar into lp:ubuntu-ui-toolkit/staging
| Status: | Merged |
|---|---|
| Approved by: | Zsombor Egri on 2015-06-17 |
| Approved revision: | 1564 |
| Merged at revision: | 1535 |
| Proposed branch: | lp:~tpeeters/ubuntu-ui-toolkit/100-SectionBar |
| Merge into: | lp:ubuntu-ui-toolkit/staging |
| Diff against target: |
835 lines (+732/-0) 12 files modified
components.api (+4/-0) examples/ubuntu-ui-toolkit-gallery/Sections.qml (+47/-0) examples/ubuntu-ui-toolkit-gallery/WidgetsModel.qml (+5/-0) modules/Ubuntu/Components/1.3/Sections.qml (+101/-0) modules/Ubuntu/Components/Themes/Ambiance/1.3/SectionsStyle.qml (+119/-0) modules/Ubuntu/Components/qmldir (+1/-0) tests/autopilot/ubuntuuitoolkit/__init__.py (+2/-0) tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/__init__.py (+2/-0) tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_sections.py (+49/-0) tests/autopilot/ubuntuuitoolkit/tests/custom_proxy_objects/test_sections.SectionsTestCase.qml (+42/-0) tests/autopilot/ubuntuuitoolkit/tests/custom_proxy_objects/test_sections.py (+51/-0) tests/unit_x11/tst_components/tst_sections.qml (+309/-0) |
| To merge this branch: | bzr merge lp:~tpeeters/ubuntu-ui-toolkit/100-SectionBar |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Approve on 2015-06-17 | |
| Zsombor Egri (community) | 2015-05-28 | Approve on 2015-06-17 | |
| Tim Peeters | Needs Fixing on 2015-06-17 | ||
|
Review via email:
|
|||
Commit Message
Introduce the new Sections component.
Description of the Change
Introduce the new Sections component.
This component will be used (in a following MR) in the new header to replace the sections selector in the current header divider. Sections will also be available as a separate component for convergence apps that need to place the Sections outside of the single standard header.
- 1534. By Tim Peeters on 2015-05-28
-
docs
- 1535. By Tim Peeters on 2015-05-28
-
docs
- 1536. By Tim Peeters on 2015-05-28
-
spacing
- 1537. By Tim Peeters on 2015-05-28
-
spacing
- 1538. By Tim Peeters on 2015-05-28
-
update components.api
- 1539. By Tim Peeters on 2015-05-28
-
docs
- 1540. By Tim Peeters on 2015-05-28
-
remove empty functions from tst_sections
- 1541. By Tim Peeters on 2015-05-28
-
sections
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1541
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Tim Peeters (tpeeters) wrote : | # |
38 +/*!
39 + \qmltype Sections
40 + \inqmlmodule Ubuntu.Components 1.3
41 + \ingroup ubuntu
42 + \since Ubuntu.Components 1.3
43 + \brief Display a list of sections that the user can select.
44 + */
> Zsombor Egri (zsombi) wrote 7 hours ago:
> Shouldn't you have more to say here?
Yes I can extend it a bit.
45 +StyledItem {
46 + id: sections
47 + style: theme.createSty
> Zsombor Egri (zsombi) wrote 7 hours ago:
> This is wrong, once the styleName will get into staging, this will be broken. Please merge with
> styleName MR and fix this. With a small luck, we will get it soon if LP gets it.
Ok, will do. I thought I would land my MR before you land yours. ;)
48 +
49 + /*!
50 + List of strings that represent section names. Example:
51 + \qml
> Zsombor Egri (zsombi) wrote 7 hours ago:
> Hmm.... I was thinking shouldn't this be rather a list of actions? Then you don't need the
> model and the selectedIndex properties separated. The Action would drive the visual (you
> would also be able to show icons if design changes his mind - with the current setup an API
> change would be needed) and the trigger would tell which Action is selected. I feel we have
> to discuss more about this.
Ok. After our discussion, I'll make this a list of actions and keep the selectedIndex as well. Changing the selectedIndex will trigger the appropriate Action.
137 + Row {
138 + id: sectionsRow
> Zsombor Egri (zsombi) wrote 7 hours ago:
> Aren't the sections proportionally filling the space? What if a text exceeds the
> space available?
No. In the new designs, the sections are always aligned left and don't fill the space.
If the text exceeds the available space, the section list will be scrollable. I will add the scrolling in a following MR.
150 + AbstractButton {
151 + id: sectionButton
> Zsombor Egri (zsombi) wrote 7 hours ago:
> I feel like this should be rather that FlatButton instead...
We don't have a FlatButton yet. I think the AbstractButton is fine here, since the visuals are quite specific for the section selector.
399 + def test_click_
400 + error = self.assertRaises(
Zsombor Egri (zsombi) wrote 7 hours ago:
> Why do you need this? Can't you cover this in unit test?
It does not test component functionality, only verifies that the CPO works as expected.
- 1542. By Tim Peeters on 2015-06-01
-
sync staging
- 1543. By Tim Peeters on 2015-06-01
-
use styleName in Sections
- 1544. By Tim Peeters on 2015-06-01
-
extend docs a bit
- 1545. By Tim Peeters on 2015-06-02
-
use Actions instead of strings for the model
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1545
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
- 1546. By Tim Peeters on 2015-06-02
-
changing selectedIndex triggers Action.
- 1547. By Tim Peeters on 2015-06-02
-
update components.api
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1547
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
- 1548. By Tim Peeters on 2015-06-02
-
sync staging
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1548
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Zsombor Egri (zsombi) wrote : | # |
/tmp/buildd/
/tmp/buildd/
Makefile:289: recipe for target 'docs' failed
- 1549. By Tim Peeters on 2015-06-05
-
fix docs
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1549
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Tim Peeters (tpeeters) wrote : | # |
Ready for another review.
Note that Page.head.
Do we want to break that API and replace it with a list of Actions?
| Zsombor Egri (zsombi) wrote : | # |
> Ready for another review.
>
> Note that Page.head.
> /developer.
> s/
>
> Do we want to break that API and replace it with a list of Actions?
Do we break the API if we say that it can be either strings - in which case we have more work - or it also can be a list of Actions? I think not.
| Tim Peeters (tpeeters) wrote : | # |
Supporting both Actions and strings in PageHeadSections is problematic. Then in order to feed it to the Sections we need to convert the list of strings into a list of Actions. I don't see a simple way to do that in QML.
We can support strings and actions in Sections and PageHeadSections, and then inside Sections I'll have to support both in the Repeater. That is not difficult but I'd say it is a bit messy.
- 1550. By Tim Peeters on 2015-06-16
-
unit tests for list of strings as model
- 1551. By Tim Peeters on 2015-06-16
-
rename actions to model and support a list of strings as model
- 1552. By Tim Peeters on 2015-06-16
-
improve test app
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1552
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
- 1553. By Tim Peeters on 2015-06-17
-
split up unit tests
- 1554. By Tim Peeters on 2015-06-17
-
update components.api
- 1555. By Tim Peeters on 2015-06-17
-
merge staging
- 1556. By Tim Peeters on 2015-06-17
-
update docs
| Tim Peeters (tpeeters) wrote : | # |
Updated and ready for another review. The 'actions' property was renamed to 'model' and now accepts either a list of Actions or a list of strings. Docs and unit tests were also updated.
- 1557. By Tim Peeters on 2015-06-17
-
fix components.api
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1553
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:1557
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Tim Peeters (tpeeters) wrote : | # |
[10:55:46] <nerochiaro> timp: i am trying to use the Sections from your branch but when i follow the example and set actions to a list, like this "actions: [ Action { text: "A" } ]" QML gives me this error: "Cannot assign multiple values to a singular property"... any ideas why ?
[10:56:11] <nerochiaro> timp: if I create a list<Action> property and then assign it to the actions it works ok
- 1558. By Tim Peeters on 2015-06-17
-
fix
- 1559. By Tim Peeters on 2015-06-17
-
document actions/model
- 1560. By Tim Peeters on 2015-06-17
-
add Sections to the component gallery
- 1561. By Tim Peeters on 2015-06-17
-
clean tst_sections.qml
- 1562. By Tim Peeters on 2015-06-17
-
update components.api
- 1563. By Tim Peeters on 2015-06-17
-
update docs
- 1564. By Tim Peeters on 2015-06-17
-
fix docs
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1558
http://
Executed test runs:
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:1564
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

FAILED: Continuous integration, rev:1539 jenkins. qa.ubuntu. com/job/ ubuntu- sdk-team- ubuntu- ui-toolkit- staging- ci/1814/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 3007 jenkins. qa.ubuntu. com/job/ ubuntu- sdk-team- ubuntu- ui-toolkit- staging- vivid-amd64- ci/542 jenkins. qa.ubuntu. com/job/ ubuntu- sdk-team- ubuntu- ui-toolkit- staging- vivid-armhf- ci/544 jenkins. qa.ubuntu. com/job/ ubuntu- sdk-team- ubuntu- ui-toolkit- staging- vivid-armhf- ci/544/ artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ ubuntu- sdk-team- ubuntu- ui-toolkit- staging- vivid-i386- ci/541 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 2561 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 3005 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 3005/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 20824
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/ubuntu- sdk-team- ubuntu- ui-toolkit- staging- ci/1814/ rebuild
http://