This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Android and the fly likes Source for the book Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Mobile » Android
Bookmark "Source for the book" Watch "Source for the book" New topic
Author

Source for the book

Johan Pelgrim
Ranch Hand

Joined: Jul 07, 2003
Posts: 105

Hi Carlos,

Welcome!

Your book title indicates you have been digging around the source code to find the nitty gritty about the Android Framework. In your opinion, did you see an increase API documentation updates during the time you have written the book and have done your research? What areas are still lacking (in documentation) and contain real gems (which hopefully are described in your book?)

When I browse around the source code I something get the experience Google is taking a considerable amount of effort to work around their own framework. Did you encounter any of those hacks as well? What scared you the most?

How future proof are the hacks described in your book? Are they clean and working 'with' the framework, so we can depend on them in the future. Or are some so hacky they need attention after every new release of the SDK?

Kind regards,

Johan.


Johan Pelgrim, The Netherlands
SCJP 1.4, SCWCD 1.4, SCBCD 5.0
Carlos Sessa
author
Greenhorn

Joined: Apr 17, 2013
Posts: 14
Johan Pelgrim wrote:Hi Carlos,

Welcome!

Your book title indicates you have been digging around the source code to find the nitty gritty about the Android Framework. In your opinion, did you see an increase API documentation updates during the time you have written the book and have done your research? What areas are still lacking (in documentation) and contain real gems (which hopefully are described in your book?)

When I browse around the source code I something get the experience Google is taking a considerable amount of effort to work around their own framework. Did you encounter any of those hacks as well? What scared you the most?

How future proof are the hacks described in your book? Are they clean and working 'with' the framework, so we can depend on them in the future. Or are some so hacky they need attention after every new release of the SDK?

Kind regards,

Johan.


1)
Android documentation has been improving but I feel there are features that lack of it.
My favorite hack in the book is "The SyncAdapter pattern". The sync adapter is an example of lack of documentation and unfortunately it's one of the best android features.

2)
I am scared about private methods in the framework classes
It happened more than once that I tried to extend a framework class and I reached a private method.

3)
Every hack has the minimun SDK version.
Most of them are 1.6+

Cheers!





 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Source for the book
 
Similar Threads
equivalent to <c:out escapeXML="true"> for servlets?
Struts vs. In House MVC : question for Mr. Neal
Ubuntu Hacks by Jonathan Oxer, Kyle Rankin, Bill Childers
Tivo Hacks by Raffi Krikorian
Learning Java (open source) API's - Like a scientist or an end user ?