If the Android platform you are developing for does not support fragments, how would you go about providing fragment-like processing in you Android Application ?
Hints: Would you have multiply activities? Which UI elements (controls/widgets) would you use?
Solution
A Fragment represents a behavior or a portion of user interface in an Activity.. One big reason to stick with the SupportFragment for a while is that you do not have access to the ChildFragmentManager until API17.
Instead of creating fragments we can use by custom views for mutliple display. Let’s implementation of fragments in views. First, we’ll have the notion of a Container, which can show an item and also handle back presses.
The activity assumes there’s always a container and merely delegates the work to it.
The list is also quite trivial.
Now, the meat of the work: loading different XML layouts based on resource qualifiers.
Using custom views works great, but we would like to isolate business logic into dedicated controllers. we call those parameters. This makes the code much more readable and facilitates testing. MyDetailView could look something like this
Make your fragments shells of themselves. Pull view code up into custom view classes, and push business logic down into a presenter that knows how to interact with the custom views. Then, your fragment is nearly empty, just inflating custom views that connect themselves with presenters:
At that point you can eliminate the fragment
.
If the Android platform you are developing for does not support fragme.docx
1. If the Android platform you are developing for does not support fragments, how would you
go about providing fragment-like processing in you Android Application ?
Hints: Would you have multiply activities? Which UI elements (controls/widgets) would
you use?
Solution
A Fragment represents a behavior or a portion of user interface in an Activity.. One big reason to
stick with the SupportFragment for a while is that you do not have access to the
ChildFragmentManager until API17.
Instead of creating fragments we can use by custom views for mutliple display. Let’s
implementation of fragments in views. First, we’ll have the notion of a Container, which can
show an item and also handle back presses.
The activity assumes there’s always a container and merely delegates the work to it.
The list is also quite trivial.
Now, the meat of the work: loading different XML layouts based on resource qualifiers.
Using custom views works great, but we would like to isolate business logic into dedicated
controllers. we call those parameters. This makes the code much more readable and facilitates
testing. MyDetailView could look something like this
Make your fragments shells of themselves. Pull view code up into custom view classes, and push
business logic down into a presenter that knows how to interact with the custom views. Then,
your fragment is nearly empty, just inflating custom views that connect themselves with
presenters:
At that point you can eliminate the fragment
