touch-packages team mailing list archive

[Zsombor Egri <1508363@xxxxxxxxxxxxxxxxxx>]

Victor,

You are right, there is one header per application. Which means that all
pages in an application use that header. However that would be broken
when you'd use the AdaptivePageLayout, which has as many headers as
columns. Therefore we are preparing to move the header in the page, so
each page will get a header of its own. Yet we have both solutions in
place, thats' why you still see a header even if you don't set one on
the Page.

So, in the future of 1.3, you will have to set the header of the page
yourself. Which means there will be as many headers as many pages
require one. The one from MainView will disappear once we finish all the
work we have for the header and its subcomponents.

When you say "With the updated imports to UITK 1.3 we are unable to do
things like the following: edgeLoader.item.flickable.contentY =
-page.header.height" - I am sorry to say that the Page.header property
was never documented, and used for private purposes. We do not promise
any compatibility for private or undocumented properties, especially
when the property comes from a super type, which is also internal.
Whilst it is a regression, switching to 1.3 would anyways require you to
go with the way I described before - specifying the header for your page
within the page.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1508363

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
     Ubuntu.Components 1.3
     Ubuntu.Components.ListItems 1.3
     Ubuntu.Components.Pickers 1.3
     Ubuntu.Components.Popups 1.3
     Ubuntu.Components.Styles 1.3
     Ubuntu.Components.Themes 1.3
     Ubuntu.Components.Themes.Ambiance 1.3
     Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
     Ubuntu.Layouts 1.0
     Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+subscriptions