Flash CS5 和 Flash builder 4 之间的概念差异
Adobe Flash CS5 和 Flash Builder 4 之间有哪些概念差异？两者似乎对于创作启用 ActionScript 的互联网和桌面丰富的交互式应用程序同样有用。使用这两个工具时，除了UI在Flash Builder中以mxml表示之外，编程原理上有什么区别？
What are the conceptual differences between Adobe Flash CS5 and Flash Builder 4? Both seem to be equally useful for authoring actionscript enabled rich interactive apps both internet and desktop. What is the difference in principle of programming when using these two tools apart from that the UI is represented in Flash Builder in mxml?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
主要区别之一是目标用户。 Flash CS 传统上面向设计师，而 FlashBuilder 面向开发人员。
大多数人普遍认为 Flash CS 应该用于设计图形资源，而 FB 则用于这些资源的逻辑或编程。
人们普遍认为 Flash CS 作为 IDE 很糟糕，因此程序员倾向于使用其他选项，例如 FDT、FlashDevelop 或 Textmate 等等，但还有其他选项。
话虽如此，这两个平台提供的工具类型差异很大，最强大的选择之一就是使用这两种平台，当然这取决于您的项目类型。
例如，游戏开发将是一个理想的候选人。
至于mxml & FlashBuilder，请注意，这仅适用于使用 Flex 框架的情况。可以使用 FB 开发纯 Actionscript 项目，在这种情况下，您的 UI 设计可以在 Flash CS 中完成，并通过使用 SWC 将其引入 FB。
最后，Adobe极大地简化了使用这两个平台时的工作流程，虽然还不理想，但已经取得了进步。
One of the main difference is the target user. Flash CS is traditionally aimed at designers, whilst FlashBuilder is aimed at developers.
Most people generally agree that Flash CS should be used for designing graphic assets whilst FB would be use for the logic or programming of these assets.
It is generally accepted that Flash CS sucks as an IDE , so programmers tend to use other options such as FDT , FlashDevelop or Textmate to name a few, but there are other options.
This being said, the type of tools offered by both platforms differs greatly and one of the most powerful option is simply to use both, depending of course on your type of projects.
Game development for instance would be an ideal candidate.
As for mxml & FlashBuilder , please note that this only applies if you use the Flex framework. It is possible to develop pure Actionscript projects with FB, in which case your UI design could be done in Flash CS and brought into FB via the use of SWCs.
Finally , Adobe has greatly facilitated the workflow when using both platforms, it's not yet ideal but progress has been made.