summaryrefslogtreecommitdiff
path: root/demos/quickstart/protected/pages/Controls/Wizard.page
diff options
context:
space:
mode:
authorxue <>2006-03-25 04:44:38 +0000
committerxue <>2006-03-25 04:44:38 +0000
commitd8d697fe108e488e4b210d96ec08aa69942a3902 (patch)
tree92976ef03e1dd0b2b28ccddee76d39618d720df0 /demos/quickstart/protected/pages/Controls/Wizard.page
parent8df1407a11df3e5a8c33c6fae1c522707aefccf3 (diff)
Added TemplatedWizardStep example.
Diffstat (limited to 'demos/quickstart/protected/pages/Controls/Wizard.page')
-rw-r--r--demos/quickstart/protected/pages/Controls/Wizard.page17
1 files changed, 14 insertions, 3 deletions
diff --git a/demos/quickstart/protected/pages/Controls/Wizard.page b/demos/quickstart/protected/pages/Controls/Wizard.page
index 0de4a44a..29718930 100644
--- a/demos/quickstart/protected/pages/Controls/Wizard.page
+++ b/demos/quickstart/protected/pages/Controls/Wizard.page
@@ -67,22 +67,33 @@ In this sample, we use wizard to collect user's preference of color. In the firs
<h3>Customizing Wizard Navigation</h3>
<p>
-Bidirectional,
-Unidirectional,
-Non-linear
+Given a set of wizard steps, <tt>TWizard</tt> supports three different ways of navigation among them:
</p>
+<ul>
+ <li>Bidirectional - Users can navigate forward and backward along a sequence of wizard steps. User input data is usally collected at the last step. This is also known as commit-at-the-end model. It is the default navigation way that <tt>TWizard</tt> supports.</li>
+ <li>Unidirectional - Users can navigate forward along a sequence of wizard steps. Backward move is not allowed. User input data is usally collected step by step. This is also known as command-as-you-go model. To disallow backward move to a specific step, set its <tt>AllowReturn</tt> property to false.</li>
+ <li>Nonlinear - User input in a step determines which step to go next. To do so, set <tt>ActiveStepIndex</tt> to the step that you want the user to go to. In this case, when a user clicks on the previous button in the navigation panel, the previous step that they visited (not the previous step in the sequential order) will become visible.</li>
+</ul>
+<com:RunBar PagePath="Controls.Samples.TWizard.Sample3" />
<h3>Using Templates in Wizard</h3>
<p>
+<tt>TWizard</tt> supports more concrete control of its outlook through templating. In particular, it provides the following template properties that allow complete customization of the wizard's header, navigation and side bar.
</p>
<ul>
<li>Header - <tt>HeaderTemplate</tt>.</li>
<li>Navigation - <tt>StartNavigationTemplate</tt>, <tt>StepNavigationTemplate</tt>, <tt>FinishNavigationTemplate</tt>.</li>
<li>Side bar - <tt>SideBarTemplate</tt>.</li>
</ul>
+Note about side bar button IDs, navigation button commands
+headertext vs. headertemplate
+tablelayout vs pure div layout
+<com:RunBar PagePath="Controls.Samples.TWizard.Sample4" />
<h3>Using Templated Wizard Steps</h3>
<p>
+Wizard steps can also be templated. By using <tt>TTemplatedWizardStep</tt>, one can customize step content and navigation through its <tt>ContentTemplate</tt> and <tt>NavigationTemplate</tt> properties, respectively. This is useful for control developers to build specialized wizards, such as user registration, shopping carts, etc.
</p>
+<com:RunBar PagePath="Controls.Samples.TWizard.Sample5" />
</com:TContent> \ No newline at end of file