Hi all --
I've started to poke around in customizing the generated form code
and providing my own widget instances, but the current Django form
code is written in such a way that it makes things nearly impossible.
Here's just one example: when fields are written out to HTML, they
get asked
On Jan 21, 5:37 pm, Russell Keith-Magee
wrote:
> > Here's just one example: when fields are written out to HTML, they
> > get asked "what attributes does this kind of widget need?".
>
> Unless I'm misunderstanding your intent with this statement - No, they
> aren't. A form contains fields, whic
On Jan 21, 7:20 pm, Malcolm Tredinnick
wrote:
> In the larger scheme, I think this is one of those areas where people's
> initial intuition differs. Django's form classes generally push
> downwards, with the greater intelligence lying at the higher levels
> (forms know the most, then form field c
On Jan 22, 12:12 am, Jacob Kaplan-Moss
wrote:
> On Thu, Jan 22, 2009 at 4:57 PM, catsclaw wrote:
> > Well, it seems to me that makes for an *extremely* tight coupling
> > between the model and the view.
>
> I'm sorry to be so blunt, but your perception is misguided.
On Jan 22, 12:12 am, Jacob Kaplan-Moss
wrote:
> Why don't we start over here: what is the problem? What did you try do
> do? What did you expect to happen? What actually happened?
Here's another problem I'm stuck at. I'm trying to determine,
within a widget, whether I'm being asked to draw a
On Jan 22, 11:53 pm, Russell Keith-Magee
wrote:
> On Fri, Jan 23, 2009 at 5:02 AM, catsclaw wrote:
> > I could have been clearer. I'm not talking about Django Models
> > here; I'm talking about models, views, and controllers from the Model-
> > View-Controller
