All of the comments above are very informative and give good guidance. My 2 cents to this thread is:
1. You'll never understand an API thoroughly by just reading the documentation. No matter how good the documentation is, just reading it is never going to be enough. 2. No matter how clear/unclear the documentation is, you should start trying things, based on the examples given in the documentation. Unless you try things out, experiment with the interface and see what changes cause which difference in behavior you'll never understand how an interface works. I believe anybody who has built knowledge on any programming framework uses this, or some derivate of this approach. ------------------------------------------------- Ali Chousein http://www.codeproject.com/KB/android/PayGol-Android.aspx http://weatherbuddy.blogspot.com | http://twitter.com/weather_buddy http://geo-filtered-assistant.blogspot.com https://marketplace.cisco.com/apphq/products/994 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
