Dear PowerGUI
I will be very much interested to use the same , If available
****************************************************************************
****************************************************************************
*************************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
-----Original Message-----
From: android-internals@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of PowerGUI
Sent: Thursday, April 17, 2008 5:13 AM
To: Android Internals
Subject: [android-internals] Re: native (C++) SDK for Android is
definitively needed
Hello Eeverybody,
I am PowerGUI from Bejing China,I am focusing on Android C/C++ SDK,
I will release the first version within two weeks.
I wonder how many people want to use such sdk.if you need it or like
it,please
tell me.haha.If there are many people will use such sdk,I will fell
very happy,
and will do more work on that.
Best Regards
PowerGUI
----------------------------------------------------------------------
Love Android - Cann't Live Without Android Now
http://www.dotphone.org/english/
On 4月5日, 上午1时29分, David Given <[EMAIL PROTECTED]> wrote:
> Sean Kelley wrote:
>
> [...]
>
> > In other words, it does not seem very appealing to be required to
> > re-architect an SDL/Gtk+/fill-in-the-blank application to use the
Android
> > Java UI framework and then somehow re-partition the native code into
> > libraries that may or may not be easy to combine with JNI.
>
> Of course, they wouldn't run anyway because Android phones don't
> (AFAICT) have X. And even if you could you wouldn't want to do that
> because they wouldn't integrate with the Android UI and the result would
> be utterly horrible.
>
> *Any* application that has a UI will have to have a UI written, and
> designed for, Android. And that's almost certainly going to mean Java,
> because that's what it's written in.
>
> (It may be possible to wrap up all the JNI needed to call into the
> Android UI in, say, a set of C++ classes so that you can write a C++ app
> that used it; but it would be a repulsive amount of work and would
> probably be extremely brittle... and even then you wouldn't be able to
> subclass components, so you'd have to write Java code to receive
> callbacks. And, frankly, I don't see the benefit; you'll have to rewrite
> your UI to fit the Android framework anyway, so you might as well do it
> in the preferred language and save everyone a lot of time.)
>
> --
> David Given
> [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Internals" group.
To post to this group, send email to android-internals@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-internals?hl=en
-~----------~----~----~----~------~----~------~--~---
