Why should designers use version control?

Published July 20th, 2009 by Anatoly

In this post I wanted to explain how we decided to create a version control system for designers and why we think it’s important for designers to use such systems.

Being a software developer I have been using various version control tools (CVS, SourceSafe, Perforce, ClearCase, Subversion) for ages, and literally cannot imagine doing any serious project without some sort of VC system to hand. So I was shocked to discover that my wife (who is a graphic designer) didn’t use any VC system at all. We decided to do some market research, and it turned out that apart from VersionCue and some extremely expensive industrial-scale systems such as Softimage Alienbrain there was nothing what designers could use to control versions of their files. Of course it’s always possible to use a generic SVN/Git client to control versions of graphic files, but very few of the clients available on the market are intuitive enough to help the creativity flow.

That’s how Timeline was born.
version control for designers

So, why should designers use Version Control?

This topic has been a popular one recently with various respectable blogs and websites giving numerous reasons for designers to start using some version control systems.

I will just highlight the most important benefits of using a version control system:

1) The ability to easily save multiple versions of the same file - ideal for brainstorming
2) Automatic backup - all your files are securely stored in the repository along with all their versions
3) Centralised storage of all your assets - this feature becomes important when you are working on a project in a team environment
4) Simplified collaboration with developers - if you are working on a web project together with developers who use Subversion for the source code then you can use the same SVN server as they do. This will help to keep all project files organised in one place and backed up when necessarily.

Why PixelNovel Timeline is the best version control for designers?

Timeline was created specifically for designers, so I would dare say that it’s the best version control system for designers.
Here are the features that make it the best choice for Photoshop professionals.

  • Photoshop plug-in with the unique UI - see all your versions, submit and get older versions with one mouse click
  • easy set-up without the need to understand SVN-specific terminology (”repository checkout”, “working copy”, “conflicts”, “clean-ups”) - we tried very hard to make everything as simple and intuitive as possible
  • hosted SVN server with previews of all your files and versions and with the ability to download any version
  • access and user rights management for your team
  • standalone client for those who already have an SVN server/repository

We also have a lot of work in progress to make Timeline even better for creative professionals. Here are just some of the features we have planned:

  • The “share” and “comment” features in the web interface: we are working on adding the possibility to make some (or all) of your files visible to your clients (or the whole world) by pressing a single button in the web interface. Your clients will be able to leave comments under the versions you shared with them.
  • Integrated layer-by-layer comparison of PSD files (ComparePSD inside Timeline)
  • Integrated repository browser
  • Timeline plug-ins for other Adobe products (Illustrator, InDesign)
  • So, are you ready to give Timeline a go? If you have any doubts or questions feel free to contact us at contact@pixelnovel.com

    3 Responses to “Why should designers use version control?”

    1. jed schneider says:

      so just curious, what was your rationale to use svn over git for versioning binaries. does timeline actually treat a psd file as a binary, or something else? how does timeline deal with moving files in the tree, is it calling svn move each time an asset goes between folders, or is deleted? does it detect those changes outside the photoshop environment? Thanks,

    2. Johan says:

      Hi

      I am also interested in what Jed asked.. does each commit store the complete PSD or will it only store the binary changes?

      Thanks

    3. Anatoly says:

      In SVN, only the difference between versions, not the full versions - no matter if the file is text or binary. You can read more about this here:
      http://help.collab.net/index.jsp?topic=/faq/svnbinary.html.

      “Note that whether or not a file is binary does not affect the amount of repository space used to store changes to that file, nor does it affect the amount of traffic between client and server. For storage and transmission purposes, Subversion uses a diffing method that works equally well on binary and text files; this is completely unrelated to the diffing method used by the ’svn diff’ command.”

      So, only the changes between 2 versions will be stored for a PSD file.

    Leave a Reply

    Spam Protection by WP-SpamFree