Android™ Application Development - Bahar Ali Khan

More documents

Recommendations

Info

Chapter 11: Advanced Android Development Creating and Using Frame-by-Frame Animations 372 Frame-by-frame animations are akin to traditional cell-based cartoons where an image is chosen for each frame. Where tweened animations use the target View to supply the content of the animation, frame-byframe animations let you specify a series of Drawable objects that are used as the background to a View. The AnimationDrawable class is used to create a new frame-by-frame animation presented as a Drawable resource. You can defi ne your Animation Drawable resource as an external resource in your project’s drawable folder using XML. Use the animation-list tag to group a collection of item tags, each of which uses a drawable attribute to defi ne an image to display, and a duration attribute to specify the time (in milliseconds) to display it. The following XML snippet shows how to create a simple animation that displays a rocket taking off (rocket images not included). The fi le is stored as res/drawable/animated_rocket.xml: To display your animation, set it as the background to a View using the setBackgroundResource method, as shown in the following code snippet: ImageView image = (ImageView)findViewById(R.id.my_animation_frame); image.setBackgroundResource(R.drawable.animated_rocket); Alternatively, use the setBackgroundDrawable to use a Drawable instance instead of a resource reference. Run the animation calling its start method, as shown in the code snippet below: AnimationDrawable animation = (AnimationDrawable)image.getBackground(); animation.start(); Using Themes to Skin Your Applications The multifunction nature of a mobile device means users will be running and switching between many applications created by a range of different developers. Themes are a way of ensuring that your applications present a consistent look and feel. To apply a theme, set the android:theme attribute on either the application or an individual activity tag in the manifest, as shown in the code snippet below:
Chapter 11: Advanced Android Development Android includes several predefi ned themes as part of the base package, including: ❑ Theme.Black Features a black background with white foreground controls and text. ❑ Theme.Light Features a white background with dark borders and text. ❑ Theme.Translucent Features a partially transparent Form. You can set the theme of an Activity at run time, but it’s generally not recommended, as Android uses your Activity’s theme for intra-Activity animations, which happens before your application is loaded. If you do apply a theme programmatically, be sure to do so before you lay out the Activity as shown in the code snippet below: protected void onCreate(Bundle icicle) { super.onCreate(icicle); setTheme(android.R.style.Theme_Translucent); setContentView(R.layout.main); } If you don’t apply a theme to your application or any of its Activities, it will use the default theme android.R.style.Theme. Advanced Canvas Drawing You were introduced to the Canvas class in Chapter 4, where you learned how to create your own Views. The Canvas was also used in Chapter 7 to annotate Overlays for MapViews. The concept of the Canvas is a common metaphor used in graphics programming and generally consists of three basic drawing components: ❑ Canvas Supplies the draw methods that paint drawing primitives onto the underlying bitmap. ❑ Paint Also referred to as a “brush,” Paint lets you specify how a primitive is drawn on the bitmap. ❑ Bitmap Is the surface being drawn on. Most of the advanced techniques described in this chapter involve variations and modifi cations to the Paint object that let you add depth and texture to otherwise fl at raster drawings. The Android drawing API supports translucency, gradient fi lls, rounded rectangles, and anti-aliasing. Unfortunately, owing to resource limitations, it does not yet support vector graphics; instead, it uses traditional raster-style repaints. The result of this raster approach is improved effi ciency, but changing a Paint object will not affect primitives that have already been drawn; it will only affect new elements. If you’ve got a Windows development background, the two-dimensional (2D) drawing capabilities of Android are roughly equivalent to those available in GDI+. 373
Page 1 and 2:
Professional Android Application su
Page 3:
Professional Android Application D
Page 6 and 7:
Professional Android Application D
Page 8 and 9:
About the Author Originally from Pe
Page 10 and 11:
Acknowledgments A big thank you goe
Page 12 and 13:
Contents Chapter 2: Getting Started
Page 14 and 15:
Contents xii Saving and Loading Fil
Page 16 and 17:
Contents Chapter 10: Accessing Andr
Page 19 and 20:
Introduction Now is an exciting tim
Page 21 and 22:
Introduction covered, you can move
Page 23:
Introduction At http://p2p.wrox.com
Page 26 and 27:
Chapter 1: Hello, Android 2 Using t
Page 28 and 29:
Chapter 1: Hello, Android An Open P
Page 30 and 31:
Chapter 1: Hello, Android 6 ❑ ❑
Page 32 and 33:
Chapter 1: Hello, Android 8 When ma
Page 34 and 35:
Chapter 1: Hello, Android 10 In mar
Page 36 and 37:
Chapter 1: Hello, Android 12 Each A
Page 38 and 39:
Chapter 1: Hello, Android 14 ❑ Da
Page 40 and 41:
Chapter 1: Hello, Android 16 ❑ an
Page 43 and 44:
Getting Started All you need to sta
Page 45 and 46:
Chapter 2: Getting Started Unless o
Page 47 and 48:
Installing the ADT Plug-in Install
Page 49 and 50:
Chapter 2: Getting Started 3. In th
Page 51 and 52:
Chapter 2: Getting Started If every
Page 53 and 54:
} lp = new LinearLayout.LayoutParam
Page 55 and 56:
❑ ❑ ❑ ❑ ❑ Small screens w
Page 57 and 58:
Chapter 2: Getting Started on how t
Page 59 and 60:
Chapter 2: Getting Started To start
Page 61 and 62:
Ensuring a Seamless User Experience
Page 63 and 64:
Figure 2-11 Chapter 2: Getting Star
Page 65 and 66:
} myListView.setAdapter(aa); Chapte
Page 67 and 68:
Chapter 2: Getting Started A number
Page 69 and 70:
Creating Applications and Activitie
Page 71 and 72:
Chapter 3: Creating Applications an
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Creating Resources Chapter 3: Creat
Page 79 and 80:
❑ ❑ #ARGB #ARRGGBB Chapter 3: C
Page 81 and 82:
Page 83 and 84:
android:startOffset=”500” andro
Page 85 and 86:
Referencing Resources in Resources
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
} } Chapter 3: Creating Application
Page 97:
Page 100 and 101:
Chapter 4: Creating User Interfaces
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Chapter 5: Intents, Broadcast Recei
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 183 and 184:
Data Storage, Retrieval, and Sharin
Page 185 and 186:
Chapter 6: Data Storage, Retrieval,
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
} Chapter 6: Data Storage, Retrieva
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
} } } Chapter 6: Data Storage, Retr
Page 205 and 206:
Querying Your Database Chapter 6: D
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
} // Open or create the database to
Page 213 and 214:
Page 215 and 216:
Adding, Updating, and Deleting Cont
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
} } Chapter 6: Data Storage, Retrie
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
} } break; Chapter 6: Data Storage,
Page 229 and 230:
Page 231 and 232:
Maps, Geocoding, and Location-Based
Page 233 and 234:
Chapter 7: Maps, Geocoding, and Loc
Page 235 and 236:
} Chapter 7: Maps, Geocoding, and L
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271:
Summary Chapter 7: Maps, Geocoding,
Page 274 and 275:
Chapter 8: Working in the Backgroun
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 303 and 304:
Peer-to-Peer Communication In this
Page 305 and 306:
Chapter 9: Peer-to-Peer Communicati
Page 307 and 308:
} Chapter 9: Peer-to-Peer Communica
Page 309 and 310:
Handling Subscription Requests Chap
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Figure 9-4 Chapter 9: Peer-to-Peer
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Accessing Android Hardware Android
Page 341 and 342:
Chapter 10: Accessing Android Hardw
Page 343 and 344:
content.put(Audio.AudioColumns.DATE
Page 345 and 346: public void onShutter() { // TODO D
Page 347 and 348: Chapter 10: Accessing Android Hardw
Page 355 and 356: public void setPitch(float pitch) {
Page 357 and 358: } setContentView(R.layout.main); Ch
Page 375: Chapter 10: Accessing Android Hardw
Page 378 and 379: Chapter 11: Advanced Android Develo
Page 424 and 425: 400 Android, getting started Androi
Page 426 and 427: 402 databases databases creating ea
Page 428 and 429: 404 interapplication communication
Page 430 and 431: 406 passing custom class objects pa
Page 432 and 433: 408 synchronizing threads synchroni
Page 435 and 436: Programmer to Programmer Get more
show all

Android™ Application Development - Bahar Ali Khan

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?