views:

3266

answers:

7

I want to play around a bit with FLASH for app development. I'm looking for a good IDE for that. Someone suggested Flash Develop.

+7  A: 

Major reason to use FlexBuilder: has a real debugger you can set breakpoints and single step and watch/edit variables.

Unless FlashDevelop has .. developed .. don't think it got any of that yet.

BTW - if you are a student/teacher FlexBuilder can be had for free

Scott Evernden
Agreed. Debugger is the make/break feature for an IDE.
Richard Szalay
The Debugger and the Design view makes Flex/Flash Builder awesome. I would definitely suggest it
Pieter van Niekerk
Flash Develop have fully featured debugger
Icaro
+1  A: 

Flex builder has a design view for MXML so you can build more visually. Flashdevelop on the other hand is free!

Iain
A: 

Along with what was already mentioned, Flex Builder has some nice tools that helps a developer to learn how to create a data enabled Flex application in form of the Data Wizards and also a nice web services introspection tool that automatically creates an ActionScript 3 client for a web service.

Remus Stratulat
A: 

I'm using the new Jetbrains IntelliJ 8, and it's great (especially if your used to java developement). Has a lot better XML/JavaScript editors that any other IDE.

The latest version of IntelliJ also has a good flex/javascript debugger.

Niels Bosma
A: 

Here are two objective contrasts between FlashDevelop (with the Flex 3 SDK) and FlexBuilder. First, only FlexBuilder includes AdvancedDataGrid. Second, FlashDevelop has no source control integration.

AdvancedDataGrid is not included in either the free or open source Flex 3 SDKs; if you want it, you have to buy FlexBuilder. (I assume it is probably possible to use it via another SDK if you possess FlexBuilder.)

FlashDevelop doesn't have any source control integration, FlexBuilder possesses the existing, stable source control options for Eclipse. This includes Subclipse for SVN, as well as a lot of other things. As a longtime Visual Studio and Emacs user, in FlashDevelop I'm beginning to feel unsatisfied with leaving the editor to check in.

Jesse Millikan
since the 3.3 version, FlashDevelop have SVN and GIT support added (requires TortoiseSVN or TortoiseGit, enable from settings)
Icaro
+7  A: 

Flexbuilder

Pros

  • easy debugging and profiling
  • automatic adding of imports and organizing of imports
  • visual designer for MXML
  • because of Eclipse: support for other languages (eg. with Aptana, PDT...) and usage of plug-ins for the Eclipse Platform with features not shipped with FlexBuilder (code snippets with CFEclipse "Dynamic Snippets", "auto-code" for getter/setters with Monkey scripts...)
  • class wizard
  • support for asdoc comments
  • support of virtual folders/files (links to external files/folders handled intern by Eclipse, so also working on Windows)
  • refactoring (renaming of classes, functions, properties with automatic changing of dependencies)

Cons

  • Commercial license
  • Big and because of Eclipse problematic with newer Eclipse versions for the FlexBuilder plug-in version (eg. not working with Eclipse Ganymede 3.4.1)
  • adding and configuring the missing features with Eclipse plug-ins needs time and searching in the Internet (which plug-in? settings etc.)
  • Code assist only average and sometimes buggy eg. if correct imports are missing ("java.lang.NullPointerException")
  • missing of a code formatter or automatic get/setters (but there are solutions with other Eclipse plugins like Monkey Scripts, CFeclipse, Flexformatter "FlexPrettyPrintCommand"...)
  • sometimes a bit sluggish if background tasks in Eclipse are working
  • no package explorer

FlashDevelop

Pros

  • free and OpenSource (developed with C#)
  • lightweight
  • best available Code Assist for AS
  • "auto code" for automatic getter/setter, variables, code for event handlers
  • code snippets with integrated editor
  • automatic adding of imports
  • extendible with plug-ins
  • support for asdoc comments
  • package explorer (show classes, symbols from a SWC file)

Cons

  • only for Windows
  • plug-in often not working in newer versions and many plug-ins are only rarely updated
  • only rudimentary debugging support (with a extra plug-in)
  • no visual designer for MXML
  • no class wizard
  • no code formatter
  • no support of virtual folders/files inside the project
  • no refactoring

For debugging, visual design of MXML and with some extra time to add other Eclipse plug-ins to get some missing features: FlexBuilder

For mostly coding of AS files under Windows: FlashDevelop.

devarni
+1  A: 

I've been using Flash Developer. Trying now FlashDevelop. FlashDevelop is fast and light, and I'm trying to switch just because of that.

I'm using HG + TortoiseHG for source control. I have 2 screens, so having external source control is not a big problem. Also the IDE stays a little cleaner by not having all the little source control icons.

DesignView helps with not having integrated design.

Also, I can debug with FlashDevelop and see the variables. I'm using FD3.2.1.

Artur Carvalho