Well, my rule of thumb (being a web developer) is to think of it in terms of how many web pages I'd want == how many Activities I should break it up into. To me, seeing setContentView called multiple times in an Activity is a bit bothersome. I can't quite explain why I feel that. I guess because from a design point of view, it makes an Activity too "busy". Really, if it's a completely different screen (which sounds like your case), I think you should use an Activity.
On Apr 6, 5:35 am, Derek <[EMAIL PROTECTED]> wrote: > Hi, > > I'm writing an application with two screens. > Screen 1: Parameters settings > Screen 2: Display info (depending on parameters settings) > > I've used one Activity and two LinearLayout views to implement it. I > switch from screen 1 to 2 with setContentView(...) and it works fine. > However, in the Android documentation, I can see that using two > activity may be recommended. So, when should we use Activity ? Why not > using view ? > > Thanks for the help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
