Beginning.PhoneGap, PhoneGap

[ Pobierz całość w formacie PDF ]
For your convenience Apress has placed some of the front
matter material after the index. Please use the Bookmarks
and Contents at a Glance links to access them.
Contents at a Glance
Contents ..............................................................................................................
About the Authors..............................................................................................
About the Technical Reviewers ..........................................................................
Acknowledgments .............................................................................................
Introduction ......................................................................................................
■
Chapter 1: Understanding Cross-Platform Mobile
Application Development...............................................................
■
Chapter 2: Getting Started with PhoneGap ....................................................
■
Chapter 3: Setting the Environment ..............................................................
■
Chapter 4: Using PhoneGap with jQuery Mobile ..........................................
■
Chapter 5: Using PhoneGap with Sencha Touch..........................................
■
Chapter 6: Using PhoneGap with GWT .........................................................
■
Chapter 7: PhoneGap Emulator and Remote Debugging .............................
■
Chapter 8: Using PhoneGap Plug-Ins...........................................................
■
Chapter 9: Extending PhoneGap ..................................................................
Index ...............................................................................................................
iv
  Introduction
Who This Book Is For
This book is meant for anyone wanting to start mobile application development across more
than one mobile platform. The book provides an introduction and detailed tutorial on PhoneGap
and also helps the reader with the following:
1.
Identifying which JavaScript UI Framework is best for them
2.
Introduces the JavaScript UI Framework and its integration with PhoneGap
3.
Explains the concept of a plug-in and how to use it to do OAuth authentication and
Cloud Push
4.
Explains how to write customized plug-ins
How This Book Is Structured
The book begins by explaining about the fragmentation in the mobile OS world and how it affects
us. It goes further to talk about how to bridge the gap due to this fragmentation and how to write
code once and deploy it across mobile platforms.
After the concept behind PhoneGap is made clear, the book goes on to explain PhoneGap
usage on Android and then gives instructions on how to do the same across the other remaining
mobile platforms.
It next introduces how to use a JavaScript UI Framework on top of PhoneGap and also talks
about which JavaScript UI Framework to use in which scenario.
Finally, the book moves its focus to plug-ins. It shows a couple of examples of how to extend
the PhoneGap framework with community plug-ins. Then it explains how to build these plug-ins
across iOS, Android, and BlackBerry.
Downloading the Code
All the source code referred to in this book is available at
apress-phonegap
. The chapters themselves state this. It is also available on the Apress web site at
Apress.com
.
Contacting the Authors
The authors can be contacted at their LinkedIn Profiles:
Rohit Ghatol—
Yogesh Patel—
xii
 1
Chapter
Understanding
Cross-Platform Mobile
Application Development
This book is about mobile application development; more specifically, about easing the
pain of mobile application development. There are many smartphone platforms on the
market: Android, iPhone, BlackBerry, Nokia, the Windows 7 Phone, and WebOS. Newer
platforms are on the rise as well, such as Samsung’s Bada and Meego.
The sheer number of development platforms for mobile applications may seem
overwhelming. This is the first of many points you must keep in mind when dealing with
mobile application development.
In the year 2000, we saw a similar situation in the desktop world. We had Microsoft
Windows, Apple’s Mac, and various versions of Linux and UNIX. At that time, it was
difficult to build products that would run on all these platforms. The resulting
fragmentation was often solved via in-house solutions by building frameworks in C++,
with Operating System (OS)-specific modules abstracted. Fortunately, Sun’s Java came
to the rescue and provided us with a common platform on which to build. With Java’s
build–once–and–run–anywhere strategy, building desktop products had become a
breeze.
Between 2004 and 2008, the developer community saw a different kind of
fragmentation; this time, it took place in the browser world. It was a fragmentation
involving the very popular Internet Explorer 6 vs. Firefox and Safari—then, Chrome and
other browsers came out of the woodwork, causing further fragmentation.
The nature of this fragmentation, however, was different and a little more tame: it was
mainly due to browsers not following the specifications outlined by the World Wide Web
Consortium (W3C). Often, this fragmentation was solved by writing either “If Browser is
IE, then do this else do that” or “If Feature is Present, then do this else do that.”
1
  [ Pobierz całość w formacie PDF ]

  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • braseria.xlx.pl

    •