StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17383390
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-06-29T18:25:18.057
FavoriteCount
0
LastActivityDate
2013-06-29T20:39:58.643
LastEditDate
2013-06-29T20:39:58.643
LastEditorUserId
77567
OwnerUserId
77567
ParentId
17378046
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
To expand on my comment… Based on your code, I guess you intend to let me specify a string name for each child widget I add to a <code>Container</code>, and then later to access the child widget by name. So you'd expect me to write something like this: <pre><code>class LoginController { Container *container; static const char *kUsernameKey = "username"; static const char *kPasswordKey = "password"; public: LoginController() : container(new Container()) { container->addChild(kUsernameKey, new TextBox()); container->addChild(kPasswordKey, new TextBox()); container->addChild("button", new Button("Log In")); container->get<Button>("button")->setAction([](){ this->login(); }) } void login() { string username = container->get<TextBox>(kUsernameKey)->getText(); string password = container->get<TextBox>(kPasswordKey)->getText(); sendLoginRequest(username, password); } }; </code></pre> Designing <code>Container</code> this way does lookups and type checks at run time, but those lookups and type checks could be done at compile time. Instead, design the API so that I keep my own, specifically-typed references to the children in my own variables. Looking up the children simply becomes using the variables, and no casting is necessary. The lookups and type checks are done at compile time. The code looks like this: <pre><code>class LoginController { Container *container; TextBox *usernameBox; TextBox *passwordBox; public: LoginController() : container(new Container()), usernameBox(new TextBox()), passwordBox(new TextBox()) { container->addChild(username); container->addChild(password); Button *button = new Button("Log In"); container->addChild(button); button->setAction([](){ this->login(); }) } void login() { string username = usernameBox->getText(); string password = passwordBox->getText(); sendLoginRequest(username, password); } }; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAvoiding dynamic_cast in GUI design
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USrob mayoff
UserOwnerUserId
1. USrob mayoff
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAvoiding dynamic_cast in GUI design
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.