blocks|key|1563001|text|我们使用subversion。只需在/trunk/docs下放置一个文件夹以进行比较，并让设计人员签出并提交到该文件夹。工作起来像个冠军。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1563002|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We use subversion. Just place a folder under /trunk/docs for comps and have designers check out and commit to that folder. Works like a champ.

blocks|key|1563154|text|我肯定会把图形放在版本控制之下。在diff工具中，差异可能不是很有用，但您仍然可以签出图形的两个版本，并并排查看它们的差异。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1563155|我看不出有任何理由不应该将生成的图形保存在程序员使用的相同版本控制系统中。但是，当您使用PSD文件或PDN文件创建图形时，您可能希望为这些文件创建一个单独的存储库，因为它们与实际的最终jpeg或gif具有不同的上下文，这些jpeg或gif是与开发的应用程序一起生成和部署的。|1563156|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would definitely put the graphics under version control. The diff might not be very useful from within a diff tool like diffmerge, but you can still checkout two versions of the graphic and view them side by side to see the differences.

I don't see any reason why the resultant graphics shouldn't be kept in the same version control system that the coders use. However, when you're creating graphics using PSD files or PDN files you might want to create a seperate repository for those as they have a different context to the actual end jpeg or gif that is produced and deployed with the developed application.

blocks|key|1563234|text|@lomaxx+TortoiseSVN包括一个名为TortoiseIDiff的程序，它看起来与图像有所不同。我没有用过它，但看起来很有趣。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1563235|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

@lomaxx TortoiseSVN includes a program called TortoiseIDiff which looks to be a diff for images. I haven't used it but looks intriguing.

blocks|key|1563263|text|关于比较和合并，我认为版本控制对于图形和媒体元素更为关键。如果你想一想，大多数设计师都是文件的唯一所有者--至少在图形方面--或者至少我认为是这样的。我很想听听设计师的意见。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1563264|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

With respect to diff and merging, I think the version control is more critical for graphics and media elements. If you think about it, most designers are going to be the sole owners of a file -- at least in the case of graphics -- or at least I would think that'd be the case. I'd be curious to hear from a designer.

blocks|key|1563311|text|我们也只是将二进制文件放在源代码控制中。我们使用Git，但它同样适用于Subversion。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1563312|我的一个建议是尽可能使用SVG，因为您可以看到实际的差异。对于二进制文件(大多数其他图像格式)，您能得到的最好结果是版本历史。|1563313|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

We, too, just put the binaries in source control. We use Git, but it would apply just as well to Subversion.

One suggestion I have is to use SVGs where possible, because you can see actual differences. With binaries (most other image formats), the best you can get is a version history.

blocks|key|1778550|text|许多图形化类型的人想要比subversion更复杂的东西。虽然它对版本控制很好，但他们需要一个内容管理系统，允许交叉引用资产、标记、缩略图和类似的东西(以及版本控制)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1778551|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A lot of the graphics type people will want something more sophisticated than subversion. While it's good for version control, they will want a content management system that allows cross-referencing of assets, tagging, thumbnails and that sort of thing (as well as versioning).

blocks|key|1778653|text|是的，在版本控制中拥有艺术资产是非常有用的。您可以跟踪历史记录、回滚更改，并且只需一个源即可进行备份。请记住，art资产要大得多，因此您的服务器需要有大量的磁盘空间和网络带宽。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1778654|我已经成功地在非常大的项目(%2B100+GB)上使用了perforce，但是我们必须用一些对艺术家更友好的东西来包装对版本控制服务器的访问。|offset|length|1778655|我也听说过一些关于Alienbrain的好消息，它看起来确实有一个非常流畅的UI。|1778656|entityMap|0|LINK|mutability|MUTABLE|url|http://www.perforce.com/|1|http://www.alienbrain.com/^0|0|Q|8|0|0|9|A|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

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 &amp; network bandwidth.

I've had success with using <a href="http://www.perforce.com/" rel="noreferrer">perforce</a> 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 <a href="http://www.alienbrain.com/" rel="noreferrer">Alienbrain</a> as well, it does seem to have a very slick UI.

blocks|key|1778701|text|@Damian+-关于标签和交叉引用的好观点。这是真的；虽然我没有在软件开发项目上与许多设计师合作过，但我曾在一家有设计部门的公司工作，知道这是一个问题。设计者仍然(永远)在寻找一个完美的系统来处理这类事情。我认为这更适合于设计部门对所有资产进行共享访问、搜索和版本控制等--在这种情况下，业务动机是不在任何可能的地方/任何时候重新发明轮子。我不认为它适用于面向项目的方式，因为标签和交叉引用不太适用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1778702|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

@Damian - Good point about the tagging and cross referencing. That's true; while I haven't working with many designers on a software development project, I have worked for a company that had a design department and know that this is an issue. Designers are still (perpetually) looking for the perfect system to handle this sort of thing. I think this is more suited to a design department for shared access, searching and versioning, etc to all assets -- where there is a business incentive to not reinvent the wheel wherever/whenever possible. I don't think it would apply for a project-oriented manner as tagging and cross referencing wouldn't be quite as applicable.

blocks|key|1778755|text|我们使用Perforce对二进制文件和镜像进行修订控制。太棒了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1778756|我们保留了大量的艺术资产，并且它可以很好地扩展到大量的大文件。它可以识别那些无法区分的二进制文件，并在后端将它们存储为完整的文件副本。|1778757|它有P4V+(跨平台可视化浏览器)和缩略图系统，因此可以在浏览器中看到图像文件。|1778758|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

We keep the binary files and images in revision control, using Perforce. It's great!

We keep a lot of art assets, and it scales well for lots of large files. It recognizes binary files, the ones that can't be diffed, and stores them as full file copies in the back end.

It has P4V (cross-platform visual browser), and a thumbnail system so image files can be seen in the browser.

blocks|key|1563657|text|TortoiseSVN可以并排显示图像修订，这真的很有用。我已经在不同的团队中使用过它，并取得了很大程度的成功。艺术家们喜欢有回滚东西的能力(在他们习惯了概念之后)。不过，它确实需要很大的空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1563658|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

TortoiseSVN can show image revisions side-by-side, which is really useful. I've used it with different teams with a great degree of success. The artists loved having the ability to roll back things (after they got used to the concepts). It does take a lot of space, though.

blocks|key|1563716|text|你可能想看看Boar：“简单的版本控制和备份照片，视频和其他二进制文件”。它可以处理任何大小的二进制文件。http://code.google.com/p/boar/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1563717|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/boar/^0|1H|U|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might want to take a look at Boar: "Simple version control and backup for photos, videos and other binary files". It can handle binary files of any size. <a href="http://code.google.com/p/boar/" rel="nofollow">http://code.google.com/p/boar/</a>

blocks|key|1563783|text|GitHub最近推出了“图像查看模式”，看看：https://github.com/blog/817-behold-image-view-modes。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1563784|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/blog/817-behold-image-view-modes^0|N|1F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

GitHub recently introduced "image view modes", take a look: <a href="https://github.com/blog/817-behold-image-view-modes" rel="nofollow noreferrer">https://github.com/blog/817-behold-image-view-modes</a>.

blocks|key|1778974|text|一个免费的和稍微不可靠的解决方案是Adobe+version+Cue，它随Adobe+Suite一起提供到CS4，并且易于安装和维护。提供用户级别的控制，并且对艺术家友好。Adobe已经停止了对它的支持，这是一件令人遗憾的事情。Adobe+Bridge充当用户和Version+Cue服务器之间的客户端。如果使用得当，它是一种廉价的版本控制解决方案。我使用带有CS3桥的CS3版本提示。对于小型团队来说效果很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1778975|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A free and slightly wonky solution is Adobe version Cue its comes with the Adobe Suites up to CS4 and is easy to install and maintain. Offers user level control and is artist friendly. Adobe has discontinued support though for it which is a shame. Adobe Bridge acts as the client between the user and the Version Cue server. If used properly its an inexpensive solution to version control. I use CS3 version cue with CS3 Bridge. Works great for small teams.

blocks|key|1563938|text|在我看来，结合了备份解决方案的Pixelapse是迄今为止我所发现的最好的图形版本控制软件。它支持adobe文件和一堆普通的光栅图像。它有一个版本一个版本的预览。它会在文件更新时自动保存(保存时)。它的工作原理类似于dropbox，但有一个很棒的web界面。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1563939|您可以在团队中使用它，并将项目共享给不同的人。它还支持无限的审阅者，这对设计机构来说是很棒的。如果你愿意，你可以在“开放”的项目上公开协作。|1563940|不幸的是，你不能有一个本地的pixelapse服务器，所以为了备份，我目前的设置是在一个git库中有一个Pixelapse文件夹(类似于dropbox文件夹)，用于创建快照。|1563941|entityMap|0|LINK|mutability|MUTABLE|url|https://www.pixelapse.com/^0|F|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

In my opinion <a href="https://www.pixelapse.com/" rel="nofollow">Pixelapse</a> combined with a backup solution is the best version control software for graphics that I've found thus far. It supports adobe files and a bunch of normal raster images. It has version by version preview. It autosaves when the files update(on save). It works like dropbox but have a great web interface. 

You can use it in teams and share projects to different people. It also support infinite reviewers which is great for design agencies. And if you want you can publicly collaborate on projects that are "open".

Unfortunately you can't have a local pixelapse server, so for backup my current setup is that I have the Pixelapse folder(like a dropbox folder) inside a git repo for snapshot creation.

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?

Version Control for Graphics

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

比方说，一个开发团队包括(或利用)图形设计师，他们创建了产品中的所有图像。这些东西包括图标、位图、窗口背景、按钮图像、动画等。显然，构建一个软件所需的一切都应该受到某种形式的版本控制。但大多数面向开发人员的版本控制系统主要是为基于文本的信息而设计的。图形人员是否应该使用与程序员相同的版本控制系统和存储库？如果不是，他们...

问图形的版本控制
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问图形的版本控制EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问图形的版本控制
EN