[FE-CVS]r1303 - in FormEncode/trunk: docs formencode

[<sub...@co...>]

Author: ianb
Date: 2005-11-20 19:30:17 +0000 (Sun, 20 Nov 2005)
New Revision: 1303

Modified:
   FormEncode/trunk/docs/ToDo.txt
   FormEncode/trunk/docs/news.txt
   FormEncode/trunk/formencode/htmlform.py
Log:
Fixed to-do list; added deprecating warning to htmlform

Modified: FormEncode/trunk/docs/ToDo.txt
===================================================================
--- FormEncode/trunk/docs/ToDo.txt	2005-11-20 10:37:30 UTC (rev 1302)
+++ FormEncode/trunk/docs/ToDo.txt	2005-11-20 19:30:17 UTC (rev 1303)
@@ -5,20 +5,17 @@
 :revision: $Rev$
 :date: $LastChangedDate$
 
-* Generate documentation for the standard validators.
-
 * Make a test fixture for validators, to make testing really easy.
 
 * Consider moving htmlfill to ElementTree or another DOM-ish
-  structure, instead of HTMLParser.
+  structure, instead of HTMLParser.  Or re-implement with another
+  parser but same interface.
 
 * Generate Javascript for validators, for client-side validation (when
   possible).
 
-* At least test and give recipes for Ajax-ish validation, when fully
-  client-side validation doesn't work.  (Client side is more
-  interesting to me, though -- Ajax still does a server query, and
-  isn't much better than a full submit)
+* Relatedly, test and give recipes for Ajax-ish validation, when fully
+  client-side validation doesn't work.
 
 * Better tests for ``htmlfill`` and ``htmlfill_schemabuilder``.
 
@@ -36,9 +33,11 @@
 * Make ``doctest_xml_compare`` work with wildcards/ellipses.  Maybe
   with non-XHTML.
 
-* Figure out how the heck to get this to scale to really small forms.
-  Does it make any sense there?  When does it start making sense to
-  use FormEncode?
+* Maybe include `wareweb.packing
+  <http://pythonpaste.org/wareweb/module-wareweb.packing.html>`_,
+  which is kind like like one-way validation for really small forms.
+  A compliment/alternative to `variabledecode
+  <module-formencode.variabledecode.html>`_.
 
 * Some more ways to build validation.  Validation from docstrings or
   method signatures.

Modified: FormEncode/trunk/docs/news.txt
===================================================================
--- FormEncode/trunk/docs/news.txt	2005-11-20 10:37:30 UTC (rev 1302)
+++ FormEncode/trunk/docs/news.txt	2005-11-20 19:30:17 UTC (rev 1303)
@@ -4,6 +4,8 @@
 SVN trunk
 ---------
 
+* Deprecated ``formencode.htmlform`` module, because it is dumb.
+
 * Added an ``.all_messages()`` method to all validators, primarily
   intended to be used for documentation purposes.
 

Modified: FormEncode/trunk/formencode/htmlform.py
===================================================================
--- FormEncode/trunk/formencode/htmlform.py	2005-11-20 10:37:30 UTC (rev 1302)
+++ FormEncode/trunk/formencode/htmlform.py	2005-11-20 19:30:17 UTC (rev 1303)
@@ -1,4 +1,8 @@
 """
+.. note::
+
+   This is deprecated, as it's not that helpful.
+
 Class to encapsulate an HTML form, using htmlfill and
 htmlfill_schemabuilder
 
@@ -26,11 +30,16 @@
 import htmlfill
 import htmlfill_schemabuilder
 from api import Invalid
+import warnings
 
 class HTMLForm(object):
 
     def __init__(self, form, schema=None,
                  auto_insert_errors=True):
+        warnings.warn(
+            'HTMLForm has been deprecated; use the htmlfill and '
+            'htmlfill_schemabuilder modules directly.',
+            DeprecationWarning)
         self.form = form
         self._schema = schema
         self.auto_insert_errors = auto_insert_errors