Thanks for the fast reply Dianne. I think I understood the whole density/size vs pixels approach, but this is an issue about aspect ratios. Android already *has* that distinction with the long/notlong qualifier, just that the WVGA/FWVGA distinction is not made.
My layout is maybe a special case. It is a presentation of a remote control[1] that simply would contain an additional row of buttons on FWGA (or let's say 1.78 vs 1.66 aspect ratio) resolutions. There is no keyboard whatsoever. So am I right that in this case all I have is the deprecated 123x456 qualifier? [1] http://android-xbmcremote.googlecode.com/svn/trunk/Documentation/Images/v0.5.0/remote_portrait.png On Sun, Feb 21, 2010 at 1:04 AM, Dianne Hackborn <[email protected]>wrote: > No, there deliberately isn't. At that level, you really shouldn't be > creating distinct layouts -- I'd strongly encourage you to design a layout > that can resize appropriately to adjust for the screen. (long is to > distinguish between HVGA and large screens like WVGA/FWVGA). > > Larger picture, you really should avoiding having layouts for different > screen sizes as much as possible. You can already see with the number of > sizes we have that this is just not scalable: QVGA, HVGA, WVGA (both med and > high density), FWVGA (both med and high density), and of course both > portrait and landscape versions of all of those. And in the future you > should expect even more varieties (wider screens, larger screens, maybe even > smaller screens). > > Also for a given size -- say FWVGA -- there is not a guarantee of exactly > how much space you may have. For example a device may have a slightly > smaller or larger status bar that impacts the space you have. > > And then if you are taking user input, there is the whole impact of the > soft keyboard being displayed and thus reducing the space available for your > UI during that time. > > So we strongly encourage that developers make use of the dynamic layout > manager in the framework to design their UI to adjust for the exact space > they have available. > > On Sat, Feb 20, 2010 at 3:51 PM, freezy <[email protected]> wrote: > >> Hello there, >> >> This seems like a simple problem to me, but I can't figure it out. I have >> a fullscreen layout that displays differently if the screen is taller (854 >> instead of 800 pixels). I've tried putting the xml into >> layout-notlong-hdpi and layout-long-dpi respectively, but both my WVGA >> and FWVGA emulators go for the "long" version (as described in the doc). >> >> Is there any way to distinguish between the two besides using the >> deprecated -800x480/-854x480 qualifiers? >> >> -- >> 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]<android-developers%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en > > > > > -- > 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. > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- 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
