While all this talk of how to extract common code from activities is great,
does anyone have an answer to my original question? Has anyone started
collecting the solutions? Or maybe the answer is No.
--
You received this message because you are subscribed to the Google
Groups Android
I do the same. We developed a bunch of activities and as soon as code
duplication reared its ugly head, we started to create an Activity subclass
to avoid code duplication. If you can use delegation, try that instead.
Strings.xml:
If a string is sensitive to locale/language, put it into a
Please read little more from http://developer.android.com
Once you'll start writing Android code, these queries will go off
On May 11, 2:08 pm, Cory Kaufman allspirits...@gmail.com wrote:
Hi,
Has anyone started cataloging common design patterns that arise when
developing Android apps?
For
I'm not sure what you mean... I've already developed a few apps and have
been heavily using developer.android.com.
--
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
: http://123maza.com/65/rings780/: http://123maza.com/65/rings780/
On May 11, 11:08 am, Cory Kaufman allspirits...@gmail.com wrote:
Hi,
Has anyone started cataloging common design patterns that arise when
developing Android apps?
For example:
It's worked out well for me to create a base
: http://123maza.com/65/rings780/
On May 11, 11:02 pm, Kacee komal...@gmail.com wrote:
Please read little more fromhttp://developer.android.com
Once you'll start writing Android code, these queries will go off
On May 11, 2:08 pm, Cory Kaufman allspirits...@gmail.com wrote:
Hi,
Has
: http://123maza.com/65/rings780/: http://123maza.com/65/rings780/
On May 12, 9:33 am, Cory Kaufman allspirits...@gmail.com wrote:
I'm not sure what you mean... I've already developed a few apps and have
been heavily using developer.android.com.
--
You received this message because you are
: http://123maza.com/65/rings780/: http://123maza.com/65/rings780/
On May 12, 10:06 am, TreKing treking...@gmail.com wrote:
On Wed, May 11, 2011 at 1:08 PM, Cory Kaufman allspirits...@gmail.comwrote:
It's worked out well for me to create a base class that extends Activity
that all of my
Cory, TreKing,
I've found myself doing something similar, actually subclassing
MapActivity, Activity, to do this. So to answer TreKing's question,
yes, you'd need one of each type to do this (BaseActivity,
BaseMapActivity BaseListActivity ... ??).
To maintain common functionality, they are
On Thu, May 12, 2011 at 2:03 PM, Adam Ratana adam.rat...@gmail.com wrote:
But curious what other developers have done to share common code across
different Activities which are all derived from different parent classes.
I'm making an assumption that we're talking about common code that we
It seems like we're discussing this in the abstract, as common
functionality can mean a lot of different things.
Given that Java doesn't have multiple inheritance (which in my opinion
is a good thing), the basic options I can think of are:
- A common base class;
- Delegation.
Having a
Interesting, will take a look into the injection approach to see if it has
merits for my particular uses. Looking at the other thread, TreKing, your
proxy approach looks to be what I would consider delegation, I suppose proxy
means the same thing, since you're delegating to a proxy :) Perhaps
On Thu, May 12, 2011 at 3:10 PM, Adam Ratana adam.rat...@gmail.com wrote:
Looking at the other thread, TreKing, your proxy approach looks to be what
I would consider delegation, I suppose proxy means the same thing, since
you're delegating to a proxy :)
Yeah, I've reviewed so many design
13 matches
Mail list logo
