Comments on: Adobe, Please Bring Flash Builder Up To Par

By: bread_man

bread_man — Wed, 03 Nov 2010 20:14:39 +0000

Great post, thanks!

Adobe, just please implement code hinting like Flash Develop. Not only do I have to hit a period to get anything, I have to SLOW DOWN to wait for that hinting to appear. RAGE QUIT!

By: JTtheGeek

JTtheGeek — Wed, 27 Oct 2010 20:42:31 +0000

Jesse, just wanted to add some updated findings on this.

1) Amethyst, though extremely promising and fantastic, is currently only applicable for small-medium sized projects and still has some issues being ironed out. They are working on getting a updated release out within the next few weeks it appears.

2) SourceMate is a great addition, but really looking forward to version 2 (in beta/alpha) which should flesh out the rest of the things in flash develop that make life so much easier.

3) HellFire Compiler Daemon is the holy grail of Flex as far am I’m concerned now. It seperated the build process out of Flash Builder into a seperate JVM, which drastically improves Flash Builders responsiveness. It also compiles your app in GOD mode as far as I can tell… Reduced my compile times on Dedoose from 2-3 minutes down to 1.6 – 2.8 seconds.

Realistically Adobe should buy SourceMate and integrate it into Flash Builder, buy HellFire and use the absolute crap out of that. And if they really wanted to kick everyone’s ass partner or buy Amethyst and WebORB as well. In my eyes that would shore up the situation as a whole.

By: 360 Flex – Washington DC | Davey's Flash Blog

360 Flex – Washington DC | Davey's Flash Blog — Tue, 05 Oct 2010 14:01:33 +0000

[…] feeling I got from the speakers and attendees is that Flash Builder is not up to par (e.g. Jesse Warden’s rant) to comparable IDE’s for Java development or MS Visual Studio. However, Flash Builder 4 is […]

By: Flex Guy

Flex Guy — Fri, 24 Sep 2010 21:36:24 +0000

I use flashbuilder daily, and find it to be quite good, except for 2 glaring oversights compared to Java in eclipse.

1) The CTRL-1 key in Java (or hover-over an error) gives you an option to fix the error, either by creating a variable, field, etc. It seems something like this will be coming in Burrito.

2) Refactoring. Flashbuilder does NOT have refactoring. It has renaming. That’s it. A proper refactoring tool makes coding and unit-testing extremely easy. Just write your 40 lines of code, refactor it into 2 or 3 easily testable pieces, get the unit-tests written, and you have understandable tested code.

Please give us proper refactoring!!!

By: William

William — Fri, 24 Sep 2010 16:12:55 +0000

Funny…for me, all the problems you talk about are NOTHING compared to the new help system…
I’m used to the import system, I’m used to code hint….but I can’t work with a non working help which was put outside Eclipse….my alt & tab keys are very used :(

I can’t say how many times the “Help” gave me a wrong page (or no page at all)
I can’t say how many times the “Help” took +1minute to load
I can’t say how many times the “Help” asked me to upload the “local help”
I can’t say how many times the “Help” asked me to update the AIR runtime XXX then opened to the start page…and so I need to re-ask for help
it’s the less productive help I ever saw … with Microsoft tech help website

F1 is no longer a key I use…It’s easier to ask to google for help!