[dijit.layout] Consider deprecating AccordionPane

[dante]

It seems odd we have this intermediary AccordionPane? (a templated ContentPane?) as a child of AccordionContainer? exclusively. Following in line with BorderContainer?, consider moving the templating logic into AccContainer?, and allow for any layout widget to be a child of the Container. This would allow you to more easily move children around from Tab->Accordion->Border->etc using the .addChild and .removeChild API. Currently, you need to create an AccPane?, add it to the AccContainer?, then setContent the domNode or the Child you want. It's probably possible to pull off with no "real" API change.

If all goes well, the proposed shim would be:

dojo.declare("dijit.layout.AccordionPane", dijit.layout.ContentPane, {
   constructor: function(){ dojo.deprecated(); }
});

[bill]

bumping 1.4 tickets to 1.5, and most 1.3 tickets to 1.4

[bill]

Refactored in [15912]

[bill]

Also [15913], [15914], [15915].

[bill]

And [15924].

[bill]

(In [15960]) Fix typo from [15912] causing closed then opened pane to have no scrollbar. Refs #4016, #6842 !strict

[bill]

(In [15978]) Test and fix addChild() for ContentPane? and AccordionContainer?. Refs #6842, #7819. !strict.

[bill]

(In [16070]) Use ContentPane? not deprecated AccordionPane?. Also, for the ContentPane? that embeds a TitlePane?, should use the default 5px padding so there's no double-border effect. Refs #6842.