Also worth mentioning -- the HC system bar works well partly because of the introduction of the concept of "lights out mode" and it never being possible for an application to cause it to go away. If you are putting your navigation buttons in this new bottom status bar, you will need to do something similar though of course you can't actually have an API for a lights out mode for third party apps to use. You definitely can't allow the bar to be hidden by the application, for two reasons: (1) it will result in a broken UI where an application has asked to go full screen, caused the bar to be hidden, and now the user has no way to get out of the app; and (2) it creates a security hole where an app can spoof something like the home key and bring the user into their own app at that point without them realizing what is going on.
On Sat, Apr 30, 2011 at 2:40 PM, Dianne Hackborn <[email protected]>wrote: > There is no magical thing to do. You will need to rewrite a lot of code -- > for example the way the sliding of the notification panel works will all > need to be rewritten to deal with this. There is also a good chance that > PhoneWindowManager where it does the layout of the screen is not prepared > for this, as well as various other places. > > As of the GB code, the platform has never been run like this, so expect a > variety of at least small problems across the framework as things just > encounter a situation they never have before. > > > On Sun, Mar 6, 2011 at 11:57 AM, samuelhalff <[email protected]>wrote: > >> Hi, >> >> I'm trying to get my Gingerbread status bar to move to the bottom of >> the screen. But the framework is different in GB, and I'm quite lost.. >> The idea is to quickly access status-bar-added soft buttons on a hard- >> button-less device. >> >> I've read the source code for hours, and found a few intersting lines, >> but havent found anything conclusive. I've yet managed to move the bar >> to the bottom, by changing the systemUI's gravity to BOTTOM >> (statusbarservice.java). That works ok, but of course, nothing else >> does. By that, I mean the rest of the screen isn't working. I can see >> the background image, but all other elements are missing. >> So it seems the architecture is built around the idea that the status >> bar is at the top of the screen. >> >> I'm not hoping for anyone to hold my hand throughout the process of >> changing my framework, but if some generous mind could give me a few >> clues as to how to proceed. Maybe a few hints about which file will >> require my attention. And maybe a general explanation of how the >> system is built around the bar.. Anything will help, after so many >> hours of reading, I'm starting to get dizzy. >> >> I sure hope you understand that I'm willing to take the time to learn, >> but a little shortcut never hurt anyone. >> >> -- >> unsubscribe: [email protected] >> website: http://groups.google.com/group/android-porting >> > > > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > 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 [email protected] 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. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
