Changes between Version 3 and Version 4 of TemplatedForm

Timestamp:

Mar 21, 2007, 2:41:17 AM (17 years ago)

Author:

anonymous

Comment:

--

TemplatedForm

@@ -1 +1 @@
 == Subclassing newforms Form.form to rendering form via django template ==
 
-Sometimes standard methods of rendering HTML/XML/other content of the django.newforms is not enough to completely
-satisfy all web design needs. So sometimes it is better to customize your forms completely.
+Newforms are made to make any kind of customizations easy. Sometimes standard methods of rendering HTML/XML/other content of 
+the django.newforms is not enough to completely satisfy all web design needs so you may want to present forms in own
+templates.
 
-Using templates to render output as HTML or XML is straighforward and uses less code then as_table() counterpart
-implemented now in the core newforms, so I hope technique explained here will be helpful.
+Using templates to render output as HTML or XML is straighforward, and in many cases easier then using standard approach.
 
-The above example has been created specifically to mark required fields with red asterisk.
-In fact all you need to do to use this, is to add 3 small files to your project, and replace
-forms.Form to TemplatedForm class. Step by step explanations:
+== Step by step guide ==
 
 1. Create file in your project:
@@ -24 +22 @@
     def output_via_template(self):
         "Helper function for fieldsting fields data from form."
-        bound_fields = []
-        for name, field in self.fields.items():
-            bf = BoundField(self, field, name)
-            bound_fields.append(bf)
-        
+        bound_fields = [BoundField(self, field, name) for name, field \
+                        in self.fields.items()]
         c = Context(dict(form = self, bound_fields = bound_fields))
         t = loader.get_template('newforms/form.html')