Dojo has gone through much work to build a nice set of widgets to help with the layout of your web applications. They currently have many different layout managers. From the highly usable dijit.layout.BorderContainer, to the functional, (or at least it doesn’t crash) dijit.layout.AccordianContainer.
But with all these layout managers, you can also use a multitude of pane objects. SplitPane, SliderPane and so on. But it’s the ContentPane, that really holds the guts of your application together.
Dojo now has 3 different content panes. The dojo.layout.ContentPane, the dijit.layout.ContentPane, and the (you guessed it)… the dojox.layout.ContentPane.
All three can be declaratively or programmatically created.
<!—Put your info here
content:"<p>Honestly, it sucks</p>"
Where, once again, Dojo fails to excel is in their documentation. While working on an application with many nested containers and layouts, I encountered several headaches, which forced me to head to Google to solve.
This was removed in 0.9, to make the widget more streamlined (Huh???). Since the dijit ContentPane was next logically choice, they must have added to the ability to run script code there. Well not exactly To run script code, you need to should actually use dojox.layout.ContentPane. Even though its in the dojox package it has been well tested and used.
Another helpful tip, when nesting multiple panes and containers together, the dojo.addOnLoad() method is ONLY executed on the first load. Even if you href another page in, that addOnLoad will not be executed. This means you can declaratively build your initial page, but subsequent pages that are “sucked in” your existing content panes, need to be built programmatically.