On Wed, Feb 24, 2010 at 10:28 PM, Conny <[email protected]> wrote: > In a generalist sense adapter pattern is a bridge between 2 classes > that have some common functionality, but the interfaces are not > reusable between them. Ideally the need for adapter arises when we > have two classes that are not developed keeping in mind interaction > between them. >
Right, and in this case, Android provides ArrayAdapter (and it's related classes) that allow you to convert a generic list of user-defined objects into a list of View objects, so the name seems appropriate. Strategy pattern, is more of a future reuse pattern, and that is the > intent its in android framework, reuse and extensibility. > Well, all patterns are designed for "future reuse". Strategy, specifically, defines a way to abstract out functionality or algorithms into components that can be added, removed, or swapped in and out at runtime. ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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
