History file generation Hot

by PVCS User +10 years no newbie on March 11, 2016

When getting history on a file or revision you get an html file at a very inconvient location with a non saying name.

E.g. //C:/Users/peter/AppData/Local/Temp/pvcs/6767hva.htm

Appdata in the path is also a hidden folder.

Instead launch a save as dialog and let user chose an appropriate location and default the name to something related to the files, revision, label or project for which the history is generated.

E.g. MyLabel_History.html

  • When getting history on a file or revision you get an html file at a very inconvient location with a non saying name.

    E.g. //C:/Users/peter/AppData/Local/Temp/pvcs/6767hva.htm

    Appdata in the path is also a hidden folder.

    Instead launch a save as dialog and let user chose an appropriate location and default the name to something related to the files, revision, label or project for which the history is generated.

    E.g. MyLabel_History.html

    Ideas

    Status
  • Please login to view any attachments.

  • Already have an account? or Create an account
    Hello "PVCS User +10 years no newbie" (awesome name!),

    The directory VM writes these reports to is a 'pvcs' subdirectory in your Windows temp directory, i.e. "%TEMP%pvcs". That location could be changed by way of asserting a different temp folder via a launch parameter (not something you'd typically do) but the non-saying name is there because VM computes a hash involving the current date and time to ensure the file is unique, as the same code has to deal with a multi-user system.

    Since VM launches a web-browser that shows the file it generated, I'd like to understand your use case why having it in a different location and with a different name is handy. Saving the existing the report from the browser using File -> Save As seems trivially easy. Am I overlooking something?

    Thanks for clarifying!

    - Richard.
    Richard Gering Commented by Richard Gering August 23, 2016
    Top 50 Reviewer  -  

    Hello "PVCS User +10 years no newbie" (awesome name!),

    The directory VM writes these reports to is a 'pvcs' subdirectory in your Windows temp directory, i.e. "%TEMP%pvcs". That location could be changed by way of asserting a different temp folder via a launch parameter (not something you'd typically do) but the non-saying name is there because VM computes a hash involving the current date and time to ensure the file is unique, as the same code has to deal with a multi-user system.

    Since VM launches a web-browser that shows the file it generated, I'd like to understand your use case why having it in a different location and with a different name is handy. Saving the existing the report from the browser using File -> Save As seems trivially easy. Am I overlooking something?

    Thanks for clarifying!

    - Richard.

     

PrintEmail