Re: Controlling form/widgets output

2009-01-30 Thread Russell Keith-Magee
On Sat, Jan 24, 2009 at 5:27 AM, catsclaw wrote: > > On Jan 22, 11:53 pm, Russell Keith-Magee > wrote: >> On Fri, Jan 23, 2009 at 5:02 AM, catsclaw wrote: Apologies for the delay in replying - I was busy with some other items on my Django todo list, and I knew that any reply was going to turn

Re: Controlling form/widgets output

2009-01-23 Thread catsclaw
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 design pattern.  Django widgets

Re: Controlling form/widgets output

2009-01-22 Thread Russell Keith-Magee
On Fri, Jan 23, 2009 at 5:02 AM, catsclaw wrote: > > 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,

Re: Controlling form/widgets output

2009-01-22 Thread Jacob Kaplan-Moss
On Fri, Jan 23, 2009 at 4:28 PM, Matt Boersma wrote: > That's an excellent question for the django-users list. Here we > discuss the development of django itself. Bit hasty on the trigger there, Matt. I asked Chris for the specific problems he's running into; he's responding to me. I appreciate

Re: Controlling form/widgets output

2009-01-22 Thread Matt Boersma
On Jan 22, 2009, at 9:23 PM, catsclaw wrote: > > 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

Re: Controlling form/widgets output

2009-01-22 Thread catsclaw
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

Re: Controlling form/widgets output

2009-01-22 Thread catsclaw
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. Forms have > no dependancy

Re: Controlling form/widgets output

2009-01-21 Thread Mike Amy
The FormRenderer idea is a good one. But how about generalised Renderer objects that take or inherit a template list, build a context and then can be passed around to fill in the details. Update-able at construction, processing or rendering, and able to be passed straight into another context for

Re: Controlling form/widgets output

2009-01-21 Thread catsclaw
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

Re: Controlling form/widgets output

2009-01-21 Thread Jacob Kaplan-Moss
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. Forms have no dependancy upon models, nor do models on forms, nor must views use fo

Re: Controlling form/widgets output

2009-01-21 Thread catsclaw
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

Re: Controlling form/widgets output

2009-01-21 Thread Malcolm Tredinnick
On Thu, 2009-01-22 at 08:37 +0900, Russell Keith-Magee wrote: > On Thu, Jan 22, 2009 at 7:39 AM, catsclaw wrote: [...] > > Adding a > > widget therefore requires rewriting the field classes you want the > > widget to be used with, rather than letting the widget interrogate the > > field classes.

Re: Controlling form/widgets output

2009-01-21 Thread Russell Keith-Magee
On Thu, Jan 22, 2009 at 7:39 AM, catsclaw wrote: > > 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. First off - as a ge

Controlling form/widgets output

2009-01-21 Thread catsclaw
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