Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

If one plans to release this for mobile devices, such as android phones or
iphones I would try and keep the language in c/c++ as both platforms can
compile those languages.

This seems fairly clueless to me.

Clearly an Impress remote control app will consist of mainly GUI code.
Not a whole lot of text or image processing, number crunching or other
"business logic" going on in such an app. The GUI APIs for Android and
iOS are different, and neither has C++ bindings (although the
Obejctive-C of iOS can be mixed just fine with C++ code, i.e.

The shared code would be the communication with the LO program, and
even there the underlying platform APIs that it makes sense to use
might be quite different. (If plain Berkeley sockets is what ends up
being used, that API is of course mostly the same on both.)

Android uses the NDK to compile code for android devices with out massive
rewriting of it into java,

Yeah, but that is true only for non-interactive code, it excludes GUI
related stuff, where to look like a "normal" Android app, one
definitely should use Java. As far as I understand, "pure" C/C++ apps
for Android are typically 3D games with (as is common for games also
on desktop platforms) homegrown GUI concepts that look and feel
different for each game family or producing company. (I put "pure" in
parens because, from following the ndk mailing list, it seems to be a
common misconception that no Java at all would be involved in such an
Android app. That is not true. There is a Dalvik virtual machine also
in such app processes, and a fair amount of Java code involved. It's
just OS-provided Java code, not from the app package.)

Anyway, I thought this mailing list was purely for the non-coding aspects?


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.