TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I work with FrameMaker, which has no interface with Visual SourceSafe,
so checking out a file and opening it in FM are two different
operations.
If we kept our graphics in VSS, and mirrored the directory structure on
our hard drives, it seems to me that we would still have to "get" all
the graphics each time we open a chapter file to ensure we have the
latest graphics. This would be time consuming. I don't even want to
think about the last check-out, when we check out the whole book
(300-400 MB).
I don't know what you mean when you talk about the batch file. I just
check the whole thing out to my hard drive and print to a .PS file. It
seems to me that your arrangement might create a headache for anyone
wanting to open these files later, after they've been archived.
I also don't know what you mean by "compile...automatically out of
SourceSafe".
P.S. We do save versions. That's the whole point of using VSS, I think.
>Not sure from your Techwriter post just where your problem with
SourceSafe
>lies, but I have been using SourceSafe to store referenced graphics
since it
>came out with no problems. I have approximately 600 referenced graphics
that
>I use in Word DOCs, WinHelp 16, and WinHelp 32. Although I have had
Word,
>RoboHelp, and operator head space mess up graphics, I have never had
>SourceSafe mess any up. I work on a network and mirror the development
tree
>in my work area in SourceSafe. We compile two ways: manually out of the
work
>trees and automatically out of SourceSafe. This requires two things:
>1. Everyone's development tree must mirror the SourceSafe project
tree.
>2. The batch file that compiles automatically gets the entire project
tree
>to a virtual drive named the same as our work areas. (Around here,
everyone
>maps their work area to H:\DEV. When the batch file GETs the projects
for
>compiles, it places them H:\DEV in the compile area. Thus all the
references
>remain connected.)
