"object oriented design", "design patterns", et al. (Not to mention
"performance".) Any time someone's throwing around buzzwords like
that I tend to run the other direction.
Ultimately, the only criteria for good code is that it works, it does
the required job in a timely fashion, without excessive use of
resources, it's reliable, it's maintainable, and it was written with a
reasonable amount of effort and expenditure. Any code that
accomplishes those goals is good code. Any that doesn't isn't, no
matter how high-falutin' the technology is.
On Dec 5, 9:49 am, jim <jcant...@gmail.com> wrote:
> In a shared project, we have an Adapter class (extends BaseAdapter,
> implements ListAdapter). In its constructor, this class fetches an
> RSS feed from the internet and parses the returned XML document to
> obtain the data it will 'adapt'; the data is kept in a private class
> variable.
> This is seen as the "Android way" of doing things by the author and is
> supported by the project lead.
> Can this be considered a "Best Practice"?
> Can it be justified on the grounds that it (may?) increase
> performance?
> Doesn't it violate the general Object Oriented Design (OOD) principle
> that a class should have only a "Single Responsiblity"?
> Are best practices for OOD or Java to be set aside in Android
> development?
--
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