9/21/10

9/21/10

9/21/10

Example taken from Dan Borensteins 2008 GoogleIO presentation: http://sites.google.com/site/io/dalvik-vm-internals

9/21/10

9/21/10

9/21/10

The invoking app is put on the stack and when the user hits the back button, it is restored.

User presses button in one app, and it causes an activity dened by another app to run!

Activity X Activity #1 Activity Y Activity Z

Step 1: An activity signals an intent.

Step 2: Android determines which available activity is most appropriate for handling that intent.

9/21/10

Eclipse 3.5 JDK v6 Android SDK

ADT Plugin

Required Optional Components Components

9/21/10

See http://developer.android.com/sdk/index.html for details.

a) Download the appropriate package for your computer.

b) Unpack archive contents on your hard disk. c) Adjust your systems PATH variable (details on next slide)

See http://developer.android.com/sdk/index.html for details.

Details vary by platform:

See http://developer.android.com/sdk/index.html for details.

9/21/10

See http://developer.android.com/sdk/index.html for details.

See http://developer.android.com/sdk/index.html for details.

See http://developer.android.com/sdk/index.html for details.

9/21/10

DEMO

10

9/21/10

ViewGroup uses the Composite design pattern to enable grouping of multiple View objects into non-trivial user interfaces.

In order to render a view tree on the devices screen an Activity must call the setContentView() method.

11

9/21/10

The normal way to create user interfaces in Android apps is to declaratively describe the UI in an XML layout file, though UIs can also be created programmatically in code.

12

9/21/10

13

9/21/10

DEMO

14

9/21/10

15

9/21/10

DEMO

16

9/21/10

17

9/21/10

18

9/21/10

19

9/21/10

DEMO

20

9/21/10

IntroActivity.java 117-135 (commit c27e6)

21

9/21/10

[commit fa7e] [commit c27e]

22

9/21/10

DEMO

23

9/21/10

24