This is still pretty WET for my tastes, but I do not completely understand
your requirements. Programming is after all an art and a science. I have a
tendendcy to normalize things as much as I feel is reasonable, perhaps it is
more than you require. I would at least consider something like the
f
Currently, I'm working from the demos in the book and the site.
Here is what I have currently.
forms.py:
from django import newforms as forms
from django.newforms import form_for_model
from models import PlanMember
TITLES = (
('Miss','Miss'),
('Mrs.','Mrs.'),
('Ms.','Ms.'),
('M
Interesting
I could set-up a single people table/model with a field indicating the
position/relation to the form/application.
I would guess I would to hand make the blank form then and am unsure
how to parce it on the other side...
Didn't see that in the tutorials...
Lance
On May 21, 4:36
Lance, it's also not clear to me what exactly you need. Are you using
ModelForm? If not, what do you mean by the 'auto generated' form? I
think I have a rough idea what you're looking for, but a few more details
would go a long way.
Adam
On Wed, May 21, 2008 at 3:30 PM, Lance F. Squire <[EMAIL P
I would caution you to think in the terms of the data storage
(models) separately from data entry (forms via views). Most likely you want
a class Person which would have a field for title. Maybe the title field is
a FK to the Title model, maybe it is a charfield with or without 'choices'
depending
I'm trying to make a Form where 3 people need to be inputed. All three
need to have a Title.(EG. Mr. Mrs. etc.)
I tried making the Title fields in the database be a key to a table of
title selections. The sql generation had no trouble with that, but the
Form generator doesn't like it at all...
I
6 matches
Mail list logo