Flex Builder is having an identity crisis

Not one to start rumours, but this comment from Lee Brimolow over at Keith Peters blog seems to suggest (or my reading between the lines is shocking) that there will be a revised naming strategy for the upcoming release of Flex Builder (currently code named Gumbo).

Anyone want to have a stab at what it could be?

We have Flash CS4 and Flash Catalyst – what’s going to be the third arm of the axis of fevil?

If it was to change, there’s going to be a lot of rebranding to do that’s for sure!

(obviously Lee’s comments are completely unsubstantiated at this time – though the post he commented on did have a few contributions regarding the inconsistency of the Flex name and how it relates to the Flash Universe Platform.)

Edit: Looks like Ryan Stewart has poo poo’d the idea of any Flex name changes.

Please follow and like us:

5 thoughts on “Flex Builder is having an identity crisis”

  1. Flash Designer, Flash Catalyst & Flash Developer would do me, all targeting the Flash Player, all part of the Flash Platform.

    They could then release Flash Suite.

  2. As someone who migrates between quite large AS3 applications some built in Flash and some in Flex there are a number of workflow issues that the model as it stands fails to address.

    There is no roundtrip between Flash Professional and Flash Catalyst as yet.
    The code editor is Flash Professional is the bain of my life, hence I have been using FDT for the last 3 years ( FlashDevelop in some cases) or Flex builder.

    Some of this split comes down to the fact that AS3 was not ready in time for Flash 8 as originally planned.

    No development effort has gone into the improvement of Flash Pro code editor for the last 3 years, so for those of us who have to maintain legacy systems the process is like pulling teeth. (I have to be dragged kicking and screaming from my FDT or Flex builder goodness)

    The mental gymnastics of jumping around the different workflows is sending me grey. ;0)

    There is not a good single solution for documenting both AS2 and AS3 that works seamlessly.

    Now before I get a deluge of posts telling me I am wrong and that ASdocs is flawless, trust me I have last week managed to blow it and get some of the most obtuse error messages I have ever seen.

    There is therefore a good case for a number of new tools in Flash Pro a better code editor, a built in documentation generator, the ability to save FXG and FXL roundtriping to Catalyst, and a command line Flash compiler that will load FLA’s and its variants so that you can build large non Flex based projects which have dependencies as part of an automated build, and output updated docs via Ant, Maven or Patchpanel

    I know we have elements of this via JFSL but its far from perfect and now is the right time for the Flash community to start raising the bar on what we what to see in Flash as new tooling is being built. If we don’t raise these issues now Flash Pro will become the beggar at the feast.

    Max San francisco was awesome by the way

  3. @Stephen – thanks for the comments. And I whole heartedly agree, the Flash IDE action editor is a pile of crap. I know also refuse to code in it, instead going from FlashDevelop to the IDE for graphics and the odd timeline change and then back to FlashDevelop. I actually completed this project using that type of workflow – http://programs.sbs.com.au/mygeneration/

    Obviously my preference would be to have all of the FlashDevelop goodness (or Flex Builder for that matter) right in the Flash IDE where it belongs.

    So come on Adobe, please integrate an industry best action editor in CS5!


Leave a Comment