TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Pixels don't matter

10 pointsby aaronpkover 11 years ago

4 comments

leofseigeover 11 years ago
When describing how you&#x27;d like raster art to display, you can use the &quot;Density-independent pixel (dp)&quot; unit described here: <a href="http://developer.android.com/guide/practices/screens_support.html" rel="nofollow">http:&#x2F;&#x2F;developer.android.com&#x2F;guide&#x2F;practices&#x2F;screens_support...</a><p>Thanks for taking the time to share this. I&#x27;d like to hear more about why your devs actually <i>need</i> pixel units specified, instead of implementing a scalable interface based on percentages.<p>You&#x27;ve done this with the &quot;13.75%&quot; left and right margins -- why not do this for most elements as well (eg, GO button is 14% screen height -- abbrv. as &#x27;sh:14&#x27;).
nikolaswiseover 11 years ago
The DP is the right direction to go, same with the XCode &#x27;point&#x27;. I think both still need to be conceptually separated form Pixels further. As for going entirely relative, There are some things that need to be solidified - mainly type treatments - as well as the elements that surround those elements - like padding, margin, and measure.
themrdarknezzover 11 years ago
Well they sorta do. Couldnt read the article because it was only designed for desktop.
j_sover 11 years ago
They do when they&#x27;re #f24613 -- my eyes!