Thread Previous • Date Previous • Date Next • Thread Next |
On Friday, May 20, 2016 3:19:00 AM PHT, Tim Süberkrüb <tim.sueberkrueb@xxxxxx> wrote:
Hi Zsombor, thanks for your reply. I'd then like to request a better policy for such changes.When I asked about click frameworks some time ago, I was told that they are meant to keep apps from breaking, each framework should be one fixed environment the app is targeting. But it looks like that's not true. I probably just didn't understand that correctly.But if it's not the framework versions, then at least the UI Toolkit version should be reliable IMO. As far as I know, UUITK 1.3 was released as a stable release, wasn't it? At least it's the current recommended release. Apps that target a specific UITK release should not just break over time until the release is officially announced as deprecated. At least that's my understanding of releases and version numbers :) I really don't like being forced to update my apps before I'm ready with my next release at least not because of changes like this.Also, I'm not following this mailing list actively. If there haven't been a message in the Ubuntu Apps telegram group, I would not even have realized this thing. And that doesn't mean I don't care. I love Ubuntu and the phone, that's why I'm writing apps for it! But I don't have unlimited time to do so. It's all my free time I'm spending here.Have a nice evening everyone, Tim Am 19.05.2016 um 20:34 schrieb Zsombor Egri:Hello Tim,As we are not making any new component, and we are targeting this work to happen with 1.3 UI Toolkit, apps made prior to 15.04.5 (or wherever this change will land) will stop working with pages using old header configuration setup. So if you have apps in the store which uses APL with old page header configurations, please update those.Cheers, ZsomborOn Thu, May 19, 2016 at 9:17 PM, Tim Süberkrüb <tim.sueberkrueb@xxxxxx <mailto:tim.sueberkrueb@xxxxxx>> wrote:Hey Tim, I was wondering whether this change does affect all frameworks? For example, will an app using the APL and targeting a prior 15.04.X framework release break because of this change or will only 15.04.5 apps be affected? Thanks for your reply! All the best Tim Am 19.05.2016 um 16:52 schrieb Tim Peeters:Hello all, As you probably know, some time ago we introduced the new PageHeader component (see https://developer.ubuntu.com/en/blog/2016/02/24/pageheader-tutorial/ ). An instance of PageHeader can be assigned to Page.header to define the header of a Page, and if no Page.header is specified, there is an automatic fallback to the old header. In AdaptivePageLayout (APL), there is also a fallback header in each column, but that complicates the APL implementation, it is not fully covered by tests, and does not support all the features of the new PageHeader, so we will drop support for that soon. We need to do this before we move the APL implementation to C++ (the API will be the same, so no more changes in app code will be needed for that, but the APL will be much faster), so pleaseupdate your apps now if you are using APL but not the new PageHeader.We may update the deprecated APL column-header fallback to show a red border before we remove it, as a final warning. The progress on the removal can be followed here:https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1583587Comments/suggestions/discussion can be added to the bug report, or as a reply to this e-mail. Best regards, Tim.-- Mailing list: https://launchpad.net/~ubuntu-phone <https://launchpad.net/%7Eubuntu-phone> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx <mailto:ubuntu-phone@xxxxxxxxxxxxxxxxxxx> Unsubscribe : https://launchpad.net/~ubuntu-phone <https://launchpad.net/%7Eubuntu-phone> More help : https://help.launchpad.net/ListHelp
-- Sent using Dekko from my Ubuntu device
Thread Previous • Date Previous • Date Next • Thread Next |