[Development] QML bindings for native Android controls

Jeremy Lainé jeremy.laine at m4x.org
Tue Apr 14 18:14:57 CEST 2015


On 04/13/2015 03:46 PM, Nurmi J-P wrote:
> On 13 Apr 2015, at 14:50, Jeremy Lainé <jeremy.laine at m4x.org> wrote:
>
>> How about just "android-controls", which would become
>> "qt-android-controls" if the project graduates from playground?
> I like this suggestion. In the end we will have much more (*) than just UI controls, though. Does that matter from the naming perspective?
>
> *) For example, good background service integration is important for my own use cases. Pretty much the same way WorkerScript works, I hope to be able to send arbitrary jsobjects between background services and UI instances.

Another option is "quick-android", which would become "qt-quick-android".

Cheers,
Jeremy



More information about the Development mailing list