In the case of a kiosk app you'd need to build it into the ROM. Since the honeycomb source hasn't been released you'll have a hard time with that. Looks like your best bet would be to base it on a 2.3 ROM and have the app work for xlarge screens. That means porting 2.3 yourself, most likely.
If it's just a cosmetic thing, you can put it into lights out mode, which dims the buttons (see the youtube app), but does not remove the bar. On Jul 28, 6:42 pm, Zsolt Vasvari <[email protected]> wrote: > I see this a legitimate use case for a kiosk app. But he cannot do > this right now, simple as that. > > On Jul 29, 4:36 am, Mark Murphy <[email protected]> wrote: > > > > > > > > > On Thu, Jul 28, 2011 at 4:29 PM, Richard Lalancette > > > <[email protected]> wrote: > > > The navigation bar breaks the look and feel of our app > > > You have *got* to be kidding me. You're willing to crash an OS because > > the system bar "breaks the look and feel" of your app? You're one sick > > puppy. > > > > and we do not need to > > > go to the desktop once our app is started. > > > You are welcome to write your own firmware that eliminates the system > > bar, as Ms. Hackborn advised. You will need to wait until the source > > code for Honeycomb is released, of course, which may be several months > > away. > > > -- > > Mark Murphy (a Commons > > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > > Android Training in NYC:http://marakana.com/training/android/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
