版本控制的图形 [英] Version Control for Graphics

问题描述

说一个开发团队包括（或利用）制作所有进入产品的图像的图形艺术家。这些东西包括图标，位图，窗口背景，按钮图像，动画等。

显然，构建软件所需的一切应该采用某种形式的版本控制。但是大多数针对开发人员的版本控制系统主要设计用于基于文本的信息。图形人员是否应该使用与编码人员相同的版本控制系统和存储库？如果不是，他们应该使用什么，什么是保持所有内容同步的最佳方式？

版本控制非常有用。您可以跟踪历史记录，回滚更改，并且可以使用单一来源进行备份。请记住，艺术资产要大得多，因此您的服务器需要大量的磁盘空间和存储空间。网络带宽。

我已经成功使用 perforce

a>在非常大的项目上（+ 100 GB），但是我们必须使用一些更友好的艺术作品来访问版本控制服务器。

还有一些关于 Alienbrain 的好消息，它似乎有一个非常漂亮的用户界面。

Say a development team includes (or makes use of) graphic artists who create all the images that go into a product. Such things include icons, bitmaps, window backgrounds, button images, animations, etc.

Obviously, everything needed to build a piece of software should be under some form of version control. But most version control systems for developers are designed primarily for text-based information. Should the graphics people use the same version-control system and repository that the coders do? If not, what should they use, and what is the best way to keep everything synchronized?

解决方案

Yes, having art assets in version control is very useful. You get the ability to track history, roll back changes, and you have a single source to do backups with. Keep in mind that art assets are MUCH larger so your server needs to have lots of disk space & network bandwidth.

I've had success with using perforce on very large projects (+100 GB), however we had to wrap access to the version control server with something a little more artist friendly.

I've heard some good things about Alienbrain as well, it does seem to have a very slick UI.

这篇关于版本控制的图形的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！