Closed pruzand closed 9 years ago
StackContainer / ViewStack http://dojotoolkit.org/reference-guide/1.9/dijit/layout/StackContainer.html
TabContainer (use internal TabController, ScrollingTabController and TabButton) http://dojotoolkit.org/reference-guide/1.9/dijit/layout/TabContainer.html
LayoutContainer https://dojotoolkit.org/reference-guide/1.9/dijit/layout/LayoutContainer.html
BorderContainer (LayoutContainer + splitters) https://dojotoolkit.org/reference-guide/1.9/dijit/layout/BorderContainer.html
ContentPane http://livedocs.dojotoolkit.org/dijit/layout/ContentPane
AccordionContainer https://dojotoolkit.org/reference-guide/1.9/dijit/layout/AccordionContainer.html
I want to emphasize two main gaps from StackContainer and TabContainer:
StackContainer can take the size of its children (doLayout = false). ViewStack must be sized then children take 100%.
I was assuming that the app didn't need to specify a size on the ViewStack, and that ViewStack's children could all be different sizes. I guess not?
Another thing is that (by design) ViewStack does not handle user interaction, i.e. swiping to move between panes. So we'll need to implement that eventually. Contrast with SwapView + PageIndicator from dojox/mobile (or Carousel embeds both).
About ContentPane: ViewStack (well actually, DisplayContainer) emits events when displaying a child, allowing a framework to load that child. But there's no built-in code to do an XHR and get the data, plus display a "Loading..." type message while the XHR is in progress.
Maybe that code should be somewhere, either a ContentPane widget or part of the parent widget. I'm not sure. In any case, this a gap compared to dijit/dojox.mobile where you could just say <div dojoType=dijit/layout/ContentPane href=...>
.
About Accordion: presumably we need one. A few issues to consider when implementing are:
From off line discussions:
About the accordion container: it might (should ?) be possible to implement it using the List widget (categorized list, with a category renderer that displays / hide its content when clicked / actioned).
I think investigation side is done here.
We need to be sure we don't drop features that were available in 1.x when switching to deliteful. Or at least, that the features that are dropped, if any, were the results of a decision or expected. @dmandrioli could you make a comparaison of the new deliteful containers capabilities vs their dijit counterparts ? (ex: LinearLayout vs BorderContainer, ViewStack vs StackContainer?)