More Information on Next Version of Flex SDK

Today we’ve pushed a lot more information on the next version of the Flex SDK, code name Gumbo. If you check out the Gumbo page on the open source site you’ll find the following:

  • An updated overview on the themes of the release
  • A recorded presentation by Matt outlining the release
  • A whitepaper describing the updated component architecture
  • Specifications for a number of features

Additionally, we have pushed a whole bunch of source into the public repository. We had kept it private partly because it was using Flash Player 10 which we couldn’t talk about for a while, and partly because there was a huge amount of churn and we wanted to have the whitepaper and other presentations ready so that everything would make sense.

We hope you’ll peruse at your leisure and talk to us about it on the open source forums!

Note: the first nightly build using all the new stuff may not be available until tomorrow.

5 Responses to More Information on Next Version of Flex SDK

  1. Balaji says:

    When its gets released,, let me know[I don’t think we’re going to email you, but you should be able to stay up to date with posts on our blog here. – Mike]

  2. Matt says:

    There will be a final subset in the Gumbo release, and then there will subsequent releases that add more components in order to reach parity.

  3. Matthew Fabb says:

    In the Matt’s presentation he mentions that Flex 4 won’t have component parity and more complex components like DataGrid won’t be rebuilt using the new model until later.Does this mean this other components will be release in later nightly builds or beta releases of Flex 4, as it’s obviously still early in the development cycle? Or does this mean these other components won’t be in the final 4.0 release and will instead be included in either later Flex 4.x releases or Flex 5?

  4. Matt says:

    At this point almost all development is happening on the public branch. Believe me, it’s harder on us to have things private. The only time I’d anticipate a private branch is when we need to code against something that we can’t release (like we had to with Player 10 before it was in Beta).We are hoping that this approach is going to make everything additive on top of your Flex 3 knowledge, one approach we considered did have it starting over a little but we moved away from that.

  5. Wow, it looks like a *lot* of the new bits to support the funky bits of Player 10 are starting to land, and so become available to the public.Hopefully new development will be done on a public branch (or at least you’ll be able to say ‘we’re doing some private work on Feature X, hold on a bit’) ?There’s a *lot* to take in in the document, and the only thing that worries me is that a lot of existing knowledge and experience is going to be thrown away when Flex 4 comes out. Although I see that commitProperties() and friends are still present, and that Halo and Gumbo components can live side by side in a Flex 4 application, so at least incremental change (and learning !) is possible.