4 ms·
I suppose, I never really version control those, just track the revisions by uploading updates of the comps for the client, or using share drives if I'm working
by erlanger 17y ago
I suppose, I never really version control those, just track the revisions by uploading updates of the comps for the client, or using share drives if I'm working with other designers. I don't think you can merge PSDs, so many of the benefits of an SCM vanish.
- gry 17y agoHere is a working example of doing diff patches on PSDs. http://www.codediesel.com/tools/transferring-psd-files-quickly/ http://www.codediesel.com/tools/transferring-psd-files-quick... I've never tried it.
- cschneid 17y agoI agree, you lose the merging when you work with binaries (for the most part). But when I was at HP, our little team was behind the curve in tool use, and I was pushing for a comprehensive scm, instead of the patchwork we had. My big selling point was that given a stack of windows and database install disks, and the scm, you should be able to bootstrap the project up, and get it running. I really like that point of view when it comes to SCMs. It's the official repository of everything project related. You have code, docs, graphics, everything needed. You do lose out on merging and stuff with binaries, but that's a small price to pay for the peace of mind you get.