16a60dca84
This version is hybrid of the old design and what Andy's suggested. - MessageViewFragment is responsible to show a single message at a time. - Call MVF.openMessage() to tell it to open another message. No need to re-create a new MVF to do this. - MessageView manages the message list, and handles "move-to-newer/older" buttons. Reason for not re-creating a fragment when opening another message is: - Re-using the same fragment doesn't make it as complecated/ugly as I was initially afraid. It's basically cancelling all running tasks, re-initializee some views, and load a message. - We don't have to run MVF.onCreate() over and over again when moving through messages. We may change the strategy later, but I think it's suffice for now. (Changing this might affect how the back key works, so let's revisit it when the fragment manager supports back.) Basically this CL is all about internal changes. No UI should have changed except for: - Moved "Move to newer/older" buttons to the bottom. Also fixes: Bug: 2849129 Change-Id: I00c05069231afded9d98d3d52dd9a7925ebdee9d |
||
|---|---|---|
| .. | ||
| arrays.xml | ||
| build_number.xml | ||
| colors.xml | ||
| dimensions.xml | ||
| strings.xml | ||
| styles.xml | ||