Dianne, Behavior of the Status bar expanded view (and search dialog) is same even in android 2.0 (Eclair - build sdk from source). They don't cover entire screen if I run emulator with 480x800 (160dpi) skin. seems like I'm missing something obvious here, but not able to locate it. Can't we have other then 240 dpi for larger screens?
Thanks Thote On Nov 20, 10:00 am, Dianne Hackborn <hack...@android.com> wrote: > Sorry no, as I said, we haven't implemented the UI for larger screens. > You'll need to go into the code of whatever is not working and tweak it > appropriately. > > > > On Thu, Nov 19, 2009 at 6:56 PM, TG <thotegowda...@gmail.com> wrote: > > Dianne, Yes, we did customized status bar UI (was in 1.5r3). Now in > > donut, the problem is the status bar expanded (and also search) dialog > > is getting displayed in 320x480 area, even though we are running > > emulator with 480x800 skin. Any thoughts? > > > Thanks > > Thote > > > On Nov 20, 7:14 am, Dianne Hackborn <hack...@android.com> wrote: > > > It's set somewhere where the default flags for aapt are set -- look > > through > > > the build system makefiles for where aapt is defined. It is based on the > > > version information defined for the build system. > > > > Sorry I don't know about the search dialog. Do keep in mind, though all > > of > > > this screen support was introduced in the platform in 1.6, it is only 2.0 > > > where we have implemented full support for high density screens across > > all > > > UI and apps, and have not done this for any other new screen > > configuration. > > > So you need to expect to do some work with parts of the UI to get them > > to > > > behave on these other screens, and I really have no idea what all those > > may > > > be. (And honestly, I would question whether things like the current > > status > > > bar UI make sense as-is on a larger screen; those are ripe for rework.) > > > > On Thu, Nov 19, 2009 at 6:02 PM, TG <thotegowda...@gmail.com> wrote: > > > > Thanks Dianne. > > > > > Can you please tell me where exactly this flag is getting set in the > > > > current build system? And also How to make the expanded status bar and > > > > the search dialog to cover entire screen when running emulator with > > > > 480x800 skin? > > > > > Thanks > > > > Thote > > > > > On Nov 20, 6:12 am, Dianne Hackborn <hack...@android.com> wrote: > > > > > The build system automatically builds applications to target the > > current > > > > > version, if they haven't otherwise specified a version in their > > manifest. > > > > > It's just a matter of passing a flag to aapt when building an app. > > > > > > On Thu, Nov 19, 2009 at 1:34 AM, TG <thotegowda...@gmail.com> wrote: > > > > > > Hi, > > > > > > > We are porting Donut (1.6r1) to a WVGA (480x800) device. When we > > > > > > install and run an application, which doesn't contain neither > > <uses- > > > > > > sdk> nor <supports-screens> tag, application covers only small area > > of > > > > > > the screen. if we use <uses-sdk> tag with value 4 in manifest file, > > it > > > > > > work fine. But All default applications (comes with Android > > source) > > > > > > works fine without any <uses-sdk> or <supports-screen> tag in their > > > > > > manifest file. > > > > > > > Where exactly is the difference between default android > > applications > > > > > > and sdk built applications? How can I make all applications to run > > in > > > > > > full screen without any <uses-sdk> tag in manifest file? > > > > > > > One more strange observation is that Status bar expanded view and > > > > > > Search dialog will not cover entire screen if you run emulator with > > > > > > 480x800 skin. why? > > > > > > > Thanks > > > > > > Thote > > > > > > > -- > > > > > > unsubscribe: > > > > > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com> > > > > > <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com> > > <android-porting%252bunsubscr...@googlegroups.com<android-porting%25252bunsubscr...@googlegroups.com> > > > > > > > website:http://groups.google.com/group/android-porting > > > > > > -- > > > > > 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. > > > > > -- > > > > unsubscribe: > > > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com> > > > > > website:http://groups.google.com/group/android-porting > > > > -- > > > 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. > > > -- > > unsubscribe: > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting > > -- > 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. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
