StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20814504
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-12-28T12:22:29.290
FavoriteCount
0
LastActivityDate
2013-12-28T12:22:29.290
LastEditDate
LastEditorUserId
0
OwnerUserId
938089
ParentId
20814282
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
What you're requesting is a highly-demanded feature (though not implemented yet), see <a href="https://code.google.com/p/chromium/issues/detail?id=25317" rel="nofollow" title="Issue 25317: Help extensions authors make options pages with a consistent look">Issue 25317: Help extensions authors make options pages with a consistent look</a> on Chromium's bug tracker. When you implement an options page, you could take either of the two next methods: <ol> <li>Implement a pixel-perfect UI that looks identical on Linux, Mac and Windows.</li> <li>Implement a UI using native controls of the relevant platforms.</li> </ol> I suggest to follow approach 2, because the most important part of an options page is the ability to quickly set preferences. This is achieved by using controls that are familiar to the user. So, start with the basic unstyled HTML to get the main purpose right. E.g.: <pre><code><label> <input type="checkbox" id="some-option-id"> Some option </label> </code></pre> When you've done that, you could dress up the UI with CSS if you wish. But don't overdo it: users should still be able to recognize a checkbox. If your app specifically demands for platform-specific colors, use CSS color keywords such as <code>ButtonFace</code>, <code>ButtonText</code>, <code>CaptionText</code>, etc. You can find more of these keywords <a href="https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/web/WebColorName.cpp&q=buttonface&sq=package%3achromium&dr=C&l=43" rel="nofollow">in Chromium's source code</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POChrome Extension User Interface
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRob W
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
CommentsPostId
1. COthanks I know the native is good but consistent look and feel will help porting the extension for other platforms and browsers, I suppose. That is why I asked for a CSS or Javascript library.
 singulars
 PostPostId
 PO
 UserUserId
 USXunshirine
2. COWhat problems are you trying to solve? If your HTML is sane, your options page will look all right on every platform/browser. Generic library recommendations are off-topic on Stack overflow, because answers tend to become outdated and opinionated. You should not use a library for the sake of using a library, but define the requirements, then look for a library. That makes it easier to find the right framework/library (Google is your friend).
 singulars
 PostPostId
 PO
 UserUserId
 USRob W

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.