Yup, his real name was 1.0, he's a changed person now!
... Qt Creator is simply amazing. I've been using it on debian/windows/osx to create some custom C++ Qt widgets (have been learning Qt for about a year), and it's very fluid to use.
I even got the Windows Debugging working (through cdb.exe found in the Windows SDK -> DDK package).
Qt Creator can now use libclang for its code completion. In addition, it can use LLDB for debugging and clang-format for code beautifying. It is nice to see other open source projects adopting LLVM/Clang/LLDB!
Yes, I'm using Qt both on Android and iOS. Both work without glitches or quirks.
The same application I compile for Linux, Windows, OSX and Mobile Devices (only tablets, for big enterprise stuff) without significative changes on code (only a couple of #ifdefs for fullscreen and alike).
> Did you use one codebase to write the application?
Yes, only one codebase
> Do you need Mac OSX to compile for iOS or run emulator?
Unfortunately yes. I hope that in the future Apple will allow some sort of cross-compiling.
> Did you use C++ or is there a workaround to it?
Only C++ and Qt Widgets (no QML yet)
> Basically I'm hoping that new Qt can replace Intel XDK, RoboVM, Xamarin. However, the biggest hurdle is developing for iOS on a non-Mac machine.
It can replace (at least for my needs), but you will always need a Mac OSX to compile for iOS as far as I know (because of XCode dependency and licensing stuff)
Unreal Development Kit can deploy from windows to ios without buying a mac. I'm not sure if they made a deal with apple or if its possible without their approval.
I've been having fun writing apps in strict QML, intentionally. About every weekend I just take a traditional app use case and try writing it from scratch.
And surprisingly, the shortcoming is always documentation shortfalls. It took me digging through code samples to find out activeFocusItem is a thing, for example.
Just note you can't deploy QML only apps to mobile, you need a system with qmlscene installed already, but it is trivial to have a small C++ layer, and removing the JS only restriction gives you a huge amount more power over QML itself (building your own components in C++ vs combining them in JS).
My only... only wish for Qt Creator (and the Qt framework as a whole) is to have a docking systems much like Visual Studio - e.g. undock a widget allows docking with another - also put some guide roses instead of moving widgets.
Qt does have a docking system, but it is nowhere near as good as visual studio's.
For the application I am building (we are using PySide, the LGPL Python bindings for Qt), I planned a fairly elaborate docking/undocking system for a collection of user-generated plots. It seems to me Qt gimped docking so it only works for toolbars on the edges of a main window. You can't "promote" a widget to be the main, central widget through the docking mechanism.
If you are fully in python, then please take a look at http://github.com/nucleic/enaml - it requires few extra modules (kiwi in C++ which is cassowary constraint system for UI widgets), and atom (python + C++):
But it has exactly what Visual Studio has, and a bit more:
I've started porting this system to C++, but gave up after realizing how much I had to do (spent a week on it, and couldn't do more).
I've chose a much simpler (again written in python) system that has some missing features (does not keep proportions, and it's not visually that appealing) - but it works in general.
If one does not need technical support, one can use the open source edition on the desktop and on Android. On iOS one would need the commercial edition due to the restriction on dynamic libraries preventing the use of LGPL.
At least a couple of years ago it used to be around 2500 EUR / platform.
Minor but important detail: With the LGPL license version you must link against the Qt DLLs and cannot statically link Qt into the executable. If this is not a problem (and you don't modify Qt itself), then the LGPL version is absolutely fine for commercial, closed source applications.
Wish they'd spend some more time fixing some bugs. Since 2.2 they've been pretty much non-stop on new features for the next version, and rarely have they stopped to fix bugs in .1 releases. It's happened, but mainly for huge show-stoppers.
There are all sorts of general bug regressions which affect generic coding and editing since 2.5 which are mildly annoying but happen many times a day when coding, that in JIRA haven't been touched.
37 comments
[ 3.1 ms ] story [ 77.0 ms ] thread... Qt Creator is simply amazing. I've been using it on debian/windows/osx to create some custom C++ Qt widgets (have been learning Qt for about a year), and it's very fluid to use.
I even got the Windows Debugging working (through cdb.exe found in the Windows SDK -> DDK package).
There's a plugin for those who want to use Qt inside Visual Studio instead of using Qt Creator.
What does this llvm support mean?
The same application I compile for Linux, Windows, OSX and Mobile Devices (only tablets, for big enterprise stuff) without significative changes on code (only a couple of #ifdefs for fullscreen and alike).
Did you use one codebase to write the application?
Do you need Mac OSX to compile for iOS or run emulator?
Did you use C++ or is there a workaround to it?
Basically I'm hoping that new Qt can replace Intel XDK, RoboVM, Xamarin. However, the biggest hurdle is developing for iOS on a non-Mac machine.
Thanks!
> Did you use one codebase to write the application?
Yes, only one codebase
> Do you need Mac OSX to compile for iOS or run emulator?
Unfortunately yes. I hope that in the future Apple will allow some sort of cross-compiling.
> Did you use C++ or is there a workaround to it?
Only C++ and Qt Widgets (no QML yet)
> Basically I'm hoping that new Qt can replace Intel XDK, RoboVM, Xamarin. However, the biggest hurdle is developing for iOS on a non-Mac machine.
It can replace (at least for my needs), but you will always need a Mac OSX to compile for iOS as far as I know (because of XCode dependency and licensing stuff)
I use Qt StyleSheet extensively (globally) to mimick iOS lines & colors. Isn't hard, in fact, it is very easy to do.
I've been having fun writing apps in strict QML, intentionally. About every weekend I just take a traditional app use case and try writing it from scratch.
And surprisingly, the shortcoming is always documentation shortfalls. It took me digging through code samples to find out activeFocusItem is a thing, for example.
Just note you can't deploy QML only apps to mobile, you need a system with qmlscene installed already, but it is trivial to have a small C++ layer, and removing the JS only restriction gives you a huge amount more power over QML itself (building your own components in C++ vs combining them in JS).
For the application I am building (we are using PySide, the LGPL Python bindings for Qt), I planned a fairly elaborate docking/undocking system for a collection of user-generated plots. It seems to me Qt gimped docking so it only works for toolbars on the edges of a main window. You can't "promote" a widget to be the main, central widget through the docking mechanism.
But it has exactly what Visual Studio has, and a bit more:
http://nucleic.github.io/enaml/docs/examples/ex_dock_area.ht...
I've started porting this system to C++, but gave up after realizing how much I had to do (spent a week on it, and couldn't do more).
I've chose a much simpler (again written in python) system that has some missing features (does not keep proportions, and it's not visually that appealing) - but it works in general.
It's part of http://github/pyqtgraph/pyqtgraph
Example for Pyqtgraph - http://www.pyqtgraph.org/images/flowchart.png
I have translated this one, except that my (C++ ported) version is currently leaking memory, which eventually would get fixed.
Hope this helps!
I actually already use pyqtgraph extensively. Those plots I was talking about are pyqtgraph plots :)
Does anyone know what it costs to license QT creator for a single commercial developer targeting desktop and mobile platforms?
When I looked at their 'try and buy' page it says 'contact us'
At least a couple of years ago it used to be around 2500 EUR / platform.
There are all sorts of general bug regressions which affect generic coding and editing since 2.5 which are mildly annoying but happen many times a day when coding, that in JIRA haven't been touched.