StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14151256
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-04T04:52:17.450
FavoriteCount
0
LastActivityDate
2013-01-04T05:20:21.667
LastEditDate
2013-01-04T05:20:21.667
LastEditorUserId
1531054
OwnerUserId
1531054
ParentId
14151121
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
AFAIK there are two kinds variables for device display : pixel density and screen dimensions. Both are theoretically independent, though in market both vary together from low end to high end devices. Pixel density demands for different bitmap resolutions and level of detail (36X36 to 96X96 icons for example) . Screen dimensions demand for better use of real estate ( Multi activity layout for phones, combined fragmented layout for tablets, for example). Not as important as pixel density, but good to have, because tablet users might find a phone layout too bland, and waste of screen space. So: <ul> <li>To cover most pixel densities you will have to have different <a href="http://developer.android.com/training/multiscreen/screendensities.html" rel="nofollow">versions of drawables</a> : <code>ldpi,mdpi,hdpi and xhdpi</code>. Prefer nine-patch drawables, these are a lot better at fitting everywhere. </li> <li>To cover most screen sizes you will have to have different <a href="http://developer.android.com/training/multiscreen/adaptui.html" rel="nofollow">layout arrangements</a>, and a <a href="http://en.wikipedia.org/wiki/Responsive_web_design" rel="nofollow">responsive</a> <a href="http://developer.android.com/training/multiscreen/screensizes.html" rel="nofollow">layout design</a> for <code>small,large and xlarge</code> values. Also, different layouts for portrait, and landscape orientations are good to have sometimes.</li> <li>Android lets you mix configuration combinations too. E.g. <code>drawable-large-hdpi</code> etc.</li> <li>Avoid hard coded pixel co-ordinated and dimensions at all costs, use density or percentage.</li> <li>Its Way better to have one flexible nine-patch drawable than to have different drawables for different screen sizes.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid supporting all tablets - categorize drawables and layouts
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USS.D.
UserOwnerUserId
1. USS.D.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.