On Wed, 2008-04-02 at 17:06 -0700, msaelices wrote:
> This mail maybe can be splitted in two, but I write only one because
> both are related.
>
> Ok, ModelForms is a very very wonderful thing, but I want to talk
> about (maybe) excessive implicitness.
>
> Look at this form declaration:
>
> cl
On 4 abr, 00:28, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> What about replacing the idea of a ModelForm with a ModelField? Then
> for shorter
> forms you could list all the fields explicitly, without having to
> recode all the
> default field definitions.
I think should be hard to implemen
What about replacing the idea of a ModelForm with a ModelField? Then
for shorter
forms you could list all the fields explicitly, without having to
recode all the
default field definitions.
e.g.:
class MyForm(forms.Form):
foo = forms.ModelField(SomeModel, 'foo', widget=forms.Textarea)
bar
On Wed, Apr 2, 2008 at 7:06 PM, msaelices <[EMAIL PROTECTED]> wrote:
> Now, what do you see? You first think again in a form with two fields,
> however maybe is a form with five fields. What is happening? You
> explicity define two fields, and the real action is a _redefinition_
> of two field
This mail maybe can be splitted in two, but I write only one because
both are related.
Ok, ModelForms is a very very wonderful thing, but I want to talk
about (maybe) excessive implicitness.
Look at this form declaration:
class AuthorForm(forms.Form):
name = myforms.MyCharField(max_length=1
