i've workaround this overloading init, so the other way exist.
But i surprised when not found meta class in simple form (model and
modelform have)
On Apr 20, 3:00 pm, Xavier Ordoquy wrote:
> Le 20 avr. 2011 à 09:22, Constantine a écrit :
>
> > On Apr 20, 12:26 pm, Xavier Ordoquy wrote:
> >> Le 2
Le 20 avr. 2011 à 09:22, Constantine a écrit :
> On Apr 20, 12:26 pm, Xavier Ordoquy wrote:
>> Le 20 avr. 2011 à 05:57, Constantine a écrit :
> ...
>> Actually, I don't understand.
>> If you need object creation, ModelForm is the way to go.
> unfortunately ModelForm is not suitable
>> You could
On Apr 20, 12:26 pm, Xavier Ordoquy wrote:
> Le 20 avr. 2011 à 05:57, Constantine a écrit :
...
> Actually, I don't understand.
> If you need object creation, ModelForm is the way to go.
unfortunately ModelForm is not suitable
> You could also take it the other way. Base form should be the one wit
Le 20 avr. 2011 à 05:57, Constantine a écrit :
> FormModel have exclude attribute in Meta, but simple Form doesnt:
> example usage:
>
> i need base form for editing with many fields, and derived form for
> object creation with subset of fields and so i want to exclude
> unnecessary fields
Actua
generally it's lack of Meta subclass in simple form, in which we can
configure fields order, exclusion of some fields etc. Now i should
override __init__ method, its not so declarative way as in modelform
--
You received this message because you are subscribed to the Google Groups
"Django develo
FormModel have exclude attribute in Meta, but simple Form doesnt:
example usage:
i need base form for editing with many fields, and derived form for
object creation with subset of fields and so i want to exclude
unnecessary fields
--
You received this message because you are subscribed to the Go
