Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide if we use another form tool instead of pyramid_simpleform #19

Open
miniwark opened this issue Mar 21, 2012 · 3 comments
Open

Decide if we use another form tool instead of pyramid_simpleform #19

miniwark opened this issue Mar 21, 2012 · 3 comments
Assignees
Labels
Milestone

Comments

@miniwark
Copy link
Member

We are actuality using pyramid_simpleform for form management. We need to give a try to alternatives likes Deform, WTForms, etc.. and decide if we keep simpleform or use something else.

@ghost ghost assigned miniwark Jul 24, 2012
@miniwark
Copy link
Member Author

We will not try Deform as i do not see advantages compared to pyramid_simpleform.
WTForms seems to be a good alternative because is more understandable to Django users
and because it may have a better i18n support than pyramid_simpleform.

Actualy the only big problem with pyramid_simpleform is the i18n support (see #24)

@miniwark
Copy link
Member Author

The i18n support of pyramid_simpleform is now working.
But, we may give a try to WTForms in a branch to see if it's better than pyramid_simpleform.

@miniwark
Copy link
Member Author

Working on a WTForms branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant