StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14405923
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-18T19:11:09.693
FavoriteCount
0
LastActivityDate
2013-01-19T04:17:21.437
LastEditDate
2013-01-19T04:17:21.437
LastEditorUserId
215945
OwnerUserId
215945
ParentId
14087216
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Here is a <a href="http://jsfiddle.net/mrajcok/tsSJA/" rel="nofollow">fiddle</a> with two versions of the directive. One does not create a new scope. The other creates an isolate scope. What I found out is that ng-click can't contain {{}}s, so we need to use a compile function to get the URL string into the template, via the attributes argument (tAttrs). No new scope. HTML: <pre><code><uploader url="http://someplace.com/pic.jpg" upload-fn="upload"></uploader> </code></pre> Directive: <pre><code>myApp.directive('uploader', function () { return { restrict: 'E', templateUrl: "/assets/uploader.html", compile: function (tElement, tAttrs) { var buttonElement = tElement.find('button') buttonElement.attr('ng-click', tAttrs.uploadFn + "('" + tAttrs.url + "')") console.log(tElement.html()) } } }); </code></pre> Above, the directive uses the same scope as the controller, so the ng-click attribute's value is set to call the function defined by the upload-fn attribute in the HTML. The upload-fn attribute is not necessary, but it does make the directive more reusable, since the directive is told what scope method to call -- "upload" -- and hence can be easily altered in the HTML. If reusablility is not a concern, here's the simpler alternative: HTML: <pre><code><uploader url="http://someplace.com/pic.jpg"></uploader> </code></pre> Directive change: <pre><code>buttonElement.attr('ng-click', "upload('" + tAttrs.url + "')") </code></pre> Isolate scope. HTML: <pre><code><uploader-isolate url="http://someplace.com/pic.jpg" upload-fn="upload(url)"> </uploader-isolate> </code></pre> Directive: <pre><code>myApp.directive('uploaderIsolate', function () { return { restrict: 'E', scope: { uploadFn: '&' }, templateUrl: "/assets/uploader.html", compile: function (tElement, tAttrs) { var buttonElement = tElement.find('button') buttonElement.attr('ng-click', "uploadFn({url:'" + tAttrs.url + "'})") console.log(tElement.html()) } } }); </code></pre> Above, the directive creates a new scope -- an isolate scope. This scope does not prototypically inherit from the parent/controller scope, so it (and the directive's template) do not have access to the upload() function defined on the controller's $scope. The '&' notation is used to create a "delegate" uploadFn function. What that means is that when "uploadFn" is used in the isolate scope (i.e., in the directive's template), it will actually call the "upload" function on the parent scope. In addition, we specify that the upload function takes one argument, url. When the delegate function is used in the directive's template, we can't just pass an argument. I.e., this won't work: uploadFn('http://...'). Instead, we need to use a map/object to specify any argument values. E.g., uploadFn({url: 'http://...'}). The isolate scope object hash does not contain <code>url: '@'</code> because I don't think attribute ng-click's value can contain <code>{{}}</code>s. This is why we use a compile function and obtain the url attribute's value via the compile function's attribute argument. If the url value was only used elsewhere in the template, such as <code>url = {{url}}</code>, then the '@' notation would be used. The template was altered to remove the value for the ng-click attribute. The value is assigned to the attribute in the compile function. <pre><code><button class="button small" ng-click>Upload File</button> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAngularJS plupload directive binding issue
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMark Rajcok
UserOwnerUserId
1. USMark Rajcok
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAngularJS plupload directive binding issue
 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
 VTAcceptedByOriginator
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.