StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16640296
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-19T22:47:34.253
FavoriteCount
0
LastActivityDate
2013-05-19T22:55:58.270
LastEditDate
2013-05-19T22:55:58.270
LastEditorUserId
472179
OwnerUserId
472179
ParentId
16640195
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I think you followed some tutorial, since both beforeRender and afterRender don't exist in Backbone core. But, they are often implemented by people who need events fired before and after the rendering routine. Moreover, Backbone leaves the render function of the View class empty, so it's up to you to implement (and even call it) when you need. As a sidenote, it's generally not good to call render() right into the initialize() function, since often you'll need to have more control on when and how to render a view after having initialized it. That said, I would suggest: <ul> <li>Move all of the initialization logic (like your navigator checks) inside initialize();</li> <li>call render() out of the view (right after your new ViewName() call)</li> </ul> If you really need (maybe for further development of your code) before and after callbacks, you can make use of Underscore (available since it's a dependency) "wrap" function. Such approach consists of: <pre><code>initialize: function() this.render = _.wrap(this.render, function(render) { this.beforeRender(); render(); this.afterRender(); }); }, render: function() {}, beforeRender: function() {}, afterRender: function() {} </code></pre> With this in mind, I would go with (remember to specify an onFailUpdatePos on the View class): <pre><code>initialize: function() { if (navigator.geolocation) { navigator.geolocation.getCurrentPosition(this.render, this.onFailUpdatePos); } else { navigator.geolocation.getCurrentPosition(this.render, this.onFailUpdatePos); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBackbone.js render a view after a getting return value
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsixFingers
UserOwnerUserId
1. USsixFingers
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBackbone.js render a view after a getting return value
 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
 VTUpMod
3. 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.