Hi,

Well I know, that this is just a pre-release bla . bla . bla,
but still this doesn't justify everything.

Wouldn't it be nice to have the documentation at least halfways
accurate?
Or if it's not accurate to add at some kind of 'obsolete' marker to
certain chapters.
This can be done very quickly and helps users.

The very first thing I looked up was docs/guide/developing/other-
ide.html

Creating an Android project still talks about "activityCreator" ,
which doesn't exist any more.

Additionally the example still talks about activityCreator.py (which
didn't even exist in the previous release under linux)

My suggestion to the Google team would be to at least mark all
chapters as obsolete, which might have to be rewritten.
If the document changes are already known, the obsolete marler could
already point to some kind of release notes file with the anticipated
changes.

In my example this could have been a reference to 
http://developer.android.com/sdk/preview/
"Where is activitycreator"

I think this suggestion might help to get rid of quite some un
necessary support questions.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to