StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17242017
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-06-21T18:28:43.107
FavoriteCount
0
LastActivityDate
2013-06-21T18:36:15.033
LastEditDate
2013-06-21T18:36:15.033
LastEditorUserId
1681451
OwnerUserId
1681451
ParentId
16166017
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
<h1>Ext.getCmp() VS Ext.get()</h1> <code>Ext.getCmp()</code> finds an existing (created) component in ExtJS component tree. Note that it is discouraged to use it. Rely on <a href="http://docs.sencha.com/extjs/4.2.1/#!/api/Ext.ComponentQuery" rel="noreferrer">ComponentQuery</a> instead. <code>Ext.get()</code> finds a DOM element by id. For example: <pre><code><html> <body> <div id="target">Hello, world!</div> </body> </html> </code></pre> <code>Ext.get('target')</code> will return <code>div#target</code> DOM element. I personally never use either one. Instead, I locate components using ComponentQuery and then retrieve their DOM elements, as described below. <h1>MyCmp.getEl() VS MyCmp.el</h1> Both just retrieve the top level DOM element of the MyCmp component. Current version of ExtJS (4.2.1) defines the <code>.getEl()</code> function as follows: <pre><code>MyCmp.getEl = function () { return this.el; } </code></pre> Which means that <code>MyCmp.getEl()</code> and <code>MyCmp.el</code> are absolutely equal. Use <code>.el</code> if you prefer to keep your code short and sweet. However, <code>.getEl()</code> might be useful in case if in the future ExtJS adds additional logic to the component's DOM element retrieval process (e.g. checking whether it exists or not first). I prefer <code>.el</code>. <h1>MyCmp.hide() VS MyCmp.el.hide()</h1> <code>MyCmp.hide()</code> and <code>MyCmp.el.hide()</code> are two different functions. Current version of ExtJS (4.2.1) defines them as follows: <pre><code>MyCmp.hide = function (animateTarget, cb, scope) { var me = this, continueHide; if (me.pendingShow) { delete me.pendingShow; } if (!(me.rendered && !me.isVisible())) { continueHide = (me.fireEvent('beforehide', me) !== false); if (me.hierarchicallyHidden || continueHide) { me.hidden = true; me.getHierarchyState().hidden = true; if (me.rendered) { me.onHide.apply(me, arguments); } } } return me; } </code></pre> and <pre><code>MyCmp.el.hide = function (animate){ if (typeof animate == 'string'){ this.setVisible(false, animate); return this; } this.setVisible(false, this.anim(animate)); return this; } </code></pre> However, both functions seem to produce identical results. They just add a <code>style="display: none;"</code> to the component's DOM element. I use <code>MyCmp.hide()</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCan you please explain .el, getEl(), Ext.get() in detail?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGeo
UserOwnerUserId
1. USGeo
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. 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.