SVN: r25691 - trunk/quixote/doc

Author: dbinger
Date: 2004-11-30 15:25:28 -0500 (Tue, 30 Nov 2004)
New Revision: 25691

Modified:
   trunk/quixote/doc/form2conversion.txt
Log:
Update form2conversion.txt to reflect the change in form package names.


Modified: trunk/quixote/doc/form2conversion.txt
===================================================================
--- trunk/quixote/doc/form2conversion.txt	2004-11-30 20:17:30 UTC (rev 25690)
+++ trunk/quixote/doc/form2conversion.txt	2004-11-30 20:25:28 UTC (rev 25691)
@@ -1,11 +1,18 @@
 Converting form1 forms to use the form2 library
 ===============================================
+********
+Note:  The packages names have changed in Quixote 2.
+Quixote form1 forms are now in the package quixote.form1.
+(In Quixote 1, they were in quixote.form.)
 
+Quixote form2 forms are now in the package quixote.form.
+(In Quixote 1, they were in quixote.form2.)
+********
 Introduction
 ------------
 
 These are some notes and examples for converting Quixote form1 forms,
-that is forms derived from ``quixote.form.Form``, to the newer form2
+that is forms derived from ``quixote.form1.Form``, to the newer form2
 forms.
 
 Form2 forms are more flexible than their form1 counterparts in that they
@@ -33,8 +40,8 @@
 Here's the short list of things to do to convert form1 forms to 
 form2 using compatibility.
 
-  1. Import the Form base class from ``quixote.form2.compatibility``
-     rather than from quixote.form.
+  1. Import the Form base class from ``quixote.form.compatibility``
+     rather than from quixote.form1.
 
   2. Getting and setting errors is slightly different.  In your form's 
      process method, where errors are typically set, form2
@@ -86,14 +93,14 @@
 
   4. You almost certainly want to include some kind of cascading style
      sheet (since form2 forms render with minimal markup).  There is a
-     basic set of CSS rules in ``quixote.form2.css``.
+     basic set of CSS rules in ``quixote.form.css``.
 
 
 Here's the longer list of things you may need to tweak in order for
 form2 compatibility forms to work with your form1 code.
  
   *  ``widget_type`` widget class attribute is gone.  This means when
-     adding widgets other than widgets defined in ``quixote.form2.widget``,
+     adding widgets other than widgets defined in ``quixote.form.widget``,
      you must import the widget class into your module and pass the 
      widget class as the first argument to the ``add_widget`` method
      rather than using the ``widget_type`` string.
@@ -231,7 +238,7 @@
 instance it keeps a reference to it as a local variable::
 
         def obj_form(request, obj):
-            form = Form() # quixote.form2.Form
+            form = Form() # quixote.form.Form
             if obj is None:
                 obj = Obj()
                 form.add_submit('add', 'Add')