Browse files

Small tweak to docs/newforms.txt

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent b6a7afd commit 9a02d668c1066a313f973ca80b204fce9eb1a252 @adrianholovaty adrianholovaty committed Dec 7, 2006
Showing with 7 additions and 6 deletions.
  1. +7 −6 docs/newforms.txt
@@ -3,10 +3,8 @@ The newforms library
``django.newforms`` is a new replacement for ``django.forms``, the old Django
-form/manipulator/validation framework. This functionality is new in the Django
-development version -- i.e., it's not available in the Django 0.95 release.
-This document explains how to use this new form library.
+form/manipulator/validation framework. This document explains how to use this
+new form library.
Migration plan
@@ -25,7 +23,7 @@ release, our plan is to do the following:
* Move the current ``django.newforms`` to ``django.forms``.
* We will remove ``django.oldforms`` in the release *after* the next Django
- release -- i.e., the release that comes after the release in which we're
+ release -- the release that comes after the release in which we're
creating ``django.oldforms``.
With this in mind, we recommend you use the following import statement when
@@ -55,9 +53,12 @@ want to perform server-side validation for an HTML form.
The library deals with these concepts:
* **Widget** -- A class that corresponds to an HTML form widget, e.g.
- ``<input type="text">`` or ``<textarea>``.
+ ``<input type="text">`` or ``<textarea>``. This handles rendering of the
+ widget as HTML.
* **Field** -- A class that is responsible for doing validation, e.g.
an ``EmailField`` that makes sure its data is a valid e-mail address.
* **Form** -- A collection of fields that knows how to validate itself and
display itself as HTML.

0 comments on commit 9a02d66

Please sign in to comment.