I am personally pretty opposed to including source in the formal -SDK- for a couple reasons: 1. The source is not documentation. You should be coding your application against the SDK specification in the documentation, not whatever some current implementation is in the platform. 2. Yes, the documentation can be improved. It is important to get feedback on where the pain points are in the documentation, rather than providing source code to cover up those problems.
On Mon, Sep 21, 2009 at 8:36 AM, Eric M. Burke <burke.e...@gmail.com> wrote: > > I do understand that sources are available at source.android.com, but > it would save people time if a src JAR were bundled with the SDK > download. > > http://code.google.com/p/android/issues/detail?id=979 > > This seems like a reasonable request. I know I've personally spent > many hours on previous SDKs trying to learn how to check out the > source and configure it properly in Eclipse. > > > On Sep 16, 1:15 am, Romain Guy <romain...@google.com> wrote: > > > Guys, is there any particular reason for you not to include sources in > > > 1.6 as well? > > > > Sources are available at source.android.com. > > > > -- > > Romain Guy > > Android framework engineer > > romain...@android.com > > > > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
