ANDROID JAVA RESUME
This application is, or was, my resume. It was developed for an older tablet, and therefore does not run on some of the newer ones. It still demonstrates how Android Java applications are separated into activities.
The user interface displays views, or fragments that contain views. Sections of the original document correspond to fragments, and are listed when the application starts. A tablet displays the menu next to the fragment, but smaller devices switch between the menu and the detail, independent of portrait/ landscape rotation.
Two types of files that contain information are a part of the application itself, and CSV files can be loaded into the SD card. CSV column names are in the first record of the file; names like "URL" allow the application to use live links, and start email or browser applications.
The user interface displays views, or fragments that contain views. Sections of the original document correspond to fragments, and are listed when the application starts. A tablet displays the menu next to the fragment, but smaller devices switch between the menu and the detail, independent of portrait/ landscape rotation.
Two types of files that contain information are a part of the application itself, and CSV files can be loaded into the SD card. CSV column names are in the first record of the file; names like "URL" allow the application to use live links, and start email or browser applications.
The Model-View-Controller program architecture manages application data, program logic and business rules. Phone/ tablet development replaces the Model-View-Controller model with a Model-View / View-Model architecture; the device operating system functions as the controller.
Inputs
|
Outputs
|
Usually, there are specific design reasons for locating input files in certain areas. However, I explored all the options and provided model methods for later applications. Consequently, input files for this application are located in four different places.
![]()
File Storage
|
Application outputs are displayed in XML fragments. Some are created programmatically, and others are generated from IDE sample apps when the type of application is selected. The fragments that are files separate from Java code are included here.
![]()
Resources
Android development relies heavily on string resources. Items that might have been declared as constants in other languages are instead stored as XML literals.
This file also includes non-animated graphics. ![]()
|
Manifest and Source Code
The manifest describes the contents of the application, and how the components will attach to the Android operating system. It also includes permissions to use elements like instrumentation or mapping services; in this instance, the app only needs to access the email application and the Web browser.
The most interesting portion of the source code is the topic detail class, which actually builds and displays views based on the user selection from the first page. The private classes are documented to expose the workings of the application as a teaching example; in some applications, the code is not exposed, although that philosophy is changing with the advent of GitHub and open source.
The rest of the source is generated by the IDE when development begins, and did not require much customization during development.
The most interesting portion of the source code is the topic detail class, which actually builds and displays views based on the user selection from the first page. The private classes are documented to expose the workings of the application as a teaching example; in some applications, the code is not exposed, although that philosophy is changing with the advent of GitHub and open source.
The rest of the source is generated by the IDE when development begins, and did not require much customization during development.
![]()
|
![]()
|
Resume Namespace Documentation
![]()
The TopicListActivity class is the primary namespace within the application. It starts
the application on the Android device and displays the list of items from which
the user can select.
![]()
The TopicDetailActivity class displays detailed information about a specific item that was displayed using the TopicListFragment class.
|
![]()
The TopicListFragment Class displays the list of topics. Most of this class is generated by the IDE when it creates a
new Master/Detail Flow Android Application Project.
![]()
The TopicDetailFragment class does all the formatting and display work for each section of the resume. However, most of its classes are private, and this document only describes entry points to the namespace.
|
Research Sources
Tutorial One: Learn Android SDK Development from Scratch
http://code.tutsplus.com/articles/learn-android-sdk-development-from-scratch--mobile-12153
Tutorial Two: Getting Started
http://developer.android.com/training/index.html
http://code.tutsplus.com/articles/learn-android-sdk-development-from-scratch--mobile-12153
Tutorial Two: Getting Started
http://developer.android.com/training/index.html