Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think your problem is right here:</p> <pre><code>var WorkoutSectionSlide = Parse.View.extend( { tag : 'div', className : 'sectionPreview', attributes : {} // &lt;----------------- This doesn't do what you think it does </code></pre> <p>Everything that you put in the <code>.extend({...})</code> ends up in <code>WorkoutSectionSlide.prototype</code>, they aren't copied to the instances, they're shared by all instances through the prototype. The result in your case is that you have one <code>attributes</code> object that is shared by all <code>WorkoutSectionSlide</code>s.</p> <p>Furthermore, the view's <a href="http://documentcloud.github.com/backbone/#View-attributes" rel="nofollow"><code>attributes</code></a> are only used while the the object is <a href="https://github.com/documentcloud/backbone/blob/master/backbone.js#L1168" rel="nofollow">being constructed</a>:</p> <pre><code>var View = Backbone.View = function(options) { this.cid = _.uniqueId('view'); this._configure(options || {}); this._ensureElement(); this.initialize.apply(this, arguments); this.delegateEvents(); }; </code></pre> <p>The <a href="https://github.com/documentcloud/backbone/blob/master/backbone.js#L1291" rel="nofollow"><code>_ensureElement</code></a> call is the thing that uses <code>attributes</code> and you'll notice that it comes before <code>initialize</code> is called. That order combined with the prototype behavior is why your attribute shows up on the <em>next</em> instance of the view. The <code>attributes</code> is really meant for static properties, your <code>this.$el.attr('tooltip', ...)</code> solution is a good way to handle a dynamic attribute.</p>
    singulars
    1. This table or related slice is empty.
    1. POBackbone View Attribute set for next Instantiation?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmu is too short
    1. USmu is too short
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBackbone View Attribute set for next Instantiation?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThat makes sense. However, I've updated my `initialize` to exactly that and am not getting the desired result :(
      singulars
      1. PO
      1. USGarrett
    2. CO@Garrett: What's reading `attributes`? I don't see anything that accesses it in your code.
      singulars
      1. PO
      1. USmu is too short
    3. COI fixed it with `this.$el.attr('tooltip', ...)`, but would like to know if there is a better solution. Thanks for your insight, I appreciate your endless dedication to SO (and most of my questions). I am using `attributes` to set attributes on the `el` so my final result is `<div class="sectionPreview" tooltip="...">...</div>`.
      singulars
      1. PO
      1. USGarrett
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload