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

问题描述

假设一个开发团队包括(或利用)图形艺术家，他们创建了进入产品的所有图像.这些东西包括图标、位图、窗口背景、按钮图像、动画等.

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.

我在非常大的项目 (+100 GB) 上使用 perforce 取得了成功，但是我们有用对艺术家更友好的东西来包装对版本控制服务器的访问.

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.

我也听说过一些关于 Alienbrain 的好消息，它似乎有一个非常漂亮的用户界面.

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

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