| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
PDFTemplateResponse is like TemplateResponse in that it does dynamic
rendering of a template on the fly.
PDFTemplateView has a much smaller implementation, relying on
PDFTemplateResponse to do the rendering for it. It also knows about
the standard TemplateResponse when it needs to render the HTML version.
|
|
|
|
|
|
|
| |
* Now matches HttpResponse in function signature.
* Modern Django content_type/mimetype handling.
* Sanitizes and quotes filenames in Content-Disposition header.
* Tests.
|
| |
|
|
|
|
|
| |
In case you want to pass more things up to HttpResponse.
Can't pass filename down though.
|
|
|
|
|
|
|
| |
Setting 'Content-Disposition' explicitly sets the PDF as an attachment causing
browsers to download the PDF. However newer browsers, like Chrome, will
display the PDF without this header. So assume the dev wants this to be force
download if they set the filename.
|
|
|
|
|
| |
Put _tmp_files onto the object and remove them after the output has been
created.
|
|
|
|
| |
If there's no context_instance (which seems to be the common case), make a Requestcontext and use that.
|
|
|
|
|
| |
Rather than directly going to self.template_name use the get_template_names() function
(which returns self.template_name if not overridden).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Use a PdfResponse to deal with the headers and response type.
Make the margin_* and filename variables instance variables on the view
with sane defaults.
|