如何设置Galaxy Nexus的布局

Question

I'm developing an Android 2.2 application.

Testing my layout with eclipse graphical layout I have a problem: it doesn't look good on Galaxy Nexus.

I have four image types: ldpi, mdpi, hdpi and xhdpi. A layout and four dimens.xml files (ldpi, mdpi, hdpi and xhdpi).

If I modify dimens.xml to make it look well with Galaxy Nexus but it won't look well on other device, eg Nexus One (in eclipse graphical layout). So, I think I need something else.

Reading Supporting Multiple Screens I see there is another approach: instead of using normal, large, etc layout, I could use sw<N>dp . But this is beginning with Android 3.2, and I need to support Android 2.2.

What do I need to add to make it look well on Galaxy Nexus?

Nexus One :

Galaxy nexus :

Answer 1

Another approach I often happen to use it to think like web developers. Try to make your layout look good with layout stretched in whatever direction. Center the important part and make sure the image behind can be stretched in both directions. Then use an imageview for the background and set it to match_parent and scaletype to centerCrop. It doesn't work for everything but I'm pretty sure it would work for your sample.

In your case you could put everything you have right now inside another container (for example a RelativeLayout) then you center it and set the dimensions or make it wrap_content. The new top container should then match_parent and have the imageview I talked about as a child.

Answer 2

You should keep the different densities for the images, for the layouts you want to use screen sizes eg

layout-large instead of layout-hdpi

EDIT

You want to have a folder layout like this:

• res/drawable-ldpi/[your image resources]
• res/drawable-mdpi/[your image resources]
• res/drawable-hdpi/[your image resources]
• res/drawable-xhdpi/[your image resources]
• res/layout/[your layout xml file]
• res/layout-large/[your layout xml file modified for big screens]
• res/layout-small/]your layout xml file modified for small screens]

See this link for further info: http://developer.android.com/training/basics/supporting-devices/screens.html

EDIT2

If you must stick to one layout then you need to edit the values in res/values-large/dimes.xml to affect large screen devices.

If you have and extra large device screen then you'd need to edit res/values-xlarge/dimens.xml and so on for each of the screen sizes.

Answer 3

one of my first questions was very similar to this one .

your problem in short is that you need to have your views placed and resized according to an image that you show on the background . sadly , android doesn't support it without some workarounds .

on silverlight&WPF there is a viewBox that does it automatically . flash has it because it's vector based . iphone has it because all of its screens have the same aspect ratio. but android doesn't have a solution for it yet.

i've even asked this same question in google developers day , and what the lecturer told me was that i should use openGL , even though my app was very simple.

for now , what you can do is :

1. the easy way : use multiple LinearLayout with weights . use views inside them with weights too in order to make rules about the positions and sizes. Lint will tell you that it is bad for performance , but if your views are not moving/resizing at all , it should be ok .

2. the advanced way: create your own layout , which will know exactly where to put views (and in which size) in relation to what you give to it. i've done it in the past , but i used imageViews instead of buttons (because i had to) .

there is also a bug with this approach (also found on solution #1) : on some screens their images didn't fit with the background image. if that's not your case , you can do it too.

3. the hardcore way : use openGl . it's will be easier to use third party libraries like andEngine or LibGdx .

4. the web-developers way : put it all in a website , show it, handle touches using an interface with android .

5. the no-buttons way: if you don't want to use the buttons , you can use simple math in order to know where the user has pressed , and not use any of the above solutions .

btw , if you stretch the image like what i see , it won't keep its aspect ratio . you need to handle it too . using openGl can help you with that.