|
|
Home » Community » Coffee corner » Qt and Android...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Qt and Android... [message #28158 is a reply to message #28157] |
Thu, 19 August 2010 14:40   |
 |
kohait00
Messages: 939 Registered: July 2009 Location: Germany
|
Experienced Contributor |
|
|
i've successfully built the 'android-vnc-viewer' app from source, it runs on my emulated android. pretty impressive. now i'm trying to finish setup of my android sandbox making the NDK examples work. this is a bit hairy as it seems. as soon as this is running, i will provide a short descritioin on how to setup an android built environment, the information is available, but as always, the difficulties show up trying..especially NDK, which needs a cygwin for compiling the native source code into a library, which then will be linked when building the .apk android application itself.
another problem show up concerning the popup windows etc..they are TopWindow derived isn't it? so far, android app is an Activity which is merly a logic surface to place controls to and that can react on user interaction overriding several base class functions. so it's pretty much a Ctrl. but here, we wont be able to invoke popup windows that easy.. i think we will need the android means, if it has stuff like 'popup a surface and draw things on it while the rest is visible, blocking other stuff'.
what about the android look and feel? i am not that fit in creating the apropriate Ctrl.iml for android
|
|
|
|
Re: Qt and Android... [message #28163 is a reply to message #28160] |
Thu, 19 August 2010 17:25   |
 |
kohait00
Messages: 939 Registered: July 2009 Location: Germany
|
Experienced Contributor |
|
|
this should be possible somehow, though printf redirection is not that easy espacially to graphics...
an interesting topic is by the way the 'ContentProvider', means to storing and retrieving data from within application, basicly data, that should survive onPause() time, when a user quits your application to switch somewhere else (as far as i understand)
i think it is closely related to their account management
Quote: |
Content Providers
Content providers store and retrieve data and make it accessible to all applications. They're the only way to share data across applications; there's no common storage area that all Android packages can access.
Content providers are one of the primary building blocks of Android applications, providing content to applications. They encapsulate data and provide it to applications through the single ContentResolver interface. A content provider is only required if you need to share data between multiple applications. For example, the contacts data is used by multiple applications and must be stored in a content provider. If you don't need to share data amongst multiple applications you can use a database directly via SQLiteDatabase.
|
nice idea anyway, maybe upp could provide such an interface as well, this might reduce the need of Serialize persistance, but using SQL instead
[Updated on: Thu, 19 August 2010 17:34] Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Sun May 11 15:12:34 CEST 2025
Total time taken to generate the page: 0.03370 seconds
|
|
|