19.10.2011 11:03, Doug пишет:
Well, in my case, it is desirable if not perfect. :-(
I work on a very high profile app and I've been in contact with a
Samsung rep who is encouraging us to support the Galaxy Note for the
home screen that is having problems with layout on its display. I
have been assured that it will be shipping with Gingerbread and being
"large". (They are also testing the app on a device that they will
not share with us.)
According to the chart here:
http://developer.android.com/guide/practices/screens_support.html#range
.... the Galaxy Tab should be a "Normal" screen, if I'm reading it right.
But I guess they want apps to look like they do on a tablet - do you
know if they're going to include a magnifying glass?
With this resource qualifier for screen dimension, does anyone know if
it is width x height or the other way around, or does it matter at
all?
It's "width x height" (switched in land mode, too). I guess it's been
taken out of the documentation.
And... psst... you didn't hear about this from me :)
-- Kostya
Doug
On Oct 18, 3:37 pm, Kostya Vasilyev<[email protected]> wrote:
Those resource qualifiers exist at runtime since 1.6, but the official
position (as posted by Dianne Hackborn on this list) is that it's not
desirable to use them because they are too specific.
I wonder if there is a better way, perhaps that device will actually ship
with ICS, or perhaps it won't present itself as -large?
--
Kostya Vasilyev
19.10.2011 2:22 пользователь "Doug"<[email protected]> написал:
There is a curious thing I noticed about the ADT tooling this week
when using the New Android XML File feature. It allows you to select
any number of resource qualifiers and will conveniently create the
folder for that configuration, which is great. But I noticed that it
has a qualifier for "Dimension", which when added to your chosen
qualifiers, asks you for two numbers (width and height, presumably).
The numbers you enter get placed into your folder name like this:
layout-large-WxH
Where W and H are width and height. Or they could be reversed, I
don't know. The point is that this kind of resource qualifier is
documented NOWHERE as far as I can tell. ADT is the only thing that
apparently understands this. And to be honest, I haven't tested to
see if it works on a real device, but I'm skeptical that it would
work.
The context for all this is that I'm trying to target the upcoming
Galaxy Note screen. It's unique in that it's a "large" screen that is
also "xhdpi" at 1280x800. My large layouts are meant for tablets, but
the Galaxy Note just isn't wide enough in portrait to do what we do on
real tablets. In fact, it probably shouldn't even be classified as
"large" given its effective width in dp. And since the Galaxy Note
doesn't target Android 3.2 so we can't use the new min width and
height qualifiers. So I'd love to target just 1280x800 if possible to
work around this one device for now.
Doug
--
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
--
Kostya Vasilyev
--
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
