I think sqlwidgets is a great idea and I'm determined not to duplicate
data and logic in my forms.  Referring to formmaker.column_params,
couldn't you use column.validator as the validator by default?  Also,
could there be a use for these attributes?

foreignKey:  for creating a list or search to populate the element.
notNone:  validation.  Should be done by column.validator, right?
tags:  Not sure what those are.
varchar:  If False, set a maxlength attribute in the element.

I think that SQLObject should and does to a good degree facilitate
detailed descriptions and rules for its data in a way that is reusable
and TurboGears should take full advantage.

A simple but cool example:  An "email" column is defined in an
SQLObject class as notNone.  Its FormEncode validator checks to see the
address is valid.  TurboGears automatically generates the column
complete with server side and javascript validation to ensure the value
is not null and a valid email address.

Randall

Reply via email to