Fixed the inevitable ReST errors in docs/form_wizard.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@7266 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
642f42bf71
commit
d0aa7c820b
|
@ -41,15 +41,15 @@ Usage
|
||||||
This application handles as much machinery for you as possible. Generally, you
|
This application handles as much machinery for you as possible. Generally, you
|
||||||
just have to do these things:
|
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.
|
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
|
forms have been submitted and validated. This also lets you override some
|
||||||
of the wizard's behavior.
|
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
|
generic template to handle every one of the forms, or you can define a
|
||||||
specific template for each form.
|
specific template for each form.
|
||||||
# Point your URLconf at your ``FormWizard`` class.
|
4. Point your URLconf at your ``FormWizard`` class.
|
||||||
|
|
||||||
Defining ``Form`` classes
|
Defining ``Form`` classes
|
||||||
=========================
|
=========================
|
||||||
|
@ -97,7 +97,7 @@ and validated. This method is passed two arguments:
|
||||||
* ``form_list`` -- a list of ``django.newforms`` ``Form`` classes
|
* ``form_list`` -- a list of ``django.newforms`` ``Form`` classes
|
||||||
|
|
||||||
In this simplistic example, rather than perform any database operation, the
|
In this simplistic example, rather than perform any database operation, the
|
||||||
method simply renders a template of the validated data::
|
method simply renders a template of the validated data::
|
||||||
|
|
||||||
from django.shortcuts import render_to_response
|
from django.shortcuts import render_to_response
|
||||||
from django.contrib.formtools.wizard import FormWizard
|
from django.contrib.formtools.wizard import FormWizard
|
||||||
|
@ -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
|
documented below. This hook also allows you to use a different template for
|
||||||
each form.)
|
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.
|
* ``step_field`` -- The name of the hidden field containing the step.
|
||||||
* ``step0`` -- The current step (zero-based).
|
* ``step0`` -- The current step (zero-based).
|
||||||
|
|
Loading…
Reference in New Issue