• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Source for the book

 
Ranch Hand
Posts: 105
Android Mac Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
author
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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!





 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic