Let me clarify a little. It's a list view that will display other
people's icons that they will have to supply, so I don't/won't have
total control of them, but I can ask that they be supplied in x number
of formats. I need to keep the number down because of that, and some of
the graphics will include some text in them, so I don't think stretching
them will be an option. The fact is that I will not have any idea of
what the graphic actually is or what it contains, and they will be
supplied by many different sources, and most of them will be added long
after my app is written (they will be uploaded to my website and
downloaded by the app), so I can't depend on anything that would require
stretching.
For portrait orientation, I think I am safe in saying that the larger
icons will be put into a layout that specifies horizontal center, so if
they are not quite the width of the screen in portrait orientation it's
ok, they will just be centered and take up that entire row in the layout
(I haven't written it yet, so that could change, but it's the what I am
thinking about). Then the same icon will be used for the landscape
orientation for the same phone, obviously with a different layout, and
probably with text beside them.
For the smaller icons they will be in the typical position in the list
view on the left side, with text beside them, so this one is simpler,
just need to choose the correct icon size. From the reading I've done it
looks like 24x24 for small screens, 32x32 for normal and 48x48 for large.
Sincerely,
Brad Gies
-----------------------------------------------------------------------
Bistro Bot - Bistro Blurb
http://bgies.com
http://bistroblurb.com
http://ihottonight.com
http://forcethetruth.com
-----------------------------------------------------------------------
Everything in moderation, including abstinence
Never doubt that a small group of thoughtful, committed people can
change the world. Indeed. It is the only thing that ever has - Margaret Mead
On 29/09/2010 5:23 PM, Mark Murphy wrote:
On Wed, Sep 29, 2010 at 8:10 PM, Brad Gies<[email protected]> wrote:
The second image is for the detail view and it basically should fill the
entire width of the screen (roughly, it's ok if it doesn't use the entire
width as long as none of it is chopped off). The size I use for my G1 is
468x60.
Saying you want something to "fill the entire width of the screen" is
fine. Saying you want a bitmap to "fill the entire width of the
screen" is likely to be a source of trouble. That's mostly because
"the entire width of the screen" has so many possible values:
-- 240
-- 320
-- 400
-- 432
-- 480
-- 800
-- 854
And that's just with the six smartphone sizes for which we have
built-in emulator configurations with Android 2.2. Add in some XGA
tablets (768 and 1024) and 1080p televisions (1080 and 1920) and
whatever else comes about in the next few months, and things will get
that much more complicated.
Since we don't really know what the graphic is or what you mean by
"it's ok if it doesn't use the entire
width as long as none of it is chopped off", it's tough to give precise advice.
Here are a few ways of doing something that will "fill the entire
width of the screen" without a preposterous number of images:
-- Use a nine-patch PNG, if the image can reasonably be stretched
-- Use a ShapeDrawable, if the image is a gradient or something that
can be stretched
-- Use a smaller image that blends into a background defined as a
solid color or a ShapeDrawable or a nine-patch PNG, so the smaller
image can be done with just three flavors for the different screen
densities so it is a reasonable size for all
Or, come up with another GUI design that does not require an image to
"fill the entire width of the screen".
There are probably other solutions as well, but these are the ones
that pop to mind right away.
--
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
