DIGG IT!
Published
Wednesday, December 12, 2007
at
12:42 PM
.
Today we pushed out some very important releases for AIR, Flex and open sourced some key data exchange technogy in Blaze DS and the AMF Specification. This release is a really big deal and will change the face of data exchange for Flash/Flex based technologies. Here is my take:
AMF3 SpecificationToday we released the specification for the Action Message Format (AMF) version 3 in pdf. This is the first time that an AMF specification has been available and will help developers integrate binary data exchange into all server platforms. AMF is the foundational data format within all remoting and messaging technologies providing fast serilization/deserialization in Flash Player using flash.utils.ByteArray.readObject and flash.utils.ByteArray.writeObject. The release of this specification will improve the quality of all remoting and messaging solutions for Flash/Flex and usher in a new era of optimized data exchange.
Blaze DS - Free LGPL Remoting and Messaging for JavaToday we released a new java solution providing a reference implementation of remoting and messaging. Blaze DS provides a 100% free and OSS solution for optimized data exchange using Java. This release not only includes support for remoting using AMF but also supports long poll messaging over http on port 80. Blaze DS bridges a gap in the LiveCycle DS product line in providing a free and open source solution for exchanging data with Flex. Blaze DS also contains a full AMF3 reference implementation for remoting and messaging in Java easily portable to any server-side platform.
Flex 3 Beta 3Today we released new beta builds of Flex 3 SDK and Flex 3 Builder. Having tested this release over the last 2 months, the quality has moved forward 10 fold since Flex 3 Beta 2. I am using this release for all Flex development moving forward and this release marks my shift over to using Flex 3 full time for all future projects. It is a great release for Flex and marks a maturing of the Flex product line for application development. This release is also the final release before we ship in 2008.
AIR Beta 3Time to write some desktop applications! This release of AIR marks the lock down of the AIR APIS and for me signals the start of major project development for AIR. I have long been frustrated migrating AIR applications from version to version as the API's migrated in design. As the API's in AIR Beta 3 are at near lock-down status, it is time to invest in AIR development. I have personally had 3 projects on hold until AIR locked down its development API's and now it is time to start development. I expect we will see a great number of AIR applications start development on AIR Beta 3 as it is near release quality and migration to the final release will be 99% trouble-free.
Sorry for the delay in the post!
Cheers,
Ted :)
I can't install AIR Runtime Beta 3 on mac: There are no mountable file systems in dmg package! (Seems it is a broken file on server)
I can't input my Flex 2 Serials into current Flex 3 release (previous works good).
There is still exist "Flex Chart Trial" water-massage if I'm compiling Flex 2 App under Flex 3 Builder.
Well, by definition it's a beta, not intended for production development. So the watermark on Flex charting components isn't really an issue, is it ;) ?
Oh, your mighty...
I'm going to have one Flex Builder, not two. And as I can see it's Adobe politic too, cause they give us ability to select SDK version.
Anyway, If you don't know, this is an old bug, and I was hopping that in next milestone it will be fixed.
https://bugs.adobe.com/jira/browse/FLEXDMV-1301
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=651&threadid=1276475&enterthread=y
Can't find any info online about expiration time on beta 3. Is it going to expire before the final comes out?
What happened to the Enhanced Constraints in beta 3 It's not there anymore. Also I got around the AIR beta for mac download by dl it on my pc and saved the file back to osx worked fine.
http://labs.adobe.com/technologies/flex/faq.pdf
Check harder
A quick question about keep-Metatdata flag on the compiler. Shouldn't it be set to true (or a general keep all) by default. People will only add metadata if they want it available in 99.9999% of cases, which begs the question why should you have to add the flag for the majority of use cases. If you are worried about the amount of metadata from the mx namespace (internal flex metadata) can't you exclude that by default?
Loving FB3 so well done guys :)
I tried to develop an air app in fb3 but it won't run when i run or debug from fb3. i can only get my apps to run by installing them. am i hitting F11 the wrong way, or is something wrong with my fb3?
The AMF3 documentation released cites the AMF0 documentation in its end notes. Will the AMF0 documentation be made available as well?
Hello Ted,
I'm considering migrating from flex 2 toward Flex 3 beta.
I've been playing with it for a while and found many features to be valuable.
When I installed the new beta 3, I was alerted to install a an up-to-date flash player version.
The version I had was flash player version 9.xx470.
I read a blog post of yours about the ability of flex 3 apps to be deployed under any version of flash player 9.
Is that still valid true ?
Thanks in advance,
Almog Kurtser
WHEN will Flex3 be available for purchase?