By Jim Rapoza  |  Posted 2006-08-16 Print this article Print

In two-plus years its been around, Adobe Flex has undergone more than two and a half version releases, which has probably made developers who use the rich Internet platform feel as if they have been riding on a particularly unpredictable and gnarly wave. (And this doesnt even take into account Adobes acquisition in 2005 of Flex creator Macromedia.) eWEEK Labs review of the bare-boned and limited Flex 1.0 release showed that the application probably should have been a beta. The 1.5 release added stability to the platform, but it had all of the growing pains more typical of a 1.0 release. Despite these shortcomings, Flex has been attractive to developers, who appreciate its simple coding structures and data handling, its strong presentation layer and, most importantly, its tight association with the ubiquitous Flash format.
With the July release of Version 2, Flex looks like it may be finally gaining the maturity and stability it needs to become a major platform for creating powerful Web-enabled applications. However, theres a potential wipeout in store for some users: Developers hoping to leverage the new features will have to migrate their existing Flex applications to Version 2.
Platform shift Like nearly every product out today that has anything to do with building Web applications or Web services, the Flex Builder environment is now based on the Eclipse development platform. And eWEEK Labs tests show that Adobe has done a good job of integrating Flex Builder into Eclipse. Development of Flex applications is now easier than ever, and the ability to move between drag-and-drop design and pure code environments let us build each part of our applications in the best possible environment. For example, in the design view, we could drag and drop components to our application layout and quickly build the basic presentation for an application. In the coding view, all of the expected code assistants were available to help in directly editing application code, style sheet information and Flex-specific code, such as ActionScripts and Macromedia XML. Probably the biggest weakness of Flex Builder, which is priced at $499, is the fact that it runs only on Windows, which is rare among Adobe applications and especially surprising considering that Eclipse itself is cross-platform. The other main component of the Flex 2 platform is Flex Data Services, which basically replaces the Flex Presentation Server of previous Flex releases. Unlike Flex Builder, the Flex Data Services component is impressively cross-platform: It runs on Windows, Linux and Unix servers and works with most major Java application servers. Adobe bridges Flash and Flex with AJAX (Asynchronous JavaScript and XML). Click here to read more. Flex Data Services has some basic monitoring and administration tools (created in Flex) that are available from a browser. For the most part, however, Flex Data Services exists mainly to deploy and run Flex applications and add enterprise-level data integration and connectivity. Most of the new capabilities of Flex Data Services deal with better data management and integration. One interesting addition is that it is now possible to build real-time collaboration applications within Flex. Using this feature, we were able to create applications that would let users see changes live, as a colleague made them. Flex Data Services is priced starting at $20,000 per processor; a free developer version, Flex Data Services Express, is also available. Theres no doubt that the tools within Flex Builder and Flex Data Services make creating Flex applications easier and make the applications themselves more enterprise-capable, but it is possible to get started creating Flex applications without having to shell out a dime for these components. The freely available Flex SDK includes all of the compilers, debuggers and code necessary to create Flex applications, and it can now also be used to create stand-alone, serverless Flex applications. The Flex SDK for Version 2, which is available here on Adobes Web site, also includes many new components and improved themes and templates for application creation. We should note that while creating Flex applications will be familiar work for anyone used to building Web applications and Web services, there is still a decent layer of complexity for newcomers. We found the Flex Developer Center to be extremely useful for finding samples, walk-throughs and other aids for navigating the complexities of Flex development. Next page: Evaluation Shortlist: Related Products.

Jim Rapoza, Chief Technology Analyst, eWEEK.For nearly fifteen years, Jim Rapoza has evaluated products and technologies in almost every technology category for eWEEK. Mr RapozaÔÇÖs current technology focus is on all categories of emerging information technology though he continues to focus on core technology areas that include: content management systems, portal applications, Web publishing tools and security. Mr. Rapoza has coordinated several evaluations at enterprise organizations, including USA Today and The Prudential, to measure the capability of products and services under real-world conditions and against real-world criteria. Jim Rapoza's award-winning weekly column, Tech Directions, delves into all areas of technologies and the challenges of managing and deploying technology today.

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel