API consistancy / optimizations in dijit

[dante]

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.

[dante]

(In [11133]) refs #4901 - doc and superclass cleanups to stackcontainer.

[dante]

(In [11134]) refs #4901 - moves lots of tab templateString to new file as well as cleanups on superclass calls.

[dante]

(In [11135]) refs #4901 -

it's no longer EXAMPLES: it's "example:" says pottedmeat ... (sorry for the confusion alex) another mild cleanup.

[dante]

(In [11136]) refs #4901 - other cleanups and doc cleanups etc. still going.

[dante]

(In [11137]) refs #4901 - really, doing it one at a time so an individual checking can be reverted in the event i miss something in testing each portion.

[dante]

(In [11139]) refs #4901 - cleanups.

[dante]

i think i got them all regarding this.

[dante]

(In [11498]) refs #4820 and refs #4901 - doc additions and one small superlclass.apply change

[dante]

(In [11660]) refs #4611 - remove usage:, use example: (though not being picked up atm) and refs #4901 - one this.inherited() change

[dante]

(In [11743]) doc cleanups to dijit.form.Button - refs #4901 ?

[dante]

(In [12341]) refs #4901 - this.inherited() stuff, and small style changes.

[dante]

(In [12342]) refs #4901 - cleanups.

[dante]

(In [12344]) refs #4901 - cleanups