Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>AbsoluteLayout is depricated. There are many better ways of accomplishing this with the use of an AbsoluteLayout.</p> <p>A GridView will work well if you don't care about how many items are in each row. This is an easy way to deal with multiple screen sizes.</p> <p>If you need exactly 9 in each row, you can use a <a href="http://developer.android.com/reference/android/widget/TableLayout.html" rel="nofollow">TableLayout</a>. See <a href="http://developer.android.com/resources/tutorials/views/hello-tablelayout.html" rel="nofollow">TableLayout tutorial</a> for a good introduction.</p> <p>Basically I would create a TableLayout with 9 rows. Each row would contain horizontal LinearLayout with 9 ImageViews. </p> <p>To prevent the image from stretching, make sure you set the <a href="http://developer.android.com/reference/android/widget/ImageView.html#attr_android%3ascaleType" rel="nofollow">scaleType</a> to fitXY and the <code>layout_width</code> and <code>layout_height</code> of the ImageViews and LinearLayouts to <code>WRAP_CONTENT</code>.</p> <p>You also need to keep in mind the many different screen densities available on phones. A 48x48 pixel image might work ok on one density, but probably won't look good on a high density phone with a large screen size. See <a href="http://developer.android.com/guide/practices/screens_support.html" rel="nofollow">supporting multiple screen sizes</a> for a good overview. Basically, you'll want to have different image resources for different screen densities.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload