Design pattern for extending Android's activities?

Posted by Carl on Stack Overflow See other posts from Stack Overflow or by Carl
Published on 2010-04-28T21:34:06Z Indexed on 2010/04/28 22:07 UTC
Read the original article Hit count: 251

Filed under:
|
|

While programming on Android, I end up writing a parent activity which is extended by several others. A bit like ListActivity. My parent activity extends Activity. if I intend to use a Map or a List, I can't use my parent activity as superclass - the child activity can only extend one activity obviously. As such I end up writing my parent activities with the same logic for Activity, ListActivity, MapActivity and so forth.

What am I looking for is some sort of trait functionality/design pattern which would help in this case. Any suggestions?

© Stack Overflow or respective owner

Related posts about android

Related posts about design