![[image]](http://mowser.com/img?url=http%3A%2F%2Fwww.infoq.com%2Fstyles%2Fi%2Fqcon%2Fqcon4_image_4.jpg%3Bjsessionid%3D6DAEED158F79A6627E84150150AB8B66)
![[image]](http://mowser.com/img?url=http%3A%2F%2Fwww.infoq.com%2Fads%2FqconSF2008.jpg%3Bjsessionid%3D6DAEED158F79A6627E84150150AB8B66)
Agile in Practice: What Is Actually Going On Out There?
Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations.
News
Case Study: Applying Java Programming Skill to Flex
Posted by Moxie Zhang on Jan 24, 2008 12:41 AM
In an article published on Adobe Flex Developer Center, Bill Bejeck shares his experience creating components and enforcing separation of concerns with Flex, from a Java developer's perspective.
Bejeck's first impression when started using Flex was:
As a Java developer I was surprised at how familiar ActionScript 3.0 was, making the learning curve fairly flat. Once I started using Flex, it was great to see that I could use most, if not all, of the approaches to writing software that I was used to.
In the article Bejeck is trying to create components with a mixture of inheritance and composition, and enforce separation of concerns, especially between view and business logic. His Java application development skills come in handy. As he writes:
As an experienced Java web developer, I learned over time that a JSP page should be used only for presentation. All business logic should be in classes, and if you absolutely had to have code in your JSP page, you would wrap it up in a custom tag.
In Flex, ActionScript code can be included in a MXML file using tag, which is a similar feature of JSP page where Java code can be embedded. However, learned from working on other programming platform, Bejeck employes a practice called "code behind" where visual component is defined completely in ActionScript 3.0, and use MXML to decide how the components are visually rendered. Regarding this approach, Bejeck reminds the readers:
This is an architectural approach for building an application. If you are doing quick prototyping, there is no need to always use the "code behind" technique.
Then, Bejeck goes on describing the process in details, with code segments, on how he extended the Flex build-in visual components such as DataGrid, Panel, TextInput and Button to construct custom components and event handlers. At the end, a simple 8 lines of code MXML file is shown for rendering the UI and to demonstrate the clean UI design.
Bejeck concludes:
As you can see, by using the "code behind" approach, your code is very concise and maintainable. As you develop more complex applications, not only would you have a palate of components, but maintenance and changes to your applications would be very manageable.
Bejeck also recommends two books in the article to readers who are interested in learning more about programming in ActionScript 3. They are
Essential ActionScript 3.0 by Colin Moock Advanced ActionScript 3 with Design Patterns by Joey Lott and Danny Patterson
RelatedVendorContent
Evolutionary Design through Agile Development Podcast
The Agile Business Analyst: Skills and Techniques needed for Agile
The End of Middleware: Freedom from IT Stacks as we know it
JProbe Freeware – Eclipse Plugin for efficient memory analysis and diagnosis
I agree by Matt Giacomini Posted Jan 24, 2008 4:14 PM
As a Java developer that learned flex I agree with author, the learning curve was almost nothing. There are a few small thins that annoy me about Actionscript, but none of them affect my productivity, the maintainability of my code, or the quality of the final application. I think the author should also have mentioned the cairngorm framework for Flex. Cairngorm makes it easy for you to apply some of the most common design patterns in flex. From the point of view of a Java developer, used to using frameworks, it feels very natural.
1 comment
Reply