Hi Bobby, you're best off going through the tutorial in the online
docs, that has a basic explanation of how views made, and how you can
render a template with a given context. Try this bit in particular:
http://www.djangoproject.com/documentation/tutorial03/#write-views-that-actually-do-something
Basically, 'context' is a dictionary of variable names that will be
available to a template when it's filling in all its placeholders (ie,
your {{form}} variable). Except for a few context variables that
django internals might set automatically, you need to pass all those
variables to the template explicitly in your render_to_response()
function. As you can see from Andrew's example, the format is:
render_to_response('template/name.html', {'varname':variable,
'anothervarname':variable2}, otherstuff=stuff)
Also, in the "if request.response == "POST"" branch of your view, you
don't need to check explicitly if a zipcode was set. That's why we
love newforms – it does that stuff for you. Bind the POSTed data to an
instance of your form like so:
form = form_upslookup(request.POST)
then call:
form.is_valid()
If it is, you can use it. If it's not, you can pass that bound form
instance right back out to the template, just as though it were a
blank form (try re-using the GET branch of the view), and it will show
up with all the user's entered data still in place, plus handy error
messages for failed fields.
Newforms are better than sliced cheese.
E
On Jun 3, 2008, at 3:36 AM, Bobby Roberts wrote:
>
> ok i'm new to django... can you explain that?
>
>
>
>
> On Jun 2, 3:26 pm, Andrew Ingram <[EMAIL PROTECTED]> wrote:
>> It looks like you need to add the form to your view contexts.
>>
>> return render_to_response ("UPSRateLookUp/upsratelookup.html",{
>> "form": form
>> "results": results,
>> "query": query
>> })
>> else:
>> form = form_upslookup()
>> return render_to_response
>> ("UPSRateLookUp/upsratelookup.html",{"form": form})
>>
>> The thing to remember is that there's nothing special about forms
>> when
>> it comes to django templates, a form is simply another object that
>> must
>> be passed in the template context if you wish to use it.
>>
>> - Andrew
>>
>> Bobby Roberts wrote:
>>> yeah i'm looking at that but it doesn't make sense to me.....
>>> here's a
>>> snip
>>> of my template, the forms.py file and the views.py file. Here are
>>> my
>>> questions:
>>
>>> 1. the form doesn't show up on the template... what am I missing
>>> here
>>> to
>>> get my form to show up?
>>
>>> 2. how in the world do I tell the system that the form on the
>>> template
>>> should submit and use the process_upslookup view?
>>
>>> -lost
>>
>>> *template.html* (snip)
>>
>>> <form method="post" action=".">
>>> {{ form }}
>>> <input type="submit" name="submit" value="Get
>>> Estimate*">
>>> </form>
>>
>>> *forms.py*
>>
>>> from django import newforms as forms
>>
>>> class form_upslookup(forms.Form):
>>> zipcode=forms.CharField(max_length=15, required=True,
>>> help_text='Please
>>> enter your zipcode')
>>
>>> *views.py*
>>
>>> from forms import form_upslookup
>>
>>> def process_upslookup(request):
>>> if request.method=='POST':
>>> form = form_upslookup
>>> query = request.POST.get('zipcode','')
>>> if query:
>>> results=query
>>> else:
>>> results="No Zipcode Entered"
>>> return render_to_response ("UPSRateLookUp/
>>> upsratelookup.html",
>>> {
>>> "results": results,
>>> "query": query
>>> })
>>> else:
>>> form = form_upslookup()
>>> return render_to_response ("UPSRateLookUp/
>>> upsratelookup.html")
> >
--~--~---------~--~----~------------~-------~--~----~
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 PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
