The most powerful system for developing Flash applications in the environment MXML and AS2/AS3 (ActionScript2.0/3.0) programming. The real alternative to Adobe Flex Builder 3 and currently exceeds the product of Adobe Systems Incorporated for their custom and functionality.

Powerflasher FDT Enterprise (Flash Development Tool) is working closely with the Eclipse environment, which turns into a powerful Flash, ActionScript and MXML code editor with advanced features such as Live Error Highlighting.

Eclipse - an extensible development environment (Integrated Development Environment) open source (OpenSource). The project was launched in November 2001, when IBM donated the source code of its Websphere Studio Workbench $ 40 million worth of OpenSource and Eclipse has formed a consortium to manage the continued development.

In Powerflasher FDT Enterprise (Flash Development Tool) is everything that happens in any serious IDE: Project Manager, a wizard to create classes and interfaces, refactoring, search for projects, bookmarks, integration with version control systems and so on. In part, this functionality is provided by Eclipse. But Eclipse does not know anything about ActionScript, so all that is associated with the specific language is provided Powerflasher FDT Enterprise (Flash Development Tool). Most of this is functional and in FlexBuilder (which is also nothing but a plug-in for Eclipse), but not all. FDT has several important functions that are lacking in FlexBuilder.

1) parsing code on the fly. FDT has its own interpreter, which analyzes the code on the fly and immediately highlights the error: undefined variables and methods, incorrect data types in function parameters, the wrong type of return value, unknown class names, etc. All this is set very flexible and helps with two things: to maintain a good style of programming and boldly go to the refactoring. In Flex Builder also has a function, but it is weaker on the capabilities and does not work on the fly, but only after you save the file. Besides parser Flex Buildera checks only those classes that are included in the project. That is, creating a new class and threw a dozen lines of code, you will not see any bugs in the code until you create an instance of this class somewhere in the code of the project.
2) Quick Fix - the perfect addition to the parser code. FDT is not only highlights the error, but also offers options for correction of the mistake: to import a class, create a class, add a property or method in the class, etc.
3) Code Templates - in Eclipse, they are powerful, as nowhere else. The templates you can use variables, own or built, with special values (cursor position, name of the current class name of the current method, etc.). It is surprising that in FlexBuilder no such patterns. This is, perhaps, his main drawback, which I could not accept because he was already accustomed to their patterns, used unconsciously, to automaticity.