Is anyone really surprised about this? I think the writing was on the wall by last MAX if not before (Thermo = Flash Catalyst). But my bet was on "Flash Developer" or something similar, to appeal to the code monkeys. :-)

Calling the Flash IDE, "Flash Designer" would clear things up for new users and now with "Flash Developer" but at the same time Flex Builder has a capable designer and I would encourage it to continue to add designer features. In the end it doesn't matter. :P It's just a name and it will grow the way it is guided to grow.

I love the name change. I have been struggling with people treating Flex Builder like a totally alien experience, a big risky change, just because management tends to equate the tool with the framework. Better that they equate the tool with the other tools and the platform.

Maybe renaming the content authoring tool "Flash Designer" would help convince some stubborn folk to make the jump over to Builder. By making it sound more familiar.

I 'grew up' codewise with Flash authoring and then started to use FlashDevelop (open source editor for flash, flex, php, haxe etc) for productvity…but I still think of Flash authoring as a 'development' tool more than a design tool – simply because of the way I work with it. I suspect people in that category are outnumbered by 'flash designers' but I know others who consider themselves Flash developers more than designers who use Flash authoring as their primary tool.

Either way change happens, I guess they couldn't call it Flash Devigner, lol.

Flex Builder is a lot easier to sell to the Suit Monkeys than flash builder, they here the word flash and they think cartoons and animation. I will have to do some serious explaining when I put in a P.O for a new copy of Flash Builder 4 when I already have Flash 7,8,9…

I love the name change. I have been struggling with people treating Flex Builder like a totally alien experience, a big risky change, just because management tends to equate the tool with the framework. Better that they equate the tool with the other tools and the platform.

_____________________________________________

Alex B

<a href=”http://www.iwaayconsultant.com/” rel=”>www.iwaayconsultant.com</a>.

thi name change is good. as far as iam am fine with it i think there is no reason to worry on

http://www.iwaayconsultants.com

In my opinion, the name change is simply going to add to the already confused marketing coming out of Adobe. Which Flash is Flash? FlexFlash or FlashFlash? Sure, as developers we are all clear on the distinction, but I'm not looking forward to explaining it to managers and clients.

But whats worse than the name change is that the standalone FlashBuilder seems to be an even worse resource hog than the Eclipse based FlexBuilder or even the Dreamweaver based FlexBuilder.

This change name is geat.

I recently had the opportunity to write my first Eclipse plug-in as part of Tour de Flex for Adobe. We had a pretty short deadline for the project and I was a bit hesitant about entering the world of SWT and JFace without previous experience. I did have a good amount of experience coding in Java Swing/AWT previously, but it had been awhile and I had been coding UI’s in Flex/AIR with Java on the server side most recently. Moving back to this “widget-world” was certainly different! I discovered very quickly how spoiled I had been in the Flex/AIR world ;) I ran into a few kinks along the way in my development that I believe could have easily been avoided and saved me oodles of time had I been able to find some quick information on the web. So now that I have been through the painful task of figuring out how to code, build, package and test an Eclipse plug-in, I decided to write a series of posts to explain the steps I took in creating my plug-in as a sort of quick reference and cut to the chase, as I found myself sifting through a lot of information to find the nuggets I needed.

I love the change