Mobile and Embedded

You need to expose a QObject to QML context. Then you can run any method marked as Q_INVOKABLE and modify any Q_PROPERTYies that it has. Another option is to inherit from QQuickItem (QDeclarativeItem in your case) and expose methods there (same story: Q_INOVKABLE, QPROPERTY). Check out my CCF project - it's probably to complicated as an example, but there you go. qmlRegisterType lines register custom kids of QQuickItem, while lines 69-73 register standard QObjects. You can find base classes for those objects in "the repo":https://github.com/sierdzio/closecombatfree/tree/master/src.

[quote author="yurykosh" date="1369859362"]What about Mac OS installer for Android?[/quote] I just don't have MAC computer for MAC OS :-) For me, the best desctop OS - Wondows 7. Hey Qt developers, you're not difficult to do this, please add the Qt 5.1 for Android on Windows x64 installer, which works fine without bugs, that i see in Winx32 installer :-)

maybe this gives you an idea http://lists.qt-project.org/pipermail/android-development/2013-May/000114.html

Sorry, I can't help with that:( You could try to ask Nokia at http://developer.nokia.com/ . I am sure they have people knowledgeable about these technical details:)

Do you have a Qt version set up in your desktop kit (Tools>Options>Build & Run>Kits)? If not: Is there a Qt version defined in the Qt version tab next to the kits tab?

What is the ./configure options you have supplied? any info on chroot environment details? if you have built for arm target, you shall check with read elf libs to find readelf -a to find the details about lib. ex readelf -A libQt5Core.so.5.0.2 | grep "Shared library" to find the libs

Not familiar with Embedded System, but the topic seems related with Java and C/C++, maybe JNI could be a solution.(Java Native Interface call C/C++ or C/C++ initialize the JVM to call Java) refer to http://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/jniTOC.html

I read somewhere that Qt5, unlike Qt4, doesn't build to multiple platforms in one binary (in this case x86/arm, not sure whether it applies to OSes too), and then it clicked that the only binary for Mac builds to Mac x86 so I need to make my own for the iPhone (even the simulator). This page, specifically "Getting started" at the bottom, walks you through that process: http://blog.qt.digia.com/blog/2013/03/05/qt-for-ios-preview/

UPDATE: problem solved by updating env variables as shown below: export LD_LIBRARY_PATH=/usr/lib export TSLIB_TSEVENTTYPE=INPUT export QTDIR=/home/martin/Qt_E/qt-4.8.4_tslib/ export QWS_MOUSE_PROTO=tslib:/dev/input/event1 export TSLIB_CONSOLEDEVICE=none export TSLIB_FBDEVICE=/dev/fb0 export TSLIB_CALIBFILE=/etc/pointercal export TSLIB_CONFFILE=/etc/ts.conf export TSLIB_PLUGINDIR=/usr/lib/ts export TSLIB_TSDEVICE=/dev/input/event1 export QWS_DISPLAY=LinuxFB:mmWidth=800:mmHeight=480 I have not nailed down which exact line fixed it but I have a feeling the QWS_DISPLAY is the one.

You can only have one top-level item in a QML file, as stated in the "QML document overview":http://qt-project.org/doc/qt-5.0/qtqml/qtqml-documents-topic.html There are a few approaches you can take to implement multiple in-application screens: Define as many items as you want and toggle their visibility, simulating page transitions. Top-level item "states":http://qt-project.org/doc/qt-5.0/qtquick/qtquick-statesanimations-states.html might be useful to monitor these. This is the most straightforward solution, but it gets cumbersome with the application complexity growing. @Item { id: topLevelItem Rectangle { id: firstRectangle visible: true } Rectangle { id: secondRectangle visible: false } MouseArea { onClicked: parent.state = "second" } states: State: { name: "second" PropertyChanges { target: firstRectangle; visiblity: false } PropertyChanges { target: secondRectangle; visibility: true } } }@ Implement a "StackView":http://doc-snapshot.qt-project.org/qt5-stable/qtquickcontrols/qml-qtquick-controls1-stackview.html . With it, use different QML files for different pages you called screens and change to them by supplying the StackView with their URL. @Item { id: topLevelItem StackView { id: stackView initialItem: Qt.resolvedUrl("FirstRect.qml") } MouseArea { onClicked: stackView.push("SecondRect.qml") } }@ Use a "Loader":http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-loader.html element to load another QML file and change its source to another file when deemed necessary. Example on the documentation page.

@dexter256 I already find it, I have a not so new sdk so dx is still under platform-tools, it was the second case. Thanks anyway.

It was me who filed the bug, I'm glad you got it running. Cheers.

Yes we do that here.

Well, looking at the blog I am not 100% sure how the final outcome will be, I was looking into Qt to make IOS software. It seems you will still need to use Xcode to generate the final package (the apple dev environment), but what is not clear from the blog (to me anyway) is if we will have to develop on the apple Mac or if we can develop on any platform (i.e. windows / linux). To deploy your app you need to go via the Xcode route anyway you look at it. This involves setting up your device (iPad/iPhone) to enable dev apps to be installed..... probably best to have a look at youtube or other websites on how to deploy an apple app. Since Qt can't yet do all this I decided not to look much further into it yet...

There is no excuse for failing to read "the documentation":http://qt-project.org/doc/qt-4.8/properties.html first :) It's more than well covered there.

IIRC other language bindings also rely on Q_PROPERTY being present. E.g. if you want to export a Qt object into a javascript runtime.

Also i tryed following: Create folder icu4c-android cd icu4c-android git clone https://android.googlesource.com/platform/external/icu4c jni $NDK_ROOT/ndk-build And got errors: Android NDK: WARNING: Unsupported source file extensions in jni/i18n/Android.mk for module icui18n Android NDK: smpdtfst.h Compile++ thumb : icui18n <= dtptngen.cpp jni/i18n/dtptngen.cpp: In member function 'void icu_50::DateTimePatternGenerator::addICUPatterns(const icu_50::Locale&, UErrorCode&)': jni/i18n/dtptngen.cpp:420:68: error: 'dynamic_cast' not permitted with -fno-rtti jni/i18n/dtptngen.cpp:430:68: error: 'dynamic_cast' not permitted with -fno-rtti make: *** [obj/local/armeabi/objs/icui18n/dtptngen.o] Error 1 I suspect i need run configure script but how to do it to configure for android?