Welcome to the source code for The Busy Coder's Guide to Android Development!
All of the source code in this archive is licensed under the Apache 2.0 license except as noted.
The names of the top-level directories roughly correspond to a shortened form of the chapter titles. Since chapter numbers change with every release, and since some samples are used by multiple chapters, I am loathe to put chapter numbers in the actual directory names.
Most of the projects should have a build.gradle file suitable for
importing the project into Android Studio. Note, though, that you
may need to adjust the compileSdkVersion in build.gradle if it
requests an SDK that you have not downloaded and do not wish to
download. Similarly, you may need to adjust the buildToolsVersion
value to refer to a version of the "Build-tools" that you have downloaded
from the SDK Manager.
The samples also have stub Gradle wrapper files, enough to allow for
easy import into Android Studio. However,
always check the gradle-wrapper.properties file before importing anything into Android Studio,
as there is always the chance that somebody has published material linking you to a hacked Gradle installation.
Right now, you will need your own local installation of Gradle 2.1
in order to build the projects from the command line, as the repository
does not contain gradlew or its corresponding JAR for security reasons.
These projects can be imported using the normal Eclipse import process. That being said, importing all the projects is probably a really bad idea, simply because there are so many of them. Import select projects, if and when you need them.
Note, though, that you will have to fix some things up, particularly if you are getting errors:
-
The build target of the project may be an Android SDK that you do not have installed. You will need to set the project build target to something that you have, by means of Project Properties.
-
A few of these projects use ActionBarSherlock or other Android library projects. You will need to attach a suitable copy of those projects to your app. For example, there is a copy of a compatible ActionBarSherlock in
external/, and the project files are set up to reference that copy. If you import it first, your imports of other sample apps should go more smoothly. Alternatively, you can download and set up ActionBarSherlock yourself in your Eclipse workspace, then go into Project Properties and point the book's project to use your copy of the ActionBarSherlock library project. -
Many of the book samples, and ActionBarSherlock, require your Java compiler compliance level to be set to 1.6, so code can use the
@Overrideannotation on interface method implementations. You can find this in Project Properties, in the Java Compiler area. -
Restarting Eclipse, for whatever reason, can clear up some undefined problems indicated by red exclamation marks over the project name in the Project Explorer.