Thanks to everyone for contributing to this discussion. I guess I should summarize my findings, for the sake of anyone attempting to resolve the same issue:
1. pyramid_simpleform does what it says - it is simple to use & allows users to manually render their forms. FormEncode has resources behind it, so it is a safe choice for less-complex apps. 2. Colander/Deform is also a great combination, with good widget libraries, good documentation & lots of power, though is more complex than pyramid_simpleform. It's auto form rendering is great for those who want a simple form-rendering method. It only real drawback that I can see is the difficulty in manually laying out your form widgets into your html, if that is a requirement you have. 3. ToscaWidgets2 (ie tw2.core - I haven't looked into the ealier versions of TW - eg 0.9.x) is also a great framework, though again, it is more complex than pyramid_simpleform. It does have an excellent assortment of widgets (particularly in the area of graphs & charts), and the ability to manually render your form if you need this ability (see Ralph's earlier post), though it can also auto-render your form if you'd prefer. Probably the biggest drawback about TW2 for Pyramid users is the lack of how-to/code-example articles about. Given I am migrating an old TW1-based Pylons app to Pyramid, TW2 looks like the best option for me in this case. In general though, Pyramid users would probably benefit if there was a "pyramid_tw2" scaffold to allow users to easily add the framework to their Pyramid project... Cheers, BruceC On Jan 19, 2:32 am, Chris Lambacher <[email protected]> wrote: > Hi, > > Micheal (radeo) and I were talking on IRC. pyramid_simpleform will not > continue to support Colander in the future. The Colander support is half > baked and done because FormEncode was "unmaintained". FormEncode's > maintainership is no longer in question [1] so pyramid_simpleform can > continue to be a integration point for people who want to use FormEncode > with Pyramid. > > As one of the maintainers of FormEncode and a user of pyramid_simpleform, I > have committed to doing bug fixes and ongoing maintenance of > pyramid_simpleform. I do have some planned changes but have not had a > chance to get to them. I'll likely try to figure out some time during > sprints at PyCon (along with working on FormEncode) > > 1:http://sourceforge.net/mailarchive/forum.php?thread_name=CAO69NdkfE-E... > > -Chris > > > > > > > > > > On Wed, Jan 18, 2012 at 2:21 AM, Chris McDonough <[email protected]> wrote: > > On Tue, 2012-01-17 at 23:06 -0800, BruceC wrote: > > > Hi all, it would appear the current version of pyramid_simpleform > > > would be 0.6.1, which relies on Formencode, however I have spotted a > > > version 0.7 on bitbucket that Dan Jacob put together that also allows > > > a user to generate form schemas in Pyramid using Colander, which would > > > be my preference. > > > > Does anyone know if pyramid_simpleform 0.7 is stable for use with > > > Pyramid (& Colander)? > > > It's not. I think it may be an evolutionary dead end at this point, > > unless someone picks it up and runs with it. > > > - C > > > -- > > You received this message because you are subscribed to the Google Groups > > "pylons-discuss" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/pylons-discuss?hl=en. > > -- > Christopher Lambacher > [email protected] -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
