I could envision something like:
makeForm(User,
'getEmail',
requiredFields=['user_name', 'email_address'],
limitFields=['user_name', 'email_address'],
validators={'user_name':MyUsernameValidator(),
'email_address':MyEmailValidator()}
I just have to add a 'limitFields' argument and modify my ViewConfig
class a little bit, not to hard really. (The validator capability
you requested are already there.) The only problem is that makeForm
has 10 arguments already (in the trunk version) do we really want to
add another one?
Maybe, if you find this terribly useful then open an issue and I will
add it.
http://code.google.com/p/dbsprockets/issues/list
-chris
On Jan 15, 8:47 am, "Max Ischenko" <[EMAIL PROTECTED]> wrote:
> Hi Chris,
>
> On Jan 14, 2008 11:04 PM, percious <[EMAIL PROTECTED]> wrote:
>
>
>
> > I know a few of you on this board have been following the DBSprockets
> > project so I wanted to post about a recent development: primitives.
>
> Sounds cool!
>
> Though personally, I'm not that much interested in automatic form generation
> from SQLAlchemy models. I'd like to generate my forms "by hand". Just being
> able to say: I need a text field to enter user's name and another for email
> (with appropriate validators I'll supply). And I'd process validated form
> data on my own.
>
> Is it something DBSprockets supports or plans to support in the future?
>
> Max.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
