On Tue, Sep 14, 2010 at 2:30 PM, DanH <[email protected]> wrote: > Not really. A reference should be coherent and well-organized. >
What's so incoherent and disorganized about the current documentation? Specifics might help bring more attention to the parts that need it. > I've run across several diagrams of the application state flow, for > instance, and most are clearly wrong > In the official docs? Can you point them out? > And descriptions (no diagrams that I've found) of the Intent resolution > algorithm are similarly inconsistent. > Can you point these out as well? ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
