Qt creator does it for you, just add whatever APIs you need (Android SDK, NDK) or xCode and select the plaftorm above the big Run button in QtCreator.
Launch the Maintence tool, download Qt for the target platform
AFAIK, it is free on Mobile. However... as I've repeatedly stated that I continually find bugs/parity issues between mobile platforms. Having a support contract really helps in this regard. The diffs are not large, but if you're new to a platform, you might not find it as friendly as you'd like. I routinely hack Obj-C and Java to make things work in Qt that should "just work". But getting clued into these foreign platforms can be frustrating. You've got to know a little "too much" about the target platform - For iOS it's your Application Delegate and Obj-C, on Android it's the Activity and JNI.
But most simple apps are as easy as just changing the build target. When it doesn't work, I file a bug. Example: You can take pictures (Camera.capture()) on iOS without a VideoOutput, but you can't do that in Android so you create an invisible one as a work-around. https://bugreports.qt.io/browse/QTBUG-73237 Or that audioRoles are not implemented on the platform. https://bugreports.qt.io/browse/QTBUG-73316 (iOS)
https://bugreports.qt.io/browse/QTBUG-73119 (FIXED, Android) (iOS has a global autio context, so this is less of an issue there, but Android does not, so it's a bigger issue) but the whole diff for Android was 445 lines which is not much. (and the bulk of those lines is enumerating the various audioRole mapping to/from Android)
Sometimes it's just not possible (no iOS API for AmbientLight sensor)
As long as you're not digging too much into the platform Qt *will* *just work*. :-)
Sent: Tuesday, February 19, 2019 at 8:39 PM
From: "ich" <a...@golks.de>
To: No recipient address
Cc: interest@qt-project.org
Subject: Re: [Interest] Fwd: vs. Flutter
From: "ich" <a...@golks.de>
To: No recipient address
Cc: interest@qt-project.org
Subject: Re: [Interest] Fwd: vs. Flutter
OK, i've no idea about how to deploy to mobile devices,
but what makes you think its not free?
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet._______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
but what makes you think its not free?
Am February 19, 2019 7:30:23 PM UTC schrieb Sylvain Pointeau <sylvain.point...@gmail.com>:
Qt is free on desktop, but it is not free on mobile, which is a real showstopper for me and many others.Le mar. 19 févr. 2019 à 20:12, ich <a...@golks.de> a écrit :Qt is free, too._______________________________________________Am February 19, 2019 7:04:03 PM UTC schrieb Sylvain Pointeau <sylvain.point...@gmail.com>:I cannot get it copied in the email, but the code in the section get started has no "new" but I agree with you that it is not "declarative"The positive points about flutter is that it is free, and intellij (IDEA) is so great.However, it feels too young, and limited to mobile (some are saying that the desktop is coming, but nothing concrete yet)react native (via react xp) seems to be a better alternative for now.Best regards,SylvainLe mar. 19 févr. 2019 à 19:43, Jason H <jh...@gmx.com> a écrit :It's still on the home page: https://flutter.io/ "Fast Development"I operate on the "read at least the first page" premise. That whatever they think is most important should be found there.But losing new doesn't really change my opinion of if it's declarative or not.Thanks for the update/correction though.Sent: Tuesday, February 19, 2019 at 1:34 PM
From: "Sylvain Pointeau" <sylvain.point...@gmail.com>
To: "Qt Project" <interest@qt-project.org>
Subject: [Interest] Fwd: vs. Flutterthe "new" is now removed in dart 2.0 so you example is outdated._______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest---------- Message transféré ---------
De : Jason H <jh...@gmx.com>
Date : mar. 19 févr. 2019 à 19:25
Objet : Re: [Interest] vs. Flutter
À : Bernhard B <schluc...@gmail.com>
CC : <inter...@lists.qt-project.org>I'm in your offtopic camp.Everything is going Declarative. I really hate that web devevlopment requires the use of HTML/CSS/JS (that's just client side) and some Framework of the Month. The _javascript_ kiddies love inventing frameworks for fame and profit rather than picking one and making it better. Fragmentation is rampant. On top of that JS is slow to change, it just becomes a runtime that your flavor-of-the-month framework compiles down to, well until WebAssembly.Rene, I don't understand why you don't declare Flutter Declarative? From the Flutter home page:Widget build(BuildContext context) {return new Scaffold (appBar: new AppBar ( title: new Text (widget.title), ),body: new Center (child: new Text( "Button clicked" ...),),}Good luck typing 'new' and 'return' a lot. At least QML manages that for you. QML is the sleekest of all the declarative languages.Sent: Tuesday, February 19, 2019 at 12:55 PM
From: "Bernhard B" <schluc...@gmail.com>
To: "Bob Hood" <bho...@comcast.net>
Cc: "René Hansen" <ren...@gmail.com>, "Jason H" <jh...@gmx.com>, inter...@lists.qt-project.org_______________________________________________
Subject: Re: [Interest] vs. Flutter> I've been studying it for a while now, and I've decided that it will likely be
my mobile development language. I love Qt to death for desktop, but I've
never been able to take to it's declarative approach. I know others swear byit, but it just never fit my brain waves for some reason.<offtopic>I guess I am one of those persons, who absolutely LOVE Qt's declarative language.I like QML so much, that I even started looking for QML -> HTML/CSS translators. While I really like QML,I absolutely hate HTML and CSS (never got used to its quirks). I mean there are some attempts likeqmlcore (https://github.com/pureqml/qmlcore), but I haven't tried those yet.</offtopic>Am Di., 19. Feb. 2019 um 18:47 Uhr schrieb Bob Hood <bho...@comcast.net>:On 2/18/2019 7:40 AM, René Hansen wrote:
> I've not come across any myself, and have only built a few small things with
> it a bit for now.
>
> Initial reactions was that it is *leagues* ahead of Qt with regards to
> developer experience. You're not locked to an IDE, like with QtCreator, and
> the ui live updates across device, simulators, emulators etc. when you write
> changes. No need to build and .apk and wait for a build+deploy.
>
> There's no JS involved. It's Dart all the way. It doesn't even ship with a
> web runtime afaik.
I've been studying it for a while now, and I've decided that it will likely be
my mobile development language. I love Qt to death for desktop, but I've
never been able to take to it's declarative approach. I know others swear by
it, but it just never fit my brain waves for some reason.
I saw somebody in this thread moan about it being yet another language to
learn. Putting aside the fact that a robust developer should know more than
one, Dart is quite familiar to anybody who has used a modern scripting
language (e.g., Python).
For me personally, Flutter's "feel" just fits mobile better in my mind than Qt.
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet._______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
