Re: On form libraries
I'd like to make a quick edit on the post and some comments to get the package names right ;)
I find rather disappointing that one of the points I try to get through in the scarce TW documentation (actually, the description of the package) rarely gets through as intended. ToscaWidgets does not handle form generation.
It only aspires to:
- bundle resources needed to build a web widget (as defined in this wikipedia entry). That is, it's (X)HTML markup (could also be template in any language that implements a Buffet plugin that generates it programatically), it's styling metadata (aka CSS) and it's client-side scripting.
- Serve those static resources using the WSGI protocol so it's pluggable in any compliant app/framework.
- Allow widget composition to create complex widgets.
- Provide infrastructure to package all this into a setuptools egg for easier reuse.
I actually believe it's flexible and powerful enough to serve as a good base to build the dream form library you're sketching out if twForms doesn't satisfy you :)
(I really need to get some docs out soon...)