Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Generally, you'll find mobile usability folks <a href="http://www.uxmatters.com/mt/archives/2013/03/common-misconceptions-about-touch.php" rel="nofollow">talking about millimeters</a>. But programmers and visual designers talk about density-independent pixels or points (1 Android "DIP" = 1 iOS "point") because even if you could specify a measurement in millimeters exactly, you'd end up with rounding issues or half-pixel anti-aliasing ugliness:</p> <p>1mm equals 6.3 DIP (degree of precision there depends on the exact DPI value of the screen, since dip are quantized to the nearest of 120/160/240/320/480/640 dpi). That means on a standard G1-style 160DIP screen, if you specify a button as (let's say) 8mm, it'd be 50.4 pixels on that screen - good luck rendering that with any degree of precision, or telling Photoshop to end a line exactly 50.4px. And just rounding isn't much of a solution; the screen is still a fixed total width in pixels, and those rounding errors would compound in ways that mess up symmetry if you're (let's say) laying out a grid of buttons with specific sizes and padding amounts.</p> <p>Specifying that as (let's say) 48DIP is much better, since that smoothly scales: 48px at 160DPI, 72px at HDPI (240) and 96px at 320DPI (AKA 2x in iOS terminology), no fractional pixel rendering or rounding needed.</p> <p>As to why exactly the 160DPI pixel won out as the 1x mobile unit of measurement for the density-independent pixel, blame the first few iPhones and the HTC G1, which shared that configuration.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy aren't standard physical length units like mm used for touch UI layout?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USYoni Samlan
    1. USYoni Samlan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy aren't standard physical length units like mm used for touch UI layout?
      singulars
      1. PTQuestion
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAh, so using a unit like dp makes it easier to size things so that they still end up on pixel boundaries, even if the pixel density changes. I guess you could still run into ugly rounding in some cases (say, 13dp on 240DPI would be 19.5px), but it does definitely make it easier. Makes sense. Thanks!
      singulars
      1. PO
      1. USMatti Virkkunen
    2. COYeah, that's really an Android issue only; iPhone only has MDPI and XHDPI, which works out pretty cleanly as always 2x the DIP measure. LDPI, HDPI, and XXHDPI+ can cause those fractional/rounding issues on Android unless you use 4DIP multiples only, since LDPI and HDPI end up being 0.75x and 1.5x respectively.
      singulars
      1. PO
      1. USYoni Samlan
 

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