Errata

When launching DDMS in Eclipse Helios SR1, it is listed under "Other" under the Window > Open Perspective menu.

Note from the Author or Editor:
We need to verify this!

In the implementation of the service() method of the TemplatedService() class, there should be a semicolon after the runService() method call.

Note from the Author or Editor:
The semicolon is missing in the code at the top of page 46, the last line of the service() method.

In the example describing the behavior of thrown exceptions, the text states that "control returns to getActions"; however, the uncaught exception which occurs in readPageFromNet() would cause control to be returned to the caller of readPageFromNet(), which is getPage() (not getActions()).

Note from the Author or Editor:
fixed

"The marshaler's job is to write everything necessary to reconstruct the object state to the passed Parcel. Typically , this will mean expressing the object state in terms of the six primitive data types: byte, double, int, float, long, and String. "


The String is not a primitive data type.

Note from the Author or Editor:
This is accurate, though splitting hairs

The variable dotModel is defined but never used in the code listing. Also on Pg 182, while defining the interface method onDotsChange(..) Dots d is passed in as parameter. In the method body, Dot d = dots.getLastDot(); is defined. There seem to be typos.

I think the variable name is wrongly defined ... there is no definition for dots in the class.

Should we be changing the line:

final Dots dotModel = new Dots();

to

final Dots dots = new Dots();

AND

pubic void onDotsChange(Dots d)

to

public void onDotsChange(dots)

Make more sense ?

Pls correct me if I am wrong. It changed my perception of what you are passing into the interface method called and the underlying concept being explained ??

Thanks,
B Rgds
Rajive

Note from the Author or Editor:
On pp 182, I do not believe that dotsModel is incorrectly named. The parameter to onDotsChange should be "dots", not "d"

On page 204, the factory method in the source code listing is named "createInstance".

Lower down when using this factory in SimpleFragment's onCreate method, you call it "newInstance" instead.

On page 206, you also use "newInstance".

Note from the Author or Editor:
verified

The example code:
UPDATE contacts SET height_in_meters = 10, last_name = "Jones"
should end with a semi-column. This would make it consistent with all the other example SQL statements in the book.

Note from the Author or Editor:
mmm.... We should be consistent, but I'm not sure which way...

States there are two important constants, however four are shown.

Note from the Author or Editor:
yep. "two" should be "four"

The method 'createVideosTable' is mentioned. However, in the code sample this refers to there is no such method. The method 'createTable' was the method probably intended. This mistake is repeated on the top of page 264.

Note from the Author or Editor:
I've named the method back to "createVIdeosTable", I think thats better, so now the text is correct...

The method 'onUpdate' is mentioned, but there is no such method. Instead the method 'onUpgrade' is probably intended. This method is referred to three times in this paragraph, including one time on the subsequent page.

Also, in this paragraph the class 'SimpleVideoContentProvider' is mentioned. However, 'SimpleVideoDbHelper' is probably what was intended.

Note from the Author or Editor:
yep

The onUpgrade method for SimpleVideoDbHelper is very simple: it deletes the
database. When the provider tries to use it later, Android will call the onCreate
method because it does not exist

The above statements didn't match the following onUpgrade method defined on page 262:

public void onUpgrade(SQLiteDatabase sqLiteDatabase,
int oldv, int newv)
{
sqLiteDatabase.execSQL("DROP TABLE IF EXISTS " + VIDEO_TABLE_NAME + ";");
createTable(sqLiteDatabase);
}

onUpgrade method deletes the database and then calls createTable() to create the database. Thus, Android won't call the onCreate method because it exists already.

Note from the Author or Editor:
The "Thus" might be confusing?

The streetview calls have been deprecated and there is now a different mechanism to get streetview working. So the streetview menu in the app no longer works.

Note from the Author or Editor:
Looks like this is true. We probably will need to update the example.

BaseColumns was treated as a class at two places in the following paragraph on page 311:

The CONTENT_URI must be of type public static final Uri. It is defined in the Finch
Video class of our simple video application. In our public API class we start by extending
the class BaseColumns, and then define a string named AUTHORITY:
public final class FinchVideo.SimpleVideos extends BaseColumns {
public static final String SIMPLE_AUTHORITY =
"com.oreilly.demo.pa.finchvideo.FinchVideo";

BaseColumns is a public interface (i.e., not a public class) and thus "implements" should be used instead of "extends".

Note from the Author or Editor:
COnfirmed. Note sent to submitter

deleteOld() tries to delete the old cached file like this:
mFinchVideoProvider.deleteFile(ID);
This is wrong because ID is the record ID from ID_COLUMN.
You should get file name from MEDIA_ID_COLUMN and use that to delete file.
String Media_ID = old.getString(FinchVideo.MEDIA_ID_COLUMN);
mFinchVideoProvider.deleteFile(Media_ID);

Great book! Thanks.

Note from the Author or Editor:
I sent mail to the reader, yes, this appears to be a bug. I'll fix for next version.

In the following method, "initialValues" in the last return statement should be replaced with "values":

public Uri insert(Uri uri, ContentValues initialValues) {
......
ContentValues values;
if (initialValues != null) {
values = new ContentValues(initialValues);
} else {
values = new ContentValues();
}

SQLiteDatabase db = getDatabase();
return insert(uri, initialValues, db);
}

i.e., the above return statement should be as follows:
return insert(uri, values, db);

Note from the Author or Editor:
Code in the text is incorrect.

Chapter "Final and Static Declarations":

Throughout the chapter non-static members are called dynamic.

Static does not imply dynamic nature of members, but rather membership: is it part of the instance or not.

Dynamic implies that member is somehow changeable, which is misleading.

Standard name for non-static members are instance members, so it is not about static vs. dynamic, it is about static vs. instance member.

Note from the Author or Editor:
Note sent to submitter