Bobby Roberts wrote:
> I'm generating the
> response in my view as such:
>
> response = render_to_response("spreadsheet.html", {
> 'tms': tms,
> })
This is an evil hack, don't be surprised if weird things happen with it.
You should be using xlwt to generate your spreadsheets:
http://www.python-excel.org
> response['Content-Type'] = 'application/vnd.ms-excel'
> response['Content-Disposition'] = 'attachment;filename=biblio-
> export.xls'
...then you wouldn't be flat out lying here ;-)
> This works great with one exception. It saves the file to the
> person's last saved location... in my case it's the desktop, in other
> cases it's /downloads etc....
>
> Is there a way to force the SAVE option so that when they click SAVE,
> the user can determine where to put the file? My testing so far
> indicates this is not browser independent
Ultimately, your app has no business even trying to tell a browser where
to save things. Most browsers nowadays save to a location configured by
the user, if they right click and do something like "Save As" they will
get dialog box asking them where to save things.
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
