** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1566778
Title:
Documentation on anchoring and PageHeader is confusing
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
It is not very clear how one is best to have, for example, a Page with
a PageHeader and a ListView, and have the ListView take up the whole
page.
Page {
header:PageHeader {}
ListView {}
}
This has changed quite a lot in different versions of the UITK --
should the ListView be set to anchors.fill: parent? Or anchors.top:
page.top? Or anchors.top: pageheader.bottom? Should Page.flickable be
set to the ListView, or will that be set automatically, or is it
deprecated in favour of PageHeader.flickable, and does that have to be
set explicitly or will it be set automatically? Should one set the
ListView to anchors.fill:parent with a topMargin of pageheader.height
as the UITK gallery does?
It would be very useful to have a series of examples with diagrams
showing how to achieve various standard effects, for example:
1. a page with a header and a listview, where the listview takes up the whole
page and the header scrolls away as the listview is scrolled
2. a page with a header and a listview, where the listview takes up the whole
page and the header does not scroll away but stays fixed
3. a page with a header and a button which stays fixed under the header, and
a listview which takes up the rest of the page and scrolls
etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1566778/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
