![]() |
The initial page of the application. The purpose of the index.html file is to provide the initial layout definition and load the starting views. In this particular example, the index.html file uses the layout container widget to contain a split containerwidget . The split container widget divides the browser view into two controllable sections: the navigation view and the data view. |
![]() |
A directory that contains the HTML
template files that are loaded into the content pane widgets of the
views. |
![]() |
The buttons.html file displays the
basic navigation pane on the left side of the view. This page uses the basic Dojo Toolkit button widget and uses the dojox.wire project to construct a markup-based custom controller that posts events to the Dojo topic system when a button is selected. |
![]() |
The right data view that has a tab
container widget controlled set of views. Actions on the navigation view effect which tab is opened in the data view to demonstrate how controllers can change views and handle application events. This file also defines the controllers that control the top-level Dojo Toolkit tab container widget that is built from the dojox.wire controls and all the sub-view content pane widgets that are contained within the tab container. |
![]() |
The template view to load into the
tab one content pane widget and manipulate through a controller. Basic HTML, no Dojo Toolkit widgets. |
![]() |
The template view to load into the
tab two content pane and manipulate through a controller. Basic HTML, no Dojo Toolkit widgets. |
![]() |
The template view to load into the
tab three content pane widget and manipulate through a controller. Basic HTML, no Dojo Toolkit widgets. |
![]() |
A directory that contains the controller widgets. |
![]() |
The Dojo Toolkit view controller
for manipulating a content pane widget that is contained in a tab. The purpose of this controller is to provide an example child view controller that is part of an overall container view, such as the tab container widget. This controller only completes one action: On calls to its setMessage() function, the controller updates the content of the content pane with a new message. Therefore, this controller is an interface point for working with widgets and data contained by that specific content pane. |