I don't have any solid plan. I was thinking in donut I would just remove the mid policy. It would then need to be put back by someone in a way that it can be better maintained.
On Wed, Apr 1, 2009 at 10:59 PM, Chen Yang <sunsety...@gmail.com> wrote: > > Thanks for let us know your plan. Then would you like to share the > anticipated date for the refactored code? > Thanks. > -- > Chen > > On Thu, Apr 2, 2009 at 1:46 PM, Dianne Hackborn <hack...@android.com> > wrote: > > On Wed, Apr 1, 2009 at 10:41 PM, Chen Yang <sunsety...@gmail.com> wrote: > >> > >> Yes, eee_701 is using the mid policy at present. And that policy > >> doesn't seem well maintained. > > > > It is not maintained at all. Actually I am close to deleting it from the > > tree because it is completely not in sync with the current cupcake tree. > :/ > > I don't think it makes sense to keep it in its current form; we need to > > refactor a lot of the generic stuff in PhoneWindowManager into a common > base > > class. > > > > -- > > 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. > > > > > > > > > > > > > -- 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. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
