ubuntu-phone team mailing list archive

[Alberto Mardegan <alberto.mardegan@xxxxxxxxxxxxx>]

On 20/05/2016 18:45, Tim Peeters wrote:
> The reasons that we do this in 1.3 and not introduce 1.4 right now are
> the following:
> - Having 1.4 would not solve the problem.

It definitely would.

> APL is not performing good
> enough now, so you have to switch to 1.4 anyway.

It is performing well enough for people who are using it. People who are
not satisfied with it will move to 1.4.

> - UITK 1.3 is not feature complete yet (but we are getting close).

It's good enough for people who are using it now. When people will
decide they need new components, they'll move to 1.4.

> - Introducing a new version will require us to duplicate the qml files
> for the components and themes,

Use symlinks like the apparmor-easyprof-ubuntu project is doing. It's
actually a very good way of keeping track of what files have changed and
what file haven't.

> duplicate all the tests,

I don't think you should. At most, add a test which computes a checksum
of the 1.3 source tree and verifies that it never changes (in this way
you make sure that any modifications to it won't be accidental).

> and add an
> otherwise useless property to StyledItem to detect the correct version
> of the theme.

If it's necessary to maintain the API contract, it's not unnecessary. :-)

> - Updating the apps to 1.4 will be a lot of work but necessary if the
> apps want to use the convergence features.

The only additional work is replacing "1.3" with "1.4". And actually, I
wonder if you could avoid requiring it (with QtQuick, one can import 2.0
and 2.6 in the same app, and everything works fine).

> Because of all this, we better finish UITK 1.3 and then declare it as
> frozen and support it for a long time.

Wishful thinking. :-) 2.0 will be much better in all respects, and who
knows if design will want to revamp the components in the meantime.

You'll meet the same issues again and again, better start working on API
stability now than later. Unexpected changes will always occur, even
after 2.0 is released.

Ciao,
  Alberto