Difference between revisions of "MAP524/DPS924 Lecture 3"
(Created page with '= Android Development Building Blocks (Components) = This week we're looking at the primary components used for building an Android app. We're finally starting to write code. Bu…') |
|||
| Line 3: | Line 3: | ||
This week we're looking at the primary components used for building an Android app. We're finally starting to write code. But first we'll need an overview of: | This week we're looking at the primary components used for building an Android app. We're finally starting to write code. But first we'll need an overview of: | ||
| + | * '''Application Manifest''': XML based file that the application outlines the activities, services, broadcast receivers, data providers and permissions that make up the complete application. Used to also hold some information that's now in build.gradle. | ||
* '''Activity''': [[#Activity|see below]]. | * '''Activity''': [[#Activity|see below]]. | ||
* '''Intent''': a messaging object you can use to request an action from another app component. One of the primary ways to do IPC on Android. See overview on [http://developer.android.com/guide/components/intents-filters.html Android developers]. | * '''Intent''': a messaging object you can use to request an action from another app component. One of the primary ways to do IPC on Android. See overview on [http://developer.android.com/guide/components/intents-filters.html Android developers]. | ||
* '''Broadcast Receiver''': Enable applications to receive intents that are broadcast by the system or by other applications. See ths [http://www.vogella.com/tutorials/AndroidBroadcastReceiver/article.html BroadcastReceiver tutorial]. | * '''Broadcast Receiver''': Enable applications to receive intents that are broadcast by the system or by other applications. See ths [http://www.vogella.com/tutorials/AndroidBroadcastReceiver/article.html BroadcastReceiver tutorial]. | ||
| − | * '''Service''': an application component representing either an application's desire to perform a longer-running operation while not interacting with the user or to supply functionality for other applications to use. | + | * '''Service''': an application component representing either an application's desire to perform a longer-running operation while not interacting with the user or to supply functionality for other applications to use. We'll also look at them more closely after the break. |
* '''Event handling''': See this nice [http://www.tutorialspoint.com/android/android_event_handling.htm Android Event Handling tutorial] | * '''Event handling''': See this nice [http://www.tutorialspoint.com/android/android_event_handling.htm Android Event Handling tutorial] | ||
** Event Listener: a class specialized that contains a single callback method. | ** Event Listener: a class specialized that contains a single callback method. | ||
** Event Handler: the actual method that handles the event. | ** Event Handler: the actual method that handles the event. | ||
** Easiest way (if available) is to register the event handler via the layout xml file. | ** Easiest way (if available) is to register the event handler via the layout xml file. | ||
| − | + | * '''Layout''': [[#Layout|see below]]. | |
| − | + | * Fragment: created using an XML layout file that looks like a sub-layout and behaves like a sub-activity. We'll look at fragments next week. | |
| − | + | * '''Content Provider''': One way for an application to provide access to data it holds. It's one form of IPC usually used for more standard types of data. See a list of tutorials at the [http://developer.android.com/guide/topics/providers/content-providers.html bottom of this page]. We'll also look at them more closely after the break. | |
| − | + | * '''Menu''': Used to be a critical part of any android application until the menu button's been removed from Android tablets and later phones. Now is still used but isn't as prevalent. | |
| − | Layout | + | * '''Resource''': an additional file and static content that your code uses, such as bitmaps, layout definitions, user interface strings, animation instructions, and more. |
| − | + | * '''Notification''': a news channel that alerts the user to important events as they happen or a log that chronicles events while the user is not paying attention. See the [http://developer.android.com/guide/topics/ui/notifiers/notifications.html developer guide]. | |
| − | + | * '''Settings and Shared Preferences''': display ([http://developer.android.com/guide/topics/ui/settings.html Settings]) and store ([http://developer.android.com/guide/topics/ui/settings.html Shared Preferences]) simple configuration data (strings, numbers) for your application. | |
| − | + | * '''R.java''': A dynamically-generated class named R containing references to resources. | |
| − | Fragment | ||
| − | |||
| − | created using an XML layout file that looks like a sub-layout and behaves like a sub-activity. | ||
| − | Content Provider | ||
| − | |||
| − | |||
| − | Menu | ||
| − | |||
| − | a | ||
| − | Resource | ||
| − | |||
| − | an additional file and static content that your code uses, such as bitmaps, layout definitions, user interface strings, animation instructions, and more. | ||
| − | Notification | ||
| − | |||
| − | a news channel that alerts the user to important events as they happen or a log that chronicles events while the user is not paying attention. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Activity == | == Activity == | ||
Revision as of 12:53, 12 July 2015
Android Development Building Blocks (Components)
This week we're looking at the primary components used for building an Android app. We're finally starting to write code. But first we'll need an overview of:
- Application Manifest: XML based file that the application outlines the activities, services, broadcast receivers, data providers and permissions that make up the complete application. Used to also hold some information that's now in build.gradle.
- Activity: see below.
- Intent: a messaging object you can use to request an action from another app component. One of the primary ways to do IPC on Android. See overview on Android developers.
- Broadcast Receiver: Enable applications to receive intents that are broadcast by the system or by other applications. See ths BroadcastReceiver tutorial.
- Service: an application component representing either an application's desire to perform a longer-running operation while not interacting with the user or to supply functionality for other applications to use. We'll also look at them more closely after the break.
- Event handling: See this nice Android Event Handling tutorial
- Event Listener: a class specialized that contains a single callback method.
- Event Handler: the actual method that handles the event.
- Easiest way (if available) is to register the event handler via the layout xml file.
- Layout: see below.
- Fragment: created using an XML layout file that looks like a sub-layout and behaves like a sub-activity. We'll look at fragments next week.
- Content Provider: One way for an application to provide access to data it holds. It's one form of IPC usually used for more standard types of data. See a list of tutorials at the bottom of this page. We'll also look at them more closely after the break.
- Menu: Used to be a critical part of any android application until the menu button's been removed from Android tablets and later phones. Now is still used but isn't as prevalent.
- Resource: an additional file and static content that your code uses, such as bitmaps, layout definitions, user interface strings, animation instructions, and more.
- Notification: a news channel that alerts the user to important events as they happen or a log that chronicles events while the user is not paying attention. See the developer guide.
- Settings and Shared Preferences: display (Settings) and store (Shared Preferences) simple configuration data (strings, numbers) for your application.
- R.java: A dynamically-generated class named R containing references to resources.
