← Back to team overview

touch-packages team mailing list archive

[Bug 1349426] Re: Introduce FlickablePage and ListViewPage components

 

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: New => Triaged

-- 
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/1349426

Title:
  Introduce FlickablePage and ListViewPage components

Status in Ubuntu UI Toolkit:
  Triaged
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Triaged

Bug description:
  FlickablePage and ListViewPage are intended to be used instead of the
  current Page with a Flickable or ListView as Page.flickable. Having a
  FlickablePage/ListViewPage will be less confusing for the developer,
  and it makes things easier to implement (with less hacks/workarounds
  in detecting and updating the Page.flickable item).

  Currently in Page we try to detect a Flickable or ListView and
  depending on its anchors and settings we change its topMargin to take
  our application header into account.

  Introducing FlickablePage and ListViewPage makes it easier to set
  default properties of the Flickable and ListView, and allows us to
  control which of the Flickable/ListView parameters the app developers
  can override. We can use it, for example, to define an optimal
  horizontalVelocity of the Flickable depending on the number of grid
  units on the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1349426/+subscriptions