Dianne,

To finish that dreaded SlidingDrawer topic - yes the use of the
SlidingDrawer was in the Layout xml file only so I guess its was a
loophole that I end up using without realizing.

Thanks for your comments on the rest of the issues.

I think we all agree that changes in the APIs happen and will happen.
All we want is an advance notice so we can proactively react to them.

In my experience probably a good start is to have:
1. Good Change List
2. A single pace where Google (and probably partners) can push
emulator images (or ways to build them) for the various API releases
and platforms.

This will be a huge help to ensure we are ready for the new releases.






On Feb 9, 11:32 am, Romain Guy <romain...@google.com> wrote:
> >Currently the app lifecycle for the user is:
> >Download app -> get OTA -> broken app -> wait for app update ->
> >download app update -> working app -> get OTA -> broken app -> wait
> >for app update -> download app update -> working app -> ..
>
> Which is exactly why we tell developers not to use private APIs.
>
> But that's not your case and I already apologized for the lack of
> changelog for the current update. And you're right the SDK should also
> go out to developers before the update reaches the users. The good
> news is, it is what we want to do for Cupcake :)
>
> --
> Romain Guy
> Android framework engineer
> romain...@android.com
>
> Note: please don't send private questions to me, as I don't have time
> to provide private support.  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
-~----------~----~----~----~------~----~------~--~---

Reply via email to