As I'm learning about Activities and the components they contain I am wanting to break things up into components. Is there any list of guidelines / commonly used organization of Activity classes?
As I add functionality to my apps, things like context menus, options menus, and references to view objects in from resources, my class starts to look really ugly. I have done a lot of .net programming, so at first I wanted to start making partial class declarations in different files but found out java doesn't support this. Are activity classes generally ugly or is there a common way that pro developers compartmentalize things in their activity classes? Thanks for any helpful info, Greg Hedin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
