On Mon, Sep 6, 2010 at 1:59 AM, ytbryan <ytbryan@gmail.com> wrote:
For something this simple, I would go with Frank's suggestion and just use a static function.
However, if you find yourself with a lot of this type of code that is common to all activities, without the ability to subclass Activity since there are other specialized Activities, you can try this "proxy" method I discuss in this thread:
http://groups.google.com/group/android-developers/browse_thread/thread/de784f9cf5f21836/b968818b66dca89c
Is there some structural pattern or design pattern that i am missing out?
Like a Activities Manager that manage all the activities? can someone give me some advice?
For something this simple, I would go with Frank's suggestion and just use a static function.
However, if you find yourself with a lot of this type of code that is common to all activities, without the ability to subclass Activity since there are other specialized Activities, you can try this "proxy" method I discuss in this thread:
http://groups.google.com/group/android-developers/browse_thread/thread/de784f9cf5f21836/b968818b66dca89c
-------------------------------------------------------------------------------------------------
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment