Android UI knowledge share

Description

A brief Slide Set for the second Android knowledge share with new starts.
dfsdgas dfgdfgsgdfsgsd
Slide Set by dfsdgas dfgdfgsgdfsgsd, updated more than 1 year ago
dfsdgas dfgdfgsgdfsgsd
Created by dfsdgas dfgdfgsgdfsgsd about 8 years ago
10
0

Resource summary

Slide 1

    Key Components of Android UI
    Activities Fragments Views XML resource files Activity - A single, focused thing that the user can do. Almost all activities interact with the user, so the Activity class takes care of creating a window for you in which you can place your UI.Fragment - A piece of an application's user interface or behaviour that can be placed in an Activity. View - Basic building block for all UI components e.g. XML resource files - xml files that can define the UI for layouts, shapes, animations, dimensions, colours etc.

Slide 2

    Activity
    Activities are the heart of the Android app.  They can loosely be viewed as the "controller" in the Android framework.In the diagram on the left we see the 'activity lifecycle' from creation to being destroyed. Typically the only methods we need to worry about are onCreate(), onResume() and onPause() / onStop().Example of a simple onCreate() method that defines what layout the activity should display on screen.@Overrideprotected void onCreate(Bundle savedInstanceState) {    super.onCreate(savedInstanceState);    setContentView(R.layout.activity_home);}
    Caption: : Activity Lifecycle

Slide 3

    Fragment
    A Fragment represents a behavior or a portion of user interface in an Activity. You can combine multiple fragments in a single activity to build a multi-pane UI and reuse a fragment in multiple activities. You can think of a fragment as a modular section of an activity, which has its own lifecycle, receives its own input events, and which you can add or remove while the activity is running (sort of like a "sub activity" that you can  reuse indifferent activities).

Slide 4

    View
    A view is the basic building block of any UI element. Anything that you can see on the screen inherits from view. A view will typically have it's style defined in xml, and it's behaviour defined in Java. It's worth noting that it is possible to style views programmatically, but generally it's cleaner to keep this stuff separate. We can define our own custom views if the behaviour we require is not included in the standard framework. For example our Mind Maps uses a custom zoomable view to draw the nodes on to a canvas.

Slide 5

    XML resources
    XML files are used to define the appearence of many UI elements in Android including: Layouts Animations Styles Colors Shapes Views Drawables

Slide 6

    Thank you.Any questions please feel free to ask or email peter.smith@examtime.com For a comprehensive API reference and really good training material checkout http://developer.android.com/
Show full summary Hide full summary

Similar

KEE2
harrym
A-Level Physics: Course Overview
cian.buckley+1
Symbols in Lord of the Flies
lowri_luxton
B5 - Growth and Deveolopment
blairzy123
USA and Vietnam (1964-1975) - Part 1
Lewis Appleton-Jones
OCR AS CHEMISTRY A DEFINITIONS
awesome.lois
Matters of Life and Death - Edexcel GCSE Religious Studies Unit 3
nicolalennon12
AQA Business Unit 1
lauren_binney
Teaching Methods Every Educator Should Know
Micheal Heffernan
Bowlby's Theory of Attachment
Jessica Phillips
Salesforce Admin 201 Exam Chunk 6 (156-179)
Brianne Wright