Flash源代码管理 - 最佳实践 [英] Flash Source Control - Best Practices

问题描述

我现在正在开发一个Flash项目，我不得不迫使设计人员使用我们的源代码控制库（SVN）来帮助管理和跟踪项目。完全让他接受源代码控制的好处已经是一场艰苦的战斗了，但是它已经到来了。

我不必使用源代码控制一个Flash项目之前，除了我是唯一一个在其上工作的项目之外。我开始发现有一些额外的工作流程部分需要在周围实现，所以你没有一个噩梦战斗的二进制文件。

因为我主要在代码上工作，我已经把所有的ActionScript文件放到外部文件中，所以我可以在设计人员使用所有的图形处理FLA文件时使用它们。这似乎工作正常，但是当我需要更改实例名称之类的时候，我必须确保我的沟通良好，所以我们不会遇到任何问题。

我想知道其他人在源代码控制中如何处理Flash，以及他们如何管理工作流程，以便开发人员和设计人员可以同时处理项目。

谢谢。

解决方案

你几乎有解决方案。通信是版本控制系统中非常重要的一部分，对于二进制文件，您需要更加注意。不幸的是，许多人只是假设软件是最终的解决方案，团队沟通走出了窗口。

我将SVN传播给客户端非常大的Flash代码库。我不知道他们是否会再让我进入那座建筑物。我失败的原因是我无法改变组织的文化，所以在一个项目上工作的人之间有更多的沟通，结果是更多的人喊叫.fla是谁冲突。

也许采用每日scrum会议（有些人称之为站起来）。每天早上有五分钟的会议，并提到你将在当天工作，你可能会触及哪些文件。如果有可能会有冲突，一定要在工作中全天沟通。这样，没有人在黑暗中，为什么svn说fla文件上有冲突。

我希望这可以帮助。

I'm working on a Flash project right now and I am having to force a designer into using our Source Control repository (SVN) to help manage and track the project. It's been a bit of an uphill battle to fully get him to embrace the benefits of source control, but it's coming along.

I haven't had to use source control for a Flash project before other than on projects where I was the only person working on it. I'm starting to discover there are some addition workflow pieces you need to implement around it so you don't have a nightmare fighting binary files.

Since I'm mostly working on the code, I've place all the ActionScript files into external files so I can work on them while the designer works on the FLA file with all the graphics. This seems to be working out alright, but when I need to change instance names and the like, I have to make sure I communicate well so we don't run into any issues.

I was wondering how other people handle Flash in source control and how they manage the workflow so a developer and designer can be working on the project at the same time.

Thanks.

解决方案

You pretty much have the solution there. Communication is a very important part of version control systems and with binary files you need to be a lot more mindful of it. Unfortunately a lot of people just assume the software is the end all solution and team communication goes out the window.

I have made the mistake of evangelizing SVN to a client with a very large Flash codebase. I don't know if they will ever let me into that building again. Where I failed was that I was unable to change the culture of the organization so that there was more communication between people working on a project and as a result there was more yelling about who conflicted the .fla's.

Maybe adopt a daily scrum meeting ( some call it stand up ). Every morning have a five minute meeting and mention what you will be working that day and which files you may touch. If there is any probability that there will be conflicts be sure to communicate throughout the day while you work. This way no one is in the dark as to why svn is saying there is a conflict on a fla file.

I hope this helps.

这篇关于Flash源代码管理 - 最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！