Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I believe you're mixing screen size with pixel density:</p> <p><strong>From the dev guide:</strong></p> <blockquote> <ul> <li>The platform supports a set of resource qualifiers that let you provide size- and density-specific resources, if needed. The qualifiers for size-specific resources are <code>small</code>, <code>normal</code>, <code>large</code>, and <code>xlarge</code>. Those for density-specific resources are <code>ldpi</code> (low), <code>mdpi</code> (medium), <code>hdpi</code> (high), and <code>xhdpi</code> (extra high). The qualifiers correspond to the generalized densities described in <a href="http://developer.android.com/guide/practices/screens_support.html#range" rel="nofollow">Range of screens supported</a>, above.</li> <li>The platform also provides a <a href="http://developer.android.com/guide/topics/manifest/supports-screens-element.html" rel="nofollow"><code>&lt;supports-screens&gt;</code></a> manifest element, whose attributes <code>android:smallScreens</code>, <code>android:normalScreens</code>, <code>android:largeScreens</code>, and <code>android:xlargeScreens</code> let you specify what generalized screen sizes your application supports. Another attribute, android:anyDensity, lets you indicate whether or not your application includes built-in support for multiple densities.</li> </ul> </blockquote> <p><strong>Edit: added my comments to the response.</strong></p> <p>Using the example in the comment, the Archos is a 7 inches screen, while the Nexus One has a 3.7 inches screen. <strong>At the same number of pixels, the density of pixels is double on the Nexus One</strong>. Remember, dpi means dots per inch. <strong>That means that the same image would be rendered twice as big in the Archos than in the Nexus One</strong>. </p> <p><strong>The screen size differences should be handled in the layout</strong>. Use <code>res/layout-normal</code> for the Nexus One and <code>res/layout-large</code> for the Archos. This way, you will have control over the full layout for the different screen sizes (perhaps you need to limit some widgets that would be unnecessarily large in the Archos) and decide whether you want to keep a fixed size for your drawables or expand them as necessary.</p> <p>Alternatively, if you really want to keep size proportional to the screen regardless of screen size and <em>without stretching images</em>, then you can create two sets of images, namely image1-normal.png, image2-normal.png and image1-large.png, image2-large.png, etc, both in the <code>res/drawable-mdpi</code> and the <code>res/drawable-hdpi</code> folders, that you would access from the xml files in <code>res/layout-normal</code> and <code>res/layout-large</code>.</p> <p>In summary, the full requirements should be handled by a combination of layouts and drawables:</p> <ul> <li><strong>Nexus One</strong>: <code>layout-normal</code>, <code>drawable-hdpi</code></li> <li><strong>Archos 7</strong>: <code>layout-large</code>, <code>drawable-mdpi</code></li> <li><strong>Xoom</strong>: <code>layout-xlarge</code>, <code>drawable-mdpi</code></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAndroid Resources Folders by Screen Size
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAdam Nybäck
    1. USAleadam
    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. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFrom the original question, I don't gather the confusion is strictly about size versus density. I understand the frustration is also over handling the overlap between different size/density combinations.
      singulars
      1. PO
      1. USThane Anthem
    2. COYes, that is the problem. For example, Nexus One has 480x800 of screen size, so it's hdpi, but, for example, a Archos 70 also has 480x800 but it's **mdpi**! That is the problem, I don´t understand why two devices with same resolution has different properties and, usually, the graphics are developed by resolution (for example, a background). It's totally frustating.
      singulars
      1. PO
      1. USArturo
    3. CO@Morpheo17 That's because the Archos is a 7 inches screen, while the Nexus One has a 3.7 inches screen. At the **same number** of pixels, the **density of pixels** is double on the Nexus One. Remember, **dpi means dots per inch**
      singulars
      1. PO
      1. USAleadam
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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