No information about Android

by [EMAIL PROTECTED] » Tue, 24 Jun 2008 22:24:21 GMT

Sponsored Links

I just knew the Android project ... there is a lack of information ...
Google should post news in the magazines once a Week or two about

As a programmer, people only will go with Android if there is a
business to be exploited. Google should go for professionals, offer
professional advice, tools and make learn how enterprises can gain
money with its product.



Other Threads

1. No Build option in the New Android Project dialog Box in the Eclipse IDE


I am trying to build my first project for Android platform using the
Eclipse IDE.

The problem I am facing is that there is no option under the "Build
Target" label in the New Android Project dialog box. And, hence I am
not able to proceed beyond this dialog box (as the "Next" button is

The online documentation says, "Under Target, select an Android target
to be used as the project's Build Target. The Build Target specifies
which Android platform you'd like your application built against."

Could anyone tell me how to bring options under "Target" label.

I am using Eclipse 3.5 (Galileo) and have installed latest Android SDK
as well as all Android Platform components.

The  screenshot of the dialog box is available at :

Thanks for any assistance that you can offer.



2. Android architecture.. better for one activity over multiple?

Hi all,

I've been learning Android.. almost done with my 3rd book now.. have a
pretty good idea of the beginner things like the life cycle, etc. One thing
that kind of perplexes me is the benefits of using multiple activities each
with their own lifecycle events in them. In a normal Swing, or other UI
based app,  you usually have a single class with events to handle create,
start/stop, pause/resume, destroy, etc. From that class you can spawn
threads to do the work, change the UI, etc etc. With Android, it seems that
apps have potentially many activities. Maybe I am doing something wrong, but
each time I open a new activity represented by a new class.. that Activity
"takes over" the event processing of the app. So each and every Activity
class requires all the event methods.. just in case a user happens to hit
the BACK button at one stage of my app over another. I know I can put the
common save/load routines into a base class that extends Activity, and have
all my activites extend it.. which is probably what I will do.. but it seems
strange to me that each dialog, every screen, etc is it's own activity and I
more or less need to duplicate the code to handle pause/resume, start/stop,
etc events for each activity in case it's the one running. If I have a
splash activity that starts the main screen, then the user goes to high
scores, I have to handle the events for pause/resume, etc.. and so forth for
every screen in my game, or app. Is this what most everyone is doing? OR am
I missing the boat on this issue and there is a better way to allow say, a
single Activity to handle the full app lifecycle events from Android, and
spawning other activities ignore all those things.. knowing that the main
app activity handles the issue of saving/restoring data if need be?

Please, enlighten me if I am missing something on this. Seems like a lot of
extra coding to build what seems to be a normal Android app. Again, I
realize I can copy/paste, or subclass Activity and extend my own "common"
Activity.. I am just wondering what many of you are doing out there for this



3. Nexus One is HUGE!

4. Setting apn

5. opencore crashes on mydroid-donut emulator

6. about android_power

7. libwebcore - Broken Pipe