206d4e842d
Break MessageViewFragment up into two fragments, MessageViewFragment, which is used to show regular messages, and MessageFileViewFragment, which shows EML messages. (And their base class, MessageViewFragmentBase.) MessageViewFragmentBase's javadoc has a class diagram. MessageViewFragment is actually named MessageViewFragment2 at this point so that GIT correctly finds out the rename from MessageViewFragment to MessageViewFragmentBase. I'll rename it back in a following CL. Also added very basic unit tests for MessageView and MessageFileView. At this point, they just make sure the activities really open and show messages without exceptions. I feel like the current naming schema for the activities/fragments is kinda confusing. Let me know if you come up with better names. Change-Id: Iff948f4b68cfdb7c1e68f225927b0ce58d34766b |
||
---|---|---|
.. | ||
account_folder_list_item.xml | ||
account_folder_list.xml | ||
account_setup_account_type.xml | ||
account_setup_basics.xml | ||
account_setup_check_settings.xml | ||
account_setup_exchange.xml | ||
account_setup_incoming.xml | ||
account_setup_names.xml | ||
account_setup_options.xml | ||
account_setup_outgoing.xml | ||
accounts_item.xml | ||
accounts.xml | ||
connection_error_banner.xml | ||
debug.xml | ||
list_separator.xml | ||
list_title.xml | ||
mailbox_list_item.xml | ||
mailbox_list.xml | ||
message_compose_attachment.xml | ||
message_compose.xml | ||
message_file_view.xml | ||
message_list_item_footer.xml | ||
message_list_item.xml | ||
message_list_xl.xml | ||
message_list.xml | ||
message_view_attachment.xml | ||
message_view_fragment.xml | ||
message_view_invitation.xml | ||
message_view.xml | ||
recipient_dropdown_item.xml | ||
recipient_dropdown_separator.xml | ||
upgrade_accounts_item.xml | ||
upgrade_accounts.xml |