Hello Alberto and others,

My feedback on trying out twForms following "part 1" tutorial.

0. It all worked!

1. middleware configuration step could be optional, since I believe you could do the same with some magic tweaking of .ini file.

2. API docs kind of useless. I have tried pydoc hint, mentioned in the article. "pydoc toscawidgets.api" gives nothing useful, just like "pydoc toscawidgets.widgets" and others.

I knew for sure that besides ListForm forms there should be other variant but how I am supposed to find it out? "pydoc toscawidgets.widgets.forms" doesn't mention either ListForm or anything else in particular but gives a useless list of confusing names. Alice down the rabbit hole. ;)

3. FormEncode's UnicodeString validator didn't work, producing ascii error when redisplaying the form. Using TW version did work fine.

4. Is it possible to specify error_handler as a full request path, e.g. "/pages/contacts/" instead of attrname of the current obj? The default approach is too inflexible (as is Pylons default, btw)

5. I think "fancy fields" part could be safely moved to "part X" document

6. I'd really like to see docs that tell how to control layout of the HTML code produced. You see, I have a great HTML/CSS guy in my team and he is responsible for all HTML/CSS produced by our app. Hence he wants to be in control and b able to easily tweak it. As it is, Python code essentially obscures what's going on underneath. He even objects to web_helpers and so I think twForms magic may be too much to ask. ;)

All in all, it seems good. The only thing it needs is IMO better exposure (more users, more use cases, more bugs gets fixed).

It may be a good idea to browse excellent docs for Django's newforms - TW competitor. You can steal ideas how to organize/present twForms concepts and may be some design ideas as well. I also contemplate idea to try to port newforms to Pylons, just to see whether it is technically feasible.

Max.