如何在 FlexBuilder 上进行团队合作
由于我和我的朋友正在 Flex Builder 上处理项目的相同源代码，因此我正在寻找一种解决方案，可以在不同的计算机上工作并编辑相同的源代码。
As me and my friend are working on the same source code of a project on flex builder, I'm looking for a solution that makes it possible to work on different computers and edit the same source code.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
你需要使用一些版本控制系统（VCS）。有关它的更多信息位于此处。就我个人而言，我更喜欢使用 Subversion。方便可靠。要直接从 Eclipse (Flash Builder) 使用它，您可以使用 Subclipse 或 颠覆性 插件。您可以在其中一台团队成员都可以访问的计算机上设置 Subversion 服务器。
You need to use some of the version control system (VCS). More info about it is here. As for me personally, I prefer to use Subversion. It is convenient and reliable. To work with it right from Eclipse (Flash Builder) you can use Subclipse or Subversive plugins. You can set up Subversion server on the one of the computers where everybody of the team member can have access.
任何版本控制系统都可以工作。尝试 CVS 或 SVN，两者都有 eclipse 客户端（即 flex builder）
Any version control system would work. Try CVS or SVN, the both have client for eclipse (which is flex builder)
Subversion 和 Subclipse 是您理想的团队解决方案。您所要求的（某种类型的链接实时编辑器）实际上并不存在于任何地方（并且可能不会非常有用，否则我们已经在这样做了）。
所以我认为你的问题的答案是，你只需要协调、计划、沟通和划分工作，这样你就不会踩到彼此的代码更改。一个不会导致代码更新始终发生冲突的良好架构是关键。 （尝试将项目划分为“模块”或子组件，甚至更好（如果适用的话），只让一个人专注于服务器端开发（Java、Coldfusion 或其他），而让另一个人担心Flex UI。这是保持客户端和服务器代码一定程度解耦的更简单方法之一，当然您仍然需要就服务接口进行沟通和规划。
Subversion and Subclipse is the ideal team solution for you. What you're asking for (some type of linked real-time editor) doesn't really exist anywhere (and probably wouldn't be terribly useful, otherwise we'd already be doing it).
So I think the answer to your question is, you just need to coordinate, plan, and communicate and divide up work so that you aren't stepping on each other's code changes. A decent architecture that doesn't cause your code updates to clash all the time is key. (Try dividing the project up into "modules" or sub-components, or even better (if this is applicable), just have one person focus on server-side dev (Java, Coldfusion, or whatever) and have the other worry about the Flex UI. This is one of the easier methods of keeping your client and server code somewhat decoupled, of course you still need to communicate and plan regarding the service interface.