Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Andy Edinborough is correct about var <code>self != this</code>.</p> <p>It looks like you want to store a reference to the jQuery wrapper around your object instances, so I used the <a href="http://en.wikipedia.org/wiki/Flyweight_pattern" rel="nofollow">flyweight pattern</a> <em>(avoids creating a property on the object instance to store the jQuery wrapper)</em>. You can read more about this at James Padolsey's <a href="http://james.padolsey.com/javascript/76-bytes-for-faster-jquery/" rel="nofollow">blog</a>.</p> <p>I also cleaned up your code:</p> <pre><code>(function(window) { var flyweight = $([1]); /*--------------------------------------------------------------------------*/ function GrandParent() { /* empty constructor */ } function Parent() { /* empty constructor */ } function Child() { flyweight[0] = this; flyweight.bind('SomethingHappened', function(){ console.log('Client logs: SomethingHappened'); }) .bind('Happened', function(){ console.log('Client logs: Happened'); }); } /*--------------------------------------------------------------------------*/ // setup inheritance Parent.prototype = Object.create(GrandParent.prototype, { 'constructor': { 'configurable': true, 'writable': true, 'value': Parent } }); Child.prototype = Object.create(Parent.prototype, { 'constructor': { 'configurable': true, 'writable': true, 'value': Child } }); // add methods GrandParent.prototype.doFoo = function(){ flyweight[0] = this; flyweight.trigger('Happened'); }; Parent.prototype.doSomething = function(){ flyweight[0] = this; flyweight.trigger('SomethingHappened'); }; /*--------------------------------------------------------------------------*/ // expose window.MyApp = { 'GrandParent': GrandParent, 'Parent': Parent, 'Child': Child }; }(this)); </code></pre> <p>Usage check:</p> <pre><code>var foo = new MyApp.Child; var bar = new MyApp.Child; $(bar).bind('SomethingElse', function() { console.log('Client logs: SomethingElse'); }); foo.doFoo(); // Client logs: Happened foo.doSomething(); // Client logs: SomethingHappened $(bar).trigger('SomethingElse'); // Client logs: SomethingElse $(foo).trigger('SomethingElse'); // Nothing happens \o/ </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POjquery bind/trigger in a prototypal inheritance scenario. Can't trigger events on the right object
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJohn-David Dalton
    1. USJohn-David Dalton
    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. 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. VTUpMod
    1. COHi John, thanks a lot for taking time to answer. However, Im still not satisfied ;-) Did you look at http://www.slideshare.net/fgalassi/javascript-the-new-parts slide 16ff? I would rather avoid to clutter my objects in the way to write a constructor function first and then implement the methods afterwards. And the second thing. I don't want to share a flyweight var between the objects that was created outside of the objects scope. I'd rather have it like that http://jsfiddle.net/cburgdorf/FhjnX/ It serves everything but the prototype chain. But I'd rather give that up I think...
      singulars
      1. PO
      1. USChristoph
    2. COI'm actually unsure for what I would need the prototype chain anyways? There want be masses of those objects. The only difference I could find is that all the methods will be implemented on the Child instance. Beside that, everything is fine. You can even extend base methods if you have a need for it. So I wonder what do I care for the prototype chain anyway?
      singulars
      1. PO
      1. USChristoph
    3. COI don't consider the use of constructors as *"ugly"*. I showed a clean way to use constructors with the help of `Object.create()`. Constructors are used to avoid sharing the event data with all other child objects. Using the prototype reduces the need for manual assignment of methods like `doFoo` and `doSomething` from your original example.
      singulars
      1. PO
      1. USJohn-David Dalton
 

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