Loading docs/form_wizard.txt +11 −11 Original line number Diff line number Diff line Loading @@ -41,15 +41,15 @@ Usage This application handles as much machinery for you as possible. Generally, you just have to do these things: # Define a number of ``django.newforms`` ``Form`` classes -- one per wizard 1. Define a number of ``django.newforms`` ``Form`` classes -- one per wizard page. # Create a ``FormWizard`` class that specifies what to do once all of your 2. Create a ``FormWizard`` class that specifies what to do once all of your forms have been submitted and validated. This also lets you override some of the wizard's behavior. # Create some templates that render the forms. You can define a single, 3. Create some templates that render the forms. You can define a single, generic template to handle every one of the forms, or you can define a specific template for each form. # Point your URLconf at your ``FormWizard`` class. 4. Point your URLconf at your ``FormWizard`` class. Defining ``Form`` classes ========================= Loading Loading @@ -134,7 +134,7 @@ change this template name by overriding ``FormWizard.get_template()``, which is documented below. This hook also allows you to use a different template for each form.) This template expects the following context:: This template expects the following context: * ``step_field`` -- The name of the hidden field containing the step. * ``step0`` -- The current step (zero-based). Loading Loading
docs/form_wizard.txt +11 −11 Original line number Diff line number Diff line Loading @@ -41,15 +41,15 @@ Usage This application handles as much machinery for you as possible. Generally, you just have to do these things: # Define a number of ``django.newforms`` ``Form`` classes -- one per wizard 1. Define a number of ``django.newforms`` ``Form`` classes -- one per wizard page. # Create a ``FormWizard`` class that specifies what to do once all of your 2. Create a ``FormWizard`` class that specifies what to do once all of your forms have been submitted and validated. This also lets you override some of the wizard's behavior. # Create some templates that render the forms. You can define a single, 3. Create some templates that render the forms. You can define a single, generic template to handle every one of the forms, or you can define a specific template for each form. # Point your URLconf at your ``FormWizard`` class. 4. Point your URLconf at your ``FormWizard`` class. Defining ``Form`` classes ========================= Loading Loading @@ -134,7 +134,7 @@ change this template name by overriding ``FormWizard.get_template()``, which is documented below. This hook also allows you to use a different template for each form.) This template expects the following context:: This template expects the following context: * ``step_field`` -- The name of the hidden field containing the step. * ``step0`` -- The current step (zero-based). Loading