Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
19 Cards in this Set
- Front
- Back
|
An activity |
An instance of Activity, a class in the android SDK. An activity is responsible for managing user interaction with a screen of information. |
|
|
A layout |
Defines a set of user interface objects and their position on the screen. A layout is made out of definitions written in XML. Each definition is used to create an object that appears on screen, like a button or some text. |
|
|
Widgets |
The building blocks you use to compose a user interface. A widget can show text or graphics, interact with the user, or arrange other widgets on the screen. Buttons, text input controls, and check boxes are all types of widgets. |
|
|
What must the root element in an android application specify? |
http://schemas.android.com/all/res/android |
|
|
What is a ViewGroup? |
A widget that contains and arranges other widgets. ViewGroup is a subclass of View. LinearLayout, FrameLayout, TableLayout, and RelativeLayout are all subclasses of ViewGroup. |
|
|
string resource |
A string that lives in a separate XML file called a strings file. |
|
|
What is a resource? |
A piece of your application that is not code- things like image files, audio files, and xml files. A layout is a resource. |
|
|
What does it mean to make a toast? |
A toast is a short message that informs the user of something but it does not require any input or action. To create a toast you call the makeText() method from the Toast class. |
|
|
What architecture are android applications designed around? |
Model-View-Controller (MVC). It states that any object in your application must be a model object, a view object, or a controller object. |
|
|
What is a model object? |
It holds the application's data and "business logic." Model object classes are typically designed to model the things your app is concerned with, such as a user, a product in a store, a photo on a server, etc. Model objects have no knowledge of the user interface; their sole purpose is holding and managing data. Most model object classes are custom made. |
|
|
Model layer |
All of the model objects in an application compose its model layer. |
|
|
What are view objects? |
View objects know how to draw themselves on the screen and how to respond to user input, like touches. A simple rule of thumb is that if you can see it on the screen then it is a View. Android provides a wealth of configurable View classes. You can also custom create view classes. |
|
|
What are controller objects? |
They tie the view and model objects together. They contain "application logic." Controllers are designed to respond to various events triggered by view objects and to manage the flow of data to and from model objects and the view layer. In android, controller is usually a subclass of Activity, Fragment, or Service. |
|
|
What are the four states of the activity lifecylce? |
Resumed, paused, stopped, non-existent |
|
|
What states of the activity lifecylce exist as an instance in memory? |
Stopped, Paused, Resumed exist the entire lifetime of the app as an instance in memory |
|
|
What states of the activity lifecylce are partial or fully visible to the user? |
Paused and resumed are partially and/or fully visible to the user and an instance is stored in memory. |
|
|
What activity state is in the foreground? |
Resumed is the only state in the foreground, that accepts user input. It is fully visible to the user and an instance is stored in memory. |
|
|
How many activities across a device can be in the resume state at one time? |
One |
|
|
What are lifecycle callbacks? |
Subclasses of activity. |
