Comments on: Happy New Years, Simple pattern for opening an Android Activity http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/ My eclectic journey into the blogosphere Fri, 18 May 2012 19:16:07 +0000 http://wordpress.org/?v=2.3.2 By: Kevin Dahlhausen http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-784 Kevin Dahlhausen Sat, 08 Jan 2011 01:12:06 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-784 Thanks - I like your idea a lot. Will refactor my code to try it out. Thanks - I like your idea a lot. Will refactor my code to try it out.

]]> By: Kontantinos Polychronis - Simple pattern for opening an Android Activity – Κωνσταντίνος Πολυχρόνης http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-783 Kontantinos Polychronis - Simple pattern for opening an Android Activity – Κωνσταντίνος Πολυχρόνης Tue, 04 Jan 2011 09:25:31 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-783 [...] posted a great article titled: Simple pattern for opening an Android [...] […] posted a great article titled: Simple pattern for opening an Android […]

]]> By: Christopher http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-782 Christopher Mon, 03 Jan 2011 23:35:20 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-782 It's not true to say it's only useful for an Activity that's not shared. There's no reason why it this pattern cannot be used anyway. Using this pattern makes no difference to outside users of the app -- they just have to use the normal Intent mechanism rather than this static method. This is just a convenience for when the Activity *is* launched from within the same app. It’s not true to say it’s only useful for an Activity that’s not shared. There’s no reason why it this pattern cannot be used anyway. Using this pattern makes no difference to outside users of the app — they just have to use the normal Intent mechanism rather than this static method.

This is just a convenience for when the Activity *is* launched from within the same app.

]]> By: michael http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-780 michael Sun, 02 Jan 2011 16:47:04 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-780 Good point Davy, the project I've started using this on is with a number of different devs and a large number of screens/activities, so yes it is meant for calls within the same Android App. Good point Davy, the project I’ve started using this on is with a number of different devs and a large number of screens/activities, so yes it is meant for calls within the same Android App.

]]> By: Davy http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-779 Davy Sun, 02 Jan 2011 12:37:07 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-779 Your "simple pattern" is only useful for an Activity that you don't share with other applications. The main goal of the Activity is beeing created by everyone and not only by your application. So, it's important to specify that this pattern is only useful for the developer of THIS app. Your “simple pattern” is only useful for an Activity that you don’t share with other applications.
The main goal of the Activity is beeing created by everyone and not only by your application.

So, it’s important to specify that this pattern is only useful for the developer of THIS app.

]]> By: michael http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-778 michael Sun, 02 Jan 2011 05:23:18 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-778 Actually, I messed up there, in my haste to publish I forgot one of the most important lines (just updated), the line startActivity creates the instance of ActivityOne then onCreate is called. I don't want to the values _value1 and _value2 to be static because I want them to be set for each instance of ActivityOne. Actually, I messed up there, in my haste to publish I forgot one of the most important lines (just updated), the line startActivity creates the instance of ActivityOne then onCreate is called. I don’t want to the values _value1 and _value2 to be static because I want them to be set for each instance of ActivityOne.

]]> By: Erik http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-777 Erik Sun, 02 Jan 2011 03:22:27 +0000 http://mgmblog.com/2011/01/01/happy-new-years-simple-pattern-for-opening-an-android-activity/#comment-777 If you're already accessing the class in a static way, why not just set val1 and val2 at the same time? I think this would increase performance and memory and save yourself a line or two of code. If you’re already accessing the class in a static way, why not just set val1 and val2 at the same time?
I think this would increase performance and memory and save yourself a line or two of code.

]]>