Re: FormEncode wishlist

On Thu, Apr 09, 2009 at 12:04:39PM -0700, Mike Orr wrote:
> At PyCon Ian mentioned he's looking for a maintainer for FormEncode.
> I don't have time to do this right now but I may in a few months.  In
> the meantime I'd like to start a discussion on what direction
> FormEncode should go.

* Fix the bugs reported in the sourceforge bug tracker.

* Improve the documentation.  Some of the things with FormEncode are
  confusing:

    e.g. Bool() versus StringBool() --- one is for submit buttons, the
    other is for checkboxes/etc.  Maybe.  I'm not sure :)

    e.g. String() versus UnicodeString() [sp?] --- you might end up
    doing str <-> unicode conversion twice if both your web framework
    (Pylons) and FormEncode try to do that.

* Move to a saner bug tracker.  (Sourceforge makes me go yuck,
  especially when it forgets to HTML-escape my bug titles correctly in
  some of its "recent changes" boxes, or when it randomly inserts
  backslashes in those titles---trying to blindly avoid SQL injection
  attacks?)

Marius Gedminas
-- 
Attempts to stick to simple on-or-off options lead to monsters like gcc, which
now has so many flags that programmers are using genetic algorithms to explore
them.
        -- http://www.third-bit.com/~gvwilson/xmlprog.html

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com

_______________________________________________
FormEncode-discuss mailing list
FormEncode-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/formencode-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJ3mt0kVdEXeem148RAuYdAKCE0fkcx4ZiSsoa+6Zhgs5f4ZDRAACePVMV
ykItiSOl/StyOK+TcOhtBOg=
=0rXq
-----END PGP SIGNATURE-----