#4901 closed defect (fixed)
API consistancy / optimizations in dijit
Reported by: | dante | Owned by: | dante |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Dijit | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
this.inherited() should be used over className.superclass.apply/call
where possible, we should be using this.connect() over dojo.connect all within dojo.declare()
in theory, shrinksafe will be nicer to use wrt to optimization, and this techmo will also let dijit's internal garbage collection / connection tracking stability.
Change History (14)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
comment:4 Changed 13 years ago by
comment:5 Changed 13 years ago by
comment:7 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
i think i got them all regarding this.
comment:8 Changed 13 years ago by
Milestone: | 2.0 → 1.0 |
---|
comment:9 Changed 13 years ago by
comment:10 Changed 13 years ago by
comment:12 Changed 13 years ago by
Note: See
TracTickets for help on using
tickets.
(In [11133]) refs #4901 - doc and superclass cleanups to stackcontainer.