Databases
StackOverflow2013
Postsdbo
POPrivate event handlers in Backbone Views
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPrivate event handlers in Backbone Views
    primarykey
    data
    text
    <p>I'm trying to figure out a way to keep my private functions and helper methods truly private. Each object should only publicize what is allowed to be called externally (radical, I know!). I'm having a hard time doing this with Backbone views in a way that:</p> <ol> <li>Doesn't sacrifice readability</li> <li>Doesn't involve a lot of boilerplate</li> <li>Doesn't have any unintended consequences</li> </ol> <p>Here's my general View structure:</p> <pre><code>(function(){ //Private function no other view needs to care about var addStuffToMyDom = function(model){ var newView = new Subview({model: model}); //Problem: this doesn't refer to the 'view' here this.$el.append(newView.render().$el); } //Another trivial function which should really be private var doSomeThingTrivial = function(){ this.$el.addClass("meh"); } return BaseView.extend({ events: { "click": doSomeThingTrivial }, render: function(){ var me = this; this.collection.each(addStuffToMyDom); return this; } }); }()); </code></pre> <p>As you can see the private functions can't reference 'this' to append themselves to.</p> <p>Solution 1:</p> <pre><code>(function(){ var me; ... return BaseView.extend({ initialize: function(){ me = this; } }); }()); </code></pre> <p>This has a lot of subtle side-effects + would be annoying to have to do this every time. </p> <p>Solution 2:</p> <pre><code>(function(){ var me; ... return BaseView.extend({ events{ "click" : function(){ doSomeThingTrivial.call(this); } } }); }()); </code></pre> <p>This works, but it's a lot of boilerplate for messy code.</p> <p>Solution 3:</p> <pre><code>(function(){ return BaseView.extend({ events: {..} initialize: function(){ _.bindAll(this, this.events); } }); }()); </code></pre> <p>I like this the best; this works, is fairly readable and works as advertised, but again, is one extra step to do for each view. Any other solutions I'm missing?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNaren
    1. USNaren
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPrivate event handlers in Backbone Views
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPrivate event handlers in Backbone Views
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy not just pass the function body of `doSomethingTrivial` directly to the event? That way it exists only as the anonymous event handler and not as an object method on your class/view/whatever.
      singulars
      1. POPrivate event handlers in Backbone Views
      1. USMathletics
    2. CO@Mathletics possible, but if it grew 'not so trivial' in the future it'll leave behind a huge events hash.
      singulars
      1. POPrivate event handlers in Backbone Views
      1. USNaren
    3. COI don't see a real use case where you would want to force something that is not event supported in current JavaScript implementation. From my experience on small and large projects, it is better to keep a good communication between team members and document which methods are there for everyone and which ones not. Also, if you intend to reuse your "classes", by arranging the code inside closures will really make your life harder. I really recommend you to try out this combo: RequireJS + Backbone + Backbone-Super.
      singulars
      1. POPrivate event handlers in Backbone Views
      1. USErick Ruiz de Chavez
 

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