Re: [android-developers] Petitions to Google

Making petition to make us do something is an absolute waste of time.

Filing reasonable feature request (http://b.android.com) with a
concise explanation why the feature is needed has a much better chance
of success.

Contributing is even better! See the new http://source.android.com and
be aware that the dev tools development has moved 100% to the open, so
you can see real time what we're doing.

On Wed, May 19, 2010 at 2:41 PM, blackbitshines@googlemail.com
<blackbitshines@googlemail.com> wrote:
> I think Google should make an effort to improve the android developer
> tools. Here I write some things I think need to take in account:
>
> - Fix problems of communication between IDE and emulators

Yes this is annoying.

> - Add support to conditional compilation #IF,#ELSE,#ENDIF (I wan't to
> have 2 versions in the same proyect ... beta and non beta, free and
> paid, etc.)

Free and paid apps shouldn't be done by a preprocessor for several
reasons: You want to change the content of XML file. an XML
pre-processor is going to be harder. Also you probably won't have the
same files at all and a pre-processor won't really let you
exclude/include whole files.

We will introduce a new build mechanism that will allow you to easily
share code and resources across 2+ application projects that will be
much better at handling this case.

As for the beta vs. final version, yeah, as someone else said, this
makes no sense.

> - Add support to add custom views to viewlist in IDE

We're working on a new layout editor that will allow that and more.

> - Is there any way to add voice recognition? It is a feature that I
> would love to have to experiment with, but I can't since I don't have
> an Android mobile yet. I would REALLY love to have it.

I think voice recognition is google specific and requires google
components that are not (and won't ever be) on the SDK system image.

> - Add support to C/C++ by adapting the eclipse or using another IDE. I
> feel guilty for wasting so many resources by using an intermediate
> code. I would not like to have a 1GHz processor and use it as if it
> where a 100MHz. And yes, leakage memory problems in C, C++ ... it is a
> problem, but it is worth the effort, and having in count how much code
> there is for C/C++

Yes, better integrating the NDK into the SDK, and into the Eclipse
plug-in is one of our goals.

> - I would be nice that I could use the camera of my Computer in the
> emulator :)

yes, it would be nice, wouldn't it?

> PS. If you agree sign up please or add things you see it would be
> useful to have.

Again, no don't sign up petitions. All it does is noise on the
(already too noisy) mailing list and we'll ignore it anyway.

Xav
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.

Please do not send me questions directly. Thanks!

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en