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


First of all thanks for your answer

On Fri, Mar 25, 2011 at 2:42 AM, Michael Meeks <michael.meeks@novell.com>wrote:

Hi Korrawit,

On Fri, 2011-03-25 at 12:53 +0700, Korrawit Pruegsanusak wrote:
       Personally (what with time-to-market etc.) I think we should
target the
latest android API version - ie. API level 9 - which gives us a lot of
nice (pre-wrapped) C APIs for talking to the system.

Shouldn't we use the lastest API level 11, of Android 3.0 platform?
Details at http://developer.android.com/sdk/android-3.0.html

        You're right - it's not the latest API level ;-) but it is the
latest
API level mentioned in the latest NDK you can download (my mistake). It
is also the case, that I only have a device running 2.3.3
(personally) ;-) so I'm biased.

       Its not clear to me that 3.0 gives us a lot more in the area of
basic
event handling / rendering too; clearly if there is something that makes
our job far easier there then we should use it, otherwise I'd prefer to
see 2.3.0 used personally :-)

       ATB,

               Michael.


After some research it's true that the 3.0 API would be great as it provide
interesting new features, like copy/paste and better keyboard support, but
it's not really widely use (at least for now) and the same goes for 2.3.3 so
wouldn't it be better to use 2.2.x instead so more people could use it ?


Cheers
Maxime

Context


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.