Comments on: A hidden gem of Dojo.declare – overcoming the limits of multiple inheritance http://dojocampus.org/content/2008/11/16/a-hidden-gem-of-dojodeclare-overcoming-the-limits-of-multiple-inheritance/ The definitive resource for all things Dojo: past, present, future. Wed, 10 Mar 2010 18:40:27 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: bill http://dojocampus.org/content/2008/11/16/a-hidden-gem-of-dojodeclare-overcoming-the-limits-of-multiple-inheritance/comment-page-1/#comment-284 bill Thu, 25 Dec 2008 10:12:04 +0000 http://dojocampus.org/content/?p=182#comment-284 I don't think the prototype.doSomething.apply() trick has anything to do with dojo.declare(). It works even when dojo.declare() isn't used. But there is something useful that dojo.declare() gives us: If we add this.inherited(arguments) calls to every doSomething() implementation, then calling "myPackage.A".doSomething() will call *every* doSomething()... strangely, even though myPackage.B and myPackage.C are peers from our perspective, dojo.declare() sets things up so that myPackage.B's call to this.inherited(arguments) will call myPackage.C. I don’t think the prototype.doSomething.apply() trick has anything to do with dojo.declare(). It works even when dojo.declare() isn’t used. But there is something useful that dojo.declare() gives us:

If we add this.inherited(arguments) calls to every doSomething() implementation, then calling “myPackage.A”.doSomething() will call *every* doSomething()… strangely, even though myPackage.B and myPackage.C are peers from our perspective, dojo.declare() sets things up so that myPackage.B’s call to this.inherited(arguments) will call myPackage.C.

]]>