Monkey
09-04-2003, 06:26 AM
Please can someone help with this?
I'm running a web-based photographic library system on our corporate intranet and, for reasons I won't bore you with, the photo source files are stored on the server as serially numbered files, e.g. P001234.jpg.
Users are allowed to download the medium res image. Currently, they're told to right-click on the image and choose 'Save Picture As...'. The problem is, the resulting filename doesn't mean anything to either the customer or the photo library staff. Instead, each picture is traditionally referred to by its 'Picture Reference Number', e.g. 'WW654123' or HIS1234' etc., a legacy from the old manual system.
You can imagine the confusion that's caused when for instance a user downloads a picture then rings the photolibrary a few days later and refers to it by the name of say 'P001234'.
So, the question is: can JS be used as an alternative to the usual 'Save Picture As...' approach, with the additional trick of saving a graphic under a different name (which is determined by the system)?
The HTML is genererated by a CGI script on the fly so we can easily include a JS routine with the relevant source and destination filename for any given picture. As for where they save it to, it would be most useful if they can still use a browse button much like the current 'Save Picture As' method, though simply saving it to the Desktop without prompting would be just about tolerable if not.
I hope I've explained this properly, albeit v longwinded!
I'm not a JS programmer so please be gentle :) Would immensely appreciate any help, thanks.
I'm running a web-based photographic library system on our corporate intranet and, for reasons I won't bore you with, the photo source files are stored on the server as serially numbered files, e.g. P001234.jpg.
Users are allowed to download the medium res image. Currently, they're told to right-click on the image and choose 'Save Picture As...'. The problem is, the resulting filename doesn't mean anything to either the customer or the photo library staff. Instead, each picture is traditionally referred to by its 'Picture Reference Number', e.g. 'WW654123' or HIS1234' etc., a legacy from the old manual system.
You can imagine the confusion that's caused when for instance a user downloads a picture then rings the photolibrary a few days later and refers to it by the name of say 'P001234'.
So, the question is: can JS be used as an alternative to the usual 'Save Picture As...' approach, with the additional trick of saving a graphic under a different name (which is determined by the system)?
The HTML is genererated by a CGI script on the fly so we can easily include a JS routine with the relevant source and destination filename for any given picture. As for where they save it to, it would be most useful if they can still use a browse button much like the current 'Save Picture As' method, though simply saving it to the Desktop without prompting would be just about tolerable if not.
I hope I've explained this properly, albeit v longwinded!
I'm not a JS programmer so please be gentle :) Would immensely appreciate any help, thanks.