[android-developers] Re: Why two fragments instead of one?

> Of course, you could just use a List*View* as well (e.g through an
> <include>, but that is just re-using the view, not any extra code supporting
> it.
I finally got around to testing this using <include>. Works great. The
"extra code supporting it" will end up in ActivityA both for single
and dual layout, so no problem with reusing either.

On 22 Juni, 14:16, Streets Of Boston <flyingdutc...@gmail.com> wrote:
> Yes, the compatibility package is open source. When you get it, you get full
> sources as well:
> <android-sdk-root>\android-compatibility\v4\src
>
> About ListActivity vs ListFragment.
> In my opinion, Fragments are all about re-use. It is fairly easy to dropt a
> Fragment into any activity and it will save you from re-coding it for each
> activity. Dropping in sub-activities (e.g. a ListActivity) into a main
> activity is not impossible, but hard to manage.
>
> Of course, you could just use a List*View* as well (e.g through an
> <include>, but that is just re-using the view, not any extra code supporting
> it.

--
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