If we have radio_admin for ForeignKeys (we do), then I can't see why we
wouldn't want checkbox_admin for M2M.
The danger with ether of these is that it becomes a very poor UI when
there starts to be more than a handful of choices. But...if we've
decided it's okay for one, it seems that it ought t
go-users@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of Malcolm Tredinnick
Sent: 27. heinäkuuta 2006 18:39
To: django-users@googlegroups.com
Subject: Re: Wondering about few 'burried' issues
On Thu, 2006-07-27 at 03:39 -0700, Sebastian F wrote:
> I have been researchin
Sebastian F wrote:
> Another issue was with "BooleanFields". I noticed they always hit the
> history even if not changed. Someone else had noticed this too and
> already posted a ticket (http://code.djangoproject.com/ticket/1511).
> Pretty easy to fix but has been open for 4 months?
>
> These are
On Thu, 2006-07-27 at 03:39 -0700, Sebastian F wrote:
> I have been researching few (web) application frameworks and
> considering our projects, Django outperforms all of them easily,
> reflecting exactly what we were going to build (well, no need to build
> now).
>
> After playing around with so
On 27 Jul 2006, at 11:39, Sebastian F wrote:
> But then it hit me, ticket was closed with
> resolution 'wontfix' (http://code.djangoproject.com/ticket/2004). I am
> curious, why?
Your guess is as good as mine - it looks like the ticket was closed
by the person who opened it. The Django core d
5 matches
Mail list logo
