Qt and ios : commercial ?
-
[quote author="q8phantom" date="1328797796"]
I'm using the sound engine from the QtGameEnabler, for games, it's important to have low latency sound!Anyways, I'll have a look at the source codes later
[/quote]In fact, the issues that I've found have been with QtGameEnabler's use of QtMultimedia (on iOS). I am working to get QtGameEnabler working properly on iOS. At the moment, the graphics work 100%, but there are lag and clipping issues with the audio.
-
That's great I am waiting for it.
[quote author="Qt4iOS" date="1328861589"][quote author="q8phantom" date="1328797796"]
I'm using the sound engine from the QtGameEnabler, for games, it's important to have low latency sound!Anyways, I'll have a look at the source codes later
[/quote]In fact, the issues that I've found have been with QtGameEnabler's use of QtMultimedia (on iOS). I am working to get QtGameEnabler working properly on iOS. At the moment, the graphics work 100%, but there are lag and clipping issues with the audio.
[/quote] -
licensing issue : http://wiki.qt-project.org/Licensing_talk_about_mobile_platforms
-
Let's discuss what if someone does not use webkit nor qml?
-
If I understand correctly, webkit is not issue because apple not allow qt webkit, ... but for Qml it's a big issue .. it's most appropriate for Ios interface than qt widget...
-
[quote author="qtnext" date="1328989484"]If I understand correctly, webkit is not issue because apple not allow qt webkit, ... but for Qml it's a big issue .. it's most appropriate for Ios interface than qt widget...[/quote]
Then, I won't have any problem, because I mainly use QGraphicsView, I'm not using QML at all!
-
-
The site for Mediator software is the same for long time now. It shows 10%. Please tell what is the current status.
-
The 10% refers to the completion status of the website, and not the software. The software has been 'market ready' for 6-8 months at least. There are customers using it commercially.
There is a gitorious repository (qt-ios-plaszma) which is actively maintained, that holds the latest source of the Qt 4.x library for iOS. The 'ios' platform plugin is closed-source and won't be found in that repository.
There is a new SDK (based on the Qt 4.8.1 OpenSource release) which will be released in the next few days. That version supports older devices (eg. iPhone 3G) with ARMv6 and GLES1 and newer devices (eg. anything after iPhone 3G) with ARMv7 and GLES2. The SDK is built as a 'Universal' binary, which can be used to either target a real iOS device or the iOS simulator. The new SDK has the Qt Mobility, Qt Quick3d and Qt GameEnabler add-ons built-in.
-
Do you have any approximate time when the site would be fully ready so that we can know pricing information etc ?
-
Qt4ios, while thinking about using Qt on ios, I like to know more about a few things. Does the Qt apps looks and perform like apps written using obj-c / cocoa touch ? For example, how will Qt widgets like button, check boxes ets looks on ios. Is it possible to create the same kind of animation effects using Qt on ios ? Does Qt multimedia offers the same level of functionality offered by ios apis like core audio ?
-
In fact I think there are lots of people who would want to seriously use Qt for developing iPhone applications for the appstore. The advantage is obviously to target multiple platforms with a single codebase. Imagine the current effort needed if we need to release the app on all major platforms like iPhone, Android, BlackBerry, Symbian, Maemo. Thanks for the effort and I would like to get further details like that asked by qtnext.
-
I noticed about a couple developers using QT to build Android apps, but none for iOS. Still a long way to go
-
I noticed about a couple developers using QT to build Android apps, but none for iOS.
Well, I develop an QML app for android and iOS, for example. Currently it is in TestFlight stage, the android version is already released. I use an individual GUI though. QtQuick Controls (or also QWidgets?) can mimic the android KitKat style, but there is only a very experimental lollipop "material" style yet .
I find it worse if an app has an GUI which tries to look&feel native, but is only reaching 85% at being native than and app which has an individual GUI. If you want to look&feel native, you have to go native on mobile. That's the deal IMO.