If splitting your application into multiple activities is not appropriate, there is nothing forcing you to do that. It is perfectly fine to use a single activity and change the view it is displaying. You just won't be able to take advantage (at least not easily) of many of the componentization features that activity provides, and you will need to do some of your own work in remembering your state in onFreeze() and restoring it in onCreate() (starting with the correct view displayed), handling the back key, etc.
Definitely do NOT pass argument kinds of data between activities using statics. One good rule to keep in mind: if your app goes to the background, and gets killed to give more memory to the foreground app, then when the user returns to it all of the statics will be reset, only the -front- activity is created, and the other activities will be created in reverse order as the user steps back through them. On Mar 24, 11:17 am, Raja Nagendra Kumar <[EMAIL PROTECTED]> wrote: > Hi, > > Looking for any good documents and support from expects to understand > google desing on intents and why each screen should be created using > activities. Why google not go with user creating a view object and > showing it (like in j2me). > > One thing I understand that each activity could run in different vm's > etc.. However if I could tell my application to run only in one vm, > can't avoid one activity for each screen. I am not feeling very > comfortable with data passing between the activity creations.. > > I tried one activity to other activity data though static variables > instead of passing them through intent extra.. etc.. this seem to > work.. however not sure when this could fail.. > > Regards, > Raja Nagendra Kumar, > C.T.Owww.tejasoft.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
