Loading ...
Sorry, an error occurred while loading the content.

910REVIEW: "Learning Android", Marko Gargenta

Expand Messages
  • Rob, grandpa of Ryan, Trevor, Devon & Han
    Jan 8, 2014
    • 0 Attachment
      BKLRNAND.RVW 20130123

      "Learning Android", Marko Gargenta, 2011, 978-1-449-39050-1
      %A Marko Gargenta https://github.com/marakana http://marakana.com
      %C 103 Morris Street, Suite A, Sebastopol, CA 95472
      %D 2011
      %G 1-449-39050-1 978-1-449-39050-1
      %I O'Reilly & Associates, Inc.
      %O http://examples.oreilly.com/0636920010883/ nuts@...
      %O http://www.amazon.com/exec/obidos/ASIN/1449390501/robsladesinterne
      %O http://www.amazon.ca/exec/obidos/ASIN/1449390501/robsladesin03-20
      %O Audience a+ Tech 2 Writing 2 (see revfaq.htm for explanation)
      %P 270 p.
      %T "Learning Android"

      The preface states that the book is for developers. (In other words,
      it's not going to teach you how to use Android.)

      Chapter one is a overview, a terse history of Android and the business
      model for it. The Stack, in chapter two, outlines the structure of
      the operating system, and lists some utilities and development
      environments. Chapter three describes installation of the Android SDK
      (Software Development Kit). Because I reviewed this title as an
      ebook, while the text is generally clear and detailed, some references
      are confusing as to whether a link or reference goes to another part
      of the book or some Website. Explanation of the sample code is not
      always complete, but is available, via the associated Website for
      exploration. Java or C++ programming experience is advantageous in
      understanding the material, but is not required. The material on the
      main building blocks, in chapter four, is the terminology of the
      Android system and development. Chapter five reviews the example
      Yamba project and requirements (providing a good exegesis of sample
      project choice factors and a solid design philosophy), and is an
      overview of chapters six to thirteen.

      Chapter six addresses the Android user interface, using both XML
      (eXtensible Markup Language) and Java code. The Eclipse development
      environment is used for much of the work, so some basics are not
      covered, and the options for the APIs are not clear. The filesystem
      is explained in chapter seven, although the security of the data
      partition is simply asserted, even though all the data is readable.
      Servers, background operations without a display, are discussed in
      chapter eight. Chapter nine explains the database, concentrating on
      the DbHelper API. Again, security is asserted to be automatic even
      though SQL (Structured Query Language) statements are allowed. (Yes,
      for the examples given user input is not required, but the whole
      premise of an SQL-injection attack is the assumption that all code is
      going to be valid, and the ability to append malicious commands.)
      Lists and adapters, in chapter ten, deal with display and
      presentation. "Broadcast Receivers," in chapter eleven, would
      otherwise be known as triggers and events. Chapter twelve's review of
      content providers extends chapter nine's material on databases, and
      has additional ideas on extra display functions. System services
      (like chapter eight's servers, only part of the base operating system)
      are discussed in chapter thirteen. The Android Interface Definition
      Language (AIDL), for inter-process communications, is described in
      chapter fourteen. Chapter fifteen describes the Native Development
      Kit, although it is not clear about specific uses.

      This is a well-designed introduction (though not reference) to
      programming for Android.

      copyright, Robert M. Slade 2013 BKLRNAND.RVW 20130123

      ====================== (quote inserted randomly by Pegasus Mailer)
      rslade@... slade@... rslade@...
      Post hoc, ergo propter hoc
      After it, therefore because of it
      victoria.tc.ca/techrev/rms.htm http://www.infosecbc.org/links