Hey Allen -- Any luck?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL P
Thanks for the code, I'll give it a shot.
As for initial values, I'm thinking about the add form. I'm sorry, I
should have said.
On Jul 9, 1:23 pm, leifbyron <[EMAIL PROTECTED]> wrote:
> Hi Allen,
>
> The RadioSelect widget is actually one of the more complicated ones in
> newforms. Its render m
Hi Allen,
The RadioSelect widget is actually one of the more complicated ones in
newforms. Its render method returns a RadioFieldRenderer object, which
in turn utilizes the RadioInput widget. The problem with using a
RadioSelect widget in newforms-admin is that the template is expecting
each widg
Hi Allen,
The RadioSelect widget is actually one of the more complicated ones in
newforms. Its render method returns a RadioFieldRenderer object, which
in turn utilizes the RadioInput widget. The problem with using a
RadioSelect widget in newforms-admin is that the template is expecting
each widg
Thanks Leif! I'll try to play around with the radio widget today. The
question about defaults was more simple. Formerly I had a model class
with default="0.0" or default=datetime.date.today() How do I reproduce
that with newforms-admin? Is there any easier way to provide initial
values (that's wha
Hi Allen,
I'm no Django expert (in fact, I just started learning a month ago),
but I'm happy to share what I have discovered so far.
>From what I can tell, the only way to override the default widget or
field for a model's database field is to subclass the Options class
and override the kwargs['
6 matches
Mail list logo
