[Development] Qt Quick Controls for Embedded

[Nurmi J-P]

Hi Alberto,

> On 20 Apr 2015, at 15:43, Alberto Mardegan <mardy at users.sourceforge.net> wrote:
> 
> Hi Frederik,
> 
> On 04/09/2015 04:04 PM, Frederik Gladhorn wrote:
>> We want to give you the code, here it is :)
>> https://codereview.qt-project.org/#/admin/projects/qt-labs/qtquickcontrols2
> [...]
>> Feedback welcome!
> 
> If I understand correctly, these controls are intended to be a
> cross-platform set of controls with their own style, with the goal of
> being good looking and still have a good performance; the goal is not to
> wrap (or make them look alike) any of the platform native controls,
> unlike for example qtqmlandroid.
> Is my understanding correct?

Consider the “native” styling an open question. It has major implications on the architecture and performance.

> If so, it seems to me that the naming is somehow confusing: on one hand
> we have qtquickcontrols1, which provides a uniform API to render
> native-looking controls; on the other hand, the qtquickcontrols2 module
> seems to have a very different goal.

It’s just that the good old recipe does no longer give that shiny results. No matter how fancy ways we invent to extract native assets, the native feel is always off. Attila had very good insights on this subject in the "QML bindings for native Android controls” thread.

> Maybe this qtquickcontrols2 module should be renamed to something like
> qtquickembedded, to avoid giving the false impression that is meant to
> supersede the existing module?

Nothing is set in stone at this point. Trust me, we have spent an enormous amount of time discussing the name and going back and forth… :)

> And will qtqmlandroid eventually be merged into qtquickcontrols1, once
> it's ready?

The QML for Android playground project is unlikely to be merged with Qt Quick Controls. It’s not using or even compatible with Qt Quick.

--
J-P Nurmi