On 12 Nov 2012, at 21:40, Shawn Rutledge wrote: > Anyway there is some duplication of effort - Bogdan, Eskil, you and Samuel, > at least. (All I've done so far is test them.) So maybe it's better to sync > everything up and see what are the missing pieces?
I guess that is the best way to go ... I don't know about the other work that has been done, so I'll list the main features of what I've got: - Integration in the QPA framework (normally without real issues, thanks to Laszlo). - Event handling completely using NDK functionality (keyboard event handling is limited due to NDK limitations). - Very few changes to the qt code needed. One extra static module that provides the native activity callbacks. - Launching intents via QDesktopServices. - QML, QGLContext, QBackingstore drawing is stable. - QInputInterface for the android soft-keyboard. - Very basic java class loader (which I configure via a CMake build framework) and what I haven't got: - "special" intent actions (like starting a phonecall, should be easy to add to the QDesktopServices code in the plugin) - multimedia plugin - sensor plugin (I have one in development, but I read QtSensors is being put on hold?) - native widgets other things I would like for the android port: - Little or no difference in code between android and desktop platforms. - Easy integration in a CMake build framework. - Transparent handling of state saving/restoring. Greetings, Walter > > > On 12 November 2012 20:46, Walter Horsten <[email protected]> wrote: > It does! Splendid, this solves all the static initialization and > plugins-not-unloading issues involved with the app restart. > I can probably spend some time on updating the event handler to generate the > proper events later this week. > > Thanks for the tip! > > On 12 Nov 2012, at 15:45, Laszlo Agocs wrote: > >> >> Hi, >> >> It misses screenSize. >> android:configChanges="orientation|screenSize|keyboardHidden" should work. >> >> Cheers, >> Laszlo >> >> >> >> On Mon, Nov 12, 2012 at 3:15 PM, Walter Horsten <[email protected]> >> wrote: >> Hi all, >> >> I don't think this works very well (or at all) with NativeActivity at the >> moment, I put "configChanges:orientation" in the manifest, but android >> insists on restarting the NativeActivity ... for example: >> >> <activity android:name="android.app.NativeActivity" >> android:label="@string/native_activity_name" >> android:configChanges="orientation|keyboardHidden"> >> <!-- Tell NativeActivity the name of our .so --> >> <meta-data android:name="android.app.lib_name" >> android:value="qtqpatest"/> >> </activity> >> >> Or am I missing something? >> >> Regards, >> Walter >> >> >> >> On Mon, Nov 12, 2012 at 1:33 PM, <[email protected]> wrote: >> On Android it is possible to handle display orientation by yourself, not >> using the default behaviour of destroying and recreating the UI. >> >> You’d use OrientationEventListener & Display classes to detect the >> orientation then. >> >> This would make sense for a QML application where the scene graph can handle >> rotation of elements. >> >> >> >> The android:configChanges element in the manifest file is used to specify >> what things the application can handle itself. >> >> >> >> See also >> http://developer.android.com/guide/topics/resources/runtime-changes.html >> >> -- >> >> >> This message is for the designated recipient only and may contain >> privileged, proprietary, or otherwise private information. If you have >> received it in error, please notify the sender immediately and delete the >> original. Any other use of the e-mail by you is prohibited. >> >> Where allowed by local law, electronic communications with Accenture and its >> affiliates, including e-mail and instant messaging (including content), may >> be scanned by our systems for the purposes of information security and >> assessment of internal compliance with Accenture policy. >> >> ______________________________________________________________________________________ >> >> www.accenture.com >> >> >> _______________________________________________ >> Development mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/development >> >> > > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development > >
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
