Yea, I'll create a service to essentially do the route tracking when I am doing a route.
I am wondering if it makes sense to contain all that state/logic in the service, or if I should put as much of the common state into an Application class, and let the activities/services access it through the application class. On Monday, March 19, 2012 12:18:57 PM UTC-4, TreKing wrote: > > On Mon, Mar 19, 2012 at 10:01 AM, RedBullet <> wrote: > >> So, is there an example that shows how an Application class interacts >> with activities? >> > > Application doesn't really "interact" with Activities. You can of course > add your own logic that does, but it's not necessary, particularly for what > you've described as your use case. > > >> My app to date is just activity based. Do I need to do anything aside >> from create a class derived from Application, store my own application >> state info in it, an update my manifest? >> >> Or do I need to more than that? >> > > Yes. I really sounds like you need a Service, not an Application. See the > Google Navigation app for a prime example. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > -- 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] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
