On Thu, 18 Feb 2010 17:13:09 +0100, Boris Schaeling
wrote:
[...]I see. Then it means what I actually tried to do is impossible. I
can't use properties as described at
http://www.djangoproject.com/documentation/models/properties/ but should
overwrite save() and
On Thu, 18 Feb 2010 16:53:06 +0100, Gonzalo Delgado
wrote:
El 18/02/10 10:18, Boris Schaeling escribió:
This replaces the setter but not the getter.
To replace the getter, you'd have to override the modelform's __init__
method and set the corresponding field value
El 18/02/10 10:18, Boris Schaeling escribió:
>
> This replaces the setter but not the getter.
To replace the getter, you'd have to override the modelform's __init__
method and set the corresponding field value from the instance getter.
--
Gonzalo Delgado
--
You received
On Thu, 18 Feb 2010 02:01:16 +0100, Sam Lai wrote:
On 18 February 2010 10:49, Boris Schaeling wrote:
Is it possible to make a model's properties available in a form which
are
created as described at
On 18 February 2010 10:49, Boris Schaeling wrote:
> Is it possible to make a model's properties available in a form which are
> created as described at
> http://www.djangoproject.com/documentation/models/properties/?
>
> For example the following model form does not display
Is it possible to make a model's properties available in a form which are
created as described at
http://www.djangoproject.com/documentation/models/properties/?
For example the following model form does not display any widgets for
full_name and full_name2:
class
6 matches
Mail list logo