其中闪光/动作脚本IDE一起使用 - 如果要在所有使用？ [英] Which Flash/Actionscript IDE to use -- if one should be used at all?
问题描述
我一直使用内置的IDE，但我已经经历了从闪存以来的ActionScript 2.0在Flash MX ...我回来到Flash，我注意到有一些IDE的（有些的其成本比闪存升级）。所以......对Flash / ActionScript 3的开发问题 - IDE要使用的，如果在所有
I've always used the built-in IDE, but I've been gone from Flash since ActionScript 2.0 in Flash MX... I'm coming back to Flash, and I notice there's a number of IDE's (some of which cost more than the Flash upgrade). So... question for Flash/Actionscript 3 developers -- which IDE to use, if at all?
推荐答案
相传，绝对使用IDE为ActionScript。我们使用（我推荐）Flash Builder 4中。
Hands down, definitely use an IDE for ActionScript. We use (and I recommend) Flash Builder 4.
的ActionScript 2
在老版本的ActionScript（如Flash MX，你熟悉），一个IDE是不是很重要。你可以摆脱大多数编码在Flash开发环境。在那些日子里，最code的捆绑与创建主权财富基金的FLA文件。使用ActionScript 3，即改变了，因为不像AS2，ActionScript 3的是面向对象的，这使得所有的差异。
ActionScript 2
In older versions of ActionScript (like Flash MX that you're familiar with), an IDE was not as important. You could get away with most coding in the Flash Development Environment. In those days, most code was bundled with the FLA files that created the SWFs. With ActionScript 3, that changed because unlike AS2, ActionScript 3 is Object-Oriented and this makes all the difference.
的ActionScript 3
现在，最好的做法是，接零code在Flash中的FLA文件。所有code是现在外部的* .as文件，并分为包。这与其说是AS2的情况。如今，99％我创建Flash项目中包含内部的FLA文件零动作。唯一的例外是偶尔的动画控件（如stop（）或的gotoAndPlay（）），有时不时间轴以外意义。即使是那些，我拼命拉进* .as文件只要有可能。如今，code在FLA是一个迹象，你可能正在做的事情是错误的。
为什么要使用IDE？
这里有几个原因，我认为我们应该使用IDE为ActionScript：
ActionScript 3
Now, the best practice is to have next to zero code in Flash's FLA files. All code is now external in *.as files and broken into packages. This was not so much the case in AS2. Nowadays, 99% of the flash projects I create contain zero actionscript inside the FLA files. The exception is for occasional animation controls (like stop() or gotoAndPlay()) that sometimes don't make sense outside of the timeline. Even those, I try my hardest to pull into *.as files whenever possible. Today, code in a FLA is a sign you're probably doing something wrong.
Why Use An IDE?
Here are several reasons I believe one should use an IDE for ActionScript:
- 调试可能是＃1有理由使用IDE：通过code步进，因为它是在执行现场
- 更强变量输入
核心ActionScript语言并不要求你指定变量类型，返回类型等，它可以很容易地code错误，很难追查。一个IDE鼓励更强的类型通过突出显示code和显示警告时，类型不存在
- 更强的错误检查核心语言也在悄悄地忽略了严重的错误。只使用$ C在Flash MX $ C主编已经产生了过去，其中的根本原因只有一个错字一些痛苦的错误给我。相比Flash开发环境IDE将捕获远远更多的错误在编译时，使他们永远不要让它进入生产
- code完成 code完成是如此珍贵，我希望我能使用IDE只为这StackOverflow的帖子！ I型50X IDE中的要快，因为我经常用文字完成和扩大宏和模板
- 锅炉板code IDE的是伟大的做所有的垃圾，你不想做这样生成的getter / setter方法的字段，评论，骨架类等。
- API参考：当你输入一个方法，一个IDE会告诉你该方法的签名，所以你很少有咨询在线文档记住所有的属性和特定类的方法
- 插件与Subversion的集成是绝对必要的，以我们的开发过程。用的IDE插件的帮助管理这一过程给你。最重要的进程（如单元测试）是由IDE扩展，让生活更轻松的支持。
- 重构大多数IDE具有内置的，强大的重构工具，让你到C很容易和正确 更改您的$ C $
- 项目级$ C C管理$ 一个IDE，您可以从项目级别管理code使得它更易于管理的依赖，链接库，图像，资产，CSS，源code从其他项目等。它还有助于管理恼人的设置和preferences，很容易忘记像编译器设置，命令行参数，运行时配置等。
- 团队工作的IDE都设计在团队环境中运行，并且因为他们管理整个项目，他们能够更容易多个人工作，对同一套code。他们还鼓励公约，就像一个项目的目录结构，这有助于制定标准，为社会
- 对比和导航我用另一个特点的很多的是内置的差异/历史的工具，让我发现在code差异以及导航shortcts的让我直接跳到函数声明或搜索所有引用的函数
- 语法高亮最后但并非最不重要的，明显的IDE的好处，使code更无限脱脂能力和可管理的。我也鲠在这个其他的视觉功能，如code倒塌，行号，图标/警报在margians，错误/警告高亮等。
- Debugging Possibly the #1 reason to use an IDE: stepping through the code as it's executing live
- Stronger Variable Typing
The core actionscript language doesn't require you to specify variable types, return types, etc. It can be very easy to code bugs that are difficult to track down. An IDE encourages stronger typing by highlighting code and displaying warnings when types are absent
- Stronger Error Checking The core language also quietly ignores serious errors. Using only the code editor in Flash MX has generated some painful bugs for me in the past where the root cause was only a typo. The IDE as compared to the Flash Development Environment catches far more bugs at compile time so they don't ever make it into production
- Code Completion Code completion is so valuable, I wish I could use an IDE just for this StackOverflow post! I type 50X faster in an IDE because I'm constantly using word completion and expanding macros and templates
- Boiler Plate Code IDE's are great for doing all the crap you don't want to do like generating getters/setters for a field, comments, skeleton classes, etc.
- API References When you type a method, an IDE will show you the signature of that method so you rarely have to consult online documentation to remember all the properties and methods of a particular class
- Plugins Integration with Subversion is absolutely essential to our development process. IDEs manage this process for you with the help of plugins. Most essential processes (like unit testing) are supported by IDE extensions that make life easier.
- Refactoring Most IDEs have built in, powerful refactoring tools which allow you to change your code easily and correctly
- Project-Level Code Management an IDE lets you manage your code from the project level making it much easier to manage dependencies, link libraries, images, assets, css, source code from other projects and more. It also helps with managing annoying settings and preferences that are easy to forget like compiler settings, command line arguments, runtime configurations, etc.
- Team Work IDEs are designed to function in the team environment and since they manage your entire project, they make it much easier for multiple people to work on the same set of code. They also encourage conventions, like a project's directory structure, which helps set standards for the community
- Comparison and Navigation Another feature I use a lot is the built in diff/history tools that let me spot differences in code as well as navigation shortcts that let me jump to where a function is declared or search all references to a function
- Syntax Highlighting last but not least, one of the obvious IDE benefits that makes code infinitely more skim-able and manageable. I would also lump in with this other visual features like code collapsing, line numbers, icons/alerts in the margians, error/warning highlighting, etc.
这就是所有我能想到把我的头顶部，但我敢肯定，有数以百计的其他原因。
That's about all I can think of off the top of my head but I'm sure there are hundreds of other reasons.
哪个IDE使用？
如果您或您的公司有足够的资金时，Flash Builder 4手了。这是从Adobe的事实上的IDE和它的基于Eclipse的简化版本意味着许多成千上万的有用的Eclipse插件的工作，而无需修改（如Subclipse的），它是跨平台的。很多例子在线使用Flash Builder中，很难去不妥的地方发展。其中一个不太明显的本质特征是它的与BlazeDS的和Flex地面集成 - 两件事情你肯定会使用，因为你回来为ActionScript
If you or your company has the money, Flash Builder 4. Hands down. It is the defacto IDE from Adobe and it's based on a stripped-down version of Eclipse meaning many of the thousands of useful eclipse plugins work without modification (like Subclipse) and it's cross-platform. Many examples online use Flash Builder and it's hard to go wrong developing with it. One of the less obvious essential features is it's ground-level integration with BlazeDS and Flex--two things you're certainly going to use as you get back into ActionScript.
如果你的工作不买单，那么更具成本效益的解决方案存在。 FDT是Eclipse的开源解决方案。这是pretty的好，但它缺乏强大的套件的功能，在Flash Builder中，最引人注目的是能力，调试code，它在浏览器中运行。
If your job is not footing the bill, then more cost effective solutions exist. FDT is an open source solution for eclipse. It's pretty good but it lacks the robust suite of features in Flash Builder, most notably the ability to debug code that's running in the browser.
我希望这一切帮助以某种方式，
I hope all this helps in some way,
- gMale
--gMale
这篇关于其中闪光/动作脚本IDE一起使用 - 如果要在所有使用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
