Adobe Flash项目的版本控制 [英] Version control for Adobe Flash projects

问题描述

我正在处理一个非常复杂的Flash项目，这是我们为客户使用而部署的全套服务的一部分。对于我们的大多数软件源代码（Java，PHP，Javascript，HTML和其他语言中的一些支持脚本），我们使用subversion进行版本控制和管理，所以我们对Flash项目也是这样做的，尽管我们从版本中获得的好处很少控制，除了能够恢复到以前的版本）作为FLA文件存储为只是二进制文件，我们不能得到有意义的差异。

我们把尽可能多的代码我们可以将其转换为AS文件，我们可以使用Subversion进行适当的管理，但是由于我们的体系结构和部署策略的要求（我们不能因为客户的需要而改变），我们仍然需要大量的FLA文件我已经看过Adobe Version Cue，虽然我不明白它在版本控制方面的作用，但将我们的Flash项目移动到版本托管提示会给我更好的控制，那么我现在从Subversion获得？

另外 - 如果人们可以分享他们对Flash项目版本控制的经验和建议，这将是非常有用的。

我自己也挣扎着，除了以外，我什么都不能告诉你：
$ b $ ol

在FLA中没有代码，

在适当的地方将内容语义分成单独的FLA

为FLA创建一个更改文档，并为每一个更改输入一个注释。

第一点很明显。其次是要认识到，FLA是二进制blob，它拥有所有的视觉资产，并且在版本控制方面表现不佳，但是你可以认识到这样的事实，即一些内容经常变化，而另一些则倾向于创建一次然后一个人留下。通过将您的资产分成不同的FLA，您可以将大部分更改保留在少量不稳定的FLA中，稳定和不稳定内容之间的差异将反映在版本文件中。

请注意，即使无法在运行时加载资产，编译时共享仍然可以让您将资产划分为任意数量的FLA。 （编译时间共享经常被忽略 - 如果您不熟悉它，请打开MovieClip的属性并查看底部的源代码部分。）如何划分内容取决于您的项目。我可以建议的最好的做法是在语义上进行划分 - 可能每个角色都有一个FLA，或者每个部分有一个FLA，或者每个界面元素有一个FLA等等。与所有的发展一样，目标是将相关资产分组并重复消除。第三点是，由于差异是不可能的，因此保留一个更改文件是没有办法的。我的首选方法是将FLA检查为版本控制，并记下签入说明中的所有更改，但是更改也可能位于单独的文档中。 （请注意，将每个FLA中的库保持有序是至关重要的，否则某人阅读变更描述将无法找到变更内容。）但是，由于这可能会使某些内容变得很痛苦，因此将某些FLA指定为不稳定，而不会为更改列表而烦恼。但如果这样的文件对其他文件有很大的依赖性，那么以后你会后悔的。

不幸的是，这是我迄今为止发现的。在未来的版本中，Adobe已经谈到了转换为基于文本的FLA格式，但在这之前，并没有简单的解决方案。

I'm working with a very complex Flash project which is part of a full range of services that we deploy for the use of our clients. For most of our software sources (Java, PHP, Javascript, HTML and a some supporting scripts in other languages) we use subversion for version control and management, so we do the same for our Flash projects, even though we gain little benefits from version controlling that (except being able revert to previous versions) as FLA files are stored as just binaries which we cannot get meaningful diffs from.

We're putting as much code as we can into AS files which we can properly manage using subversion, but due to the requirements of our architecture and our deployment strategy (both we cannot change because of our clients needs), we still maintain a large collection of FLA files that we need to manage.

I've looked at Adobe Version Cue and while I do not really understand what it does in terms of version control, will moving our Flash projects to hosting on Version Cue will give me better control then I currently get from Subversion?

Also - if people can share their experience and suggestions regarding version control of Flash projects, it will be very helpful.

解决方案

I've struggled with this myself, and I can't tell you anything other than:

1. No code in FLAs, ever
2. Divide content semantically into separate FLAs where appropriate
3. Make a change document for FLAs, and enter a note for every single change.

The first point is obvious enough. The second is to recognize that there's no getting around the fact that FLAs are binary blobs that hold all your visual assets and don't play well with versioning, but you can recognize the fact that some contents change frequently while others tend to be created once and then left alone. By dividing your assets into different FLAs, you can keep the large majority of changes into a small number of unstable FLAs, and the difference between stable and unstable content will be reflected in your versioned files.

Note that even if you can't load assets at runtime, compile-time sharing still lets you divide assets into an arbitrary number of FLAs. (Compile-time sharing is often overlooked - if you're not familiar with it, open a MovieClip's properties and check out the "Source" section at the bottom.) How to divide things will depend your project. The best I can suggest is to make divisions semantically - perhaps one FLA for each character, or one FLA for each section, or one FLA for each interface element, etc. As with all development the goal is to group related assets and eliminate duplication.

The third point is, since diffs are impossible, there's just no way around keeping a change document. My preferred way is to check the FLAs into versioning and note all changes in the check-in note, but the changes could also be in a separate document. (Note that it's vital that you keep the libraries in each FLA orderly, or someone reading the change description will have trouble finding the change.) However, since this can be a pain for some contents, it's also useful to designate certain FLAs as "unstable", and not bother with a change list. But if such files have a lot of dependencies on other files, you'll regret it later.

Unfortunately this is all I've discovered so far. Adobe has talked about changing to a text-based FLA format in a future version, but until that arrives, there's no easy solution.

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