Hi all, I'm not sure how much it is worth getting into the details of this right now. There is a blog post being written on the topic of different screen sizes, and we have gone through round after round of work on the underlying model of the platform and how to best explain the way this works, which is reflected in the doc. I think ultimately it is going to be much more confusing trying to answer questions piecemeal here rather than waiting for the full documentation that is well organized (first covering the concepts being used and way we look at different screen configurations, then how these impact applications, how they can opt out of different compatibility modes, and details of how old and new APIs work in these environments).
Also, please don't base any of your work in this area on 1.5. There was a lot of half-done stuff in that platform that was early work on supporting these different screen configurations, but it was very incomplete, and in many cases behaves radically different than 1.6. As usual, our goal is that the bulk of existing apps will just work on the new types of hardware, though with a new wrinkle that on some kinds of screens (smaller) there is no way for the platform to provide compatibility for existing apps so they will be filtered out by market until they are updated. But this will be covered in the upcoming blog post and documentation. On Tue, Sep 8, 2009 at 9:06 AM, Howard M. Harte <hhar...@gmail.com> wrote: > > > > > > No. Like I said, 160 dpi at other resolutions means a very different > > screen size. I mentioned WVGA/5" already, but now imagine the size of > > a q...@160dpi display... it would be very tiny. The point is that it > > wouldn't help you at all. > > > > This makes sense, but is there a way to leave minSdk="3" and turn off > compatibility mode, so my app will fill the entire WVGA screen in > medium DPI, since my app already can scale properly? Like I > mentioned, this works fine with minSDk="4" but I don't want to > restrict my app to the v1.6 SDK. > > Also, it would be nice to be able to prevent the soft keyboard IME > from forcing full-screen/extract mode for landscape WVGA at medium DPI > since now there is a lot more display real estate, and extract mode > makes less sense. > > Thanks, > Howard > > -- > > 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 > > > -- 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
