Filed Under (AIR, Flex, RIA) by jonr on May-31-2009

The Flex 4 beta is out … confusing name changes and all.  InfoQ published my Top 10 Changes in Flex 4 article outlining the changes in the Flex 4 framework / platform.  Below is the top 10 categories.  Check out the full article for details.

  1. Integration with Adobe Catalyst
  2. Spark Component Architecture
  3. MXML 2009
  4. Improvements to View States
  5. FXG Support
  6. Skinning Enhancements
  7. Updated Layout Model
  8. Flash Builder 4
  9. Compiler Performance
  10. New Text Capabilities

Click here for the article.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (Drunk On Software) by jonr on May-31-2009

We have posted our latest episode of Drunk On Software: Flex Jam 2009 Wrap Up. Enjoy!

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (Flex, InfoQ.com, Java, RIA) by jonr on May-7-2009

This week, I posted an interview with Bruce Eckel on InfoQ.com.  Bruce is a legend in the Java community, who has moved on to working with Python and Flex.  When I first learned Java his book Thinking In Java was a huge help.  In the interview, he shares on a broad number of topics, including discussing his latest book, First Steps in Flex.

Check out the interview here: http://www.infoq.com/news/2009/05/bruce-eckel

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (AIR, Drunk On Software, Flex, Java) by jonr on May-5-2009

In our latest episode of drunk’n madness, we interview Adam Flater.  He is the founder of the Merapi project, which provides a bridge between AIR and Java on the client.  Check it out at: http://www.drunkonsoftware.com/2009/05/01/episode-12-adam-flater/.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (AIR, Flex, RIA) by jonr on May-1-2009

It appears that Flex Builder Linux is no longer being developed by Adobe.  I just finished the following post on InfoQ raising the issue: http://www.infoq.com/news/2009/05/flex-builder-linux-dead.

When you consider all of the steps Adobe has taken to court Java developers, who tend to care about open source, this seems like a really strange choice.  Why not just dedicate one or two resources to the project to keep up the perception that it is being worked on?  I doubt there would ever be much direct revenue for Adobe from Flex Builder Linux, but it does seem important in there overall strategy to court forward thinking developers.  I wonder if this is a direct result of the current economic situation, which is likely forcing Adobe (and most other software vendors) to put all there resource in areas with direct revenue.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (Flex, Java, RIA) by jonr on April-8-2009

This week Dzone posted a Refcard James Ward and I wrote on the new Spring BlazeDS Integration project (Download the Refcard here).  To go along with publishing the Refcard, Dzone’s

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (Drunk On Software, Java, RIA, Software Development) by jonr on April-6-2009

Our podcast of Booze and Bits continues in episode 11, where we do our usual thing – geek out on software over a few beers.  In this episode, we chat with Matt Raible about GWT, open source, RIA, etc.

Check out the episode here: http://www.drunkonsoftware.com/2009/04/05/episode-11-matt-raible/

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (AIR, Flex, InfoQ.com, Software Development) by jonr on March-30-2009

Today, I posted an interview I did with Doug McCune on InfoQ.com. His personality and passion for development came through in his encouragement for developers to build “cool shit.” I love the sentiment, as I so often get trapped in trying to bring business value and forget that sometimes software development should just be a creative endeavor. However, as cool as that sounds, it can be challenging to bring that sort of mindset into the enterprise. With that in mind, Doug had some really interesting comments on UX within business applications:

Enterprise software is almost uniformly horrible, but there’s no reason for that. We’re seeing a “UX revolution” in RIA design, and for all the buzzword nonsense surrounding “user experience, ” there’s something real happening in terms of the overall quality of the experience delivered by RIAs. We’ve seen some really great and innovative work in consumer RIAs, with a trend toward simple and intuitive interfaces. And yet in enterprise software this trend has barely even begun, it’s all still complex. I want to see enterprise applications treated like consumer apps, with the same attention to the user experience and with a consistent drive to simplify and make everything more intuitive. Complex systems don’t have to be presented with confusing software. But it takes more work to figure out the simple, elegant solution. It’s far cheaper and faster to make bad complex software than good simple software.

I also think there’s a business intelligence breakthrough afoot that will bring these same concepts of intuitive software specifically to the BI arena. Business intelligence is just a fancy way of saying that you’re extracting value from raw data in some way. This is typically limited to your mundane set of charts, gauges, and all the other normal dashboard UI elements that are the current standard. But I think thinking about BI problems from a fresh perspective, from the perspective of someone outside the enterprise space, will lead to the invention of new visualization methods. Maybe sales performance isn’t something best shown using a silly looking speedometer gauge. Maybe there’s an intuitive way to extract more value from that heap of raw data sitting on enterprise servers. But I don’t think enterprise developers have been willing enough to experiment with new concepts. People need to start inventing.

I have to agree that enterprise software is generally poor, particularly in the user interfaces.  In addition, his comments on working toward the simple, elegant solution makes me want to scream, “Yes!”  I think the only place I differ with him on is where the blame belongs for the overall low quality of enterprise systems.  Developers do deserve some of the blame, but I think generally the challenges come from the organizations, project owners, and managers who do not understand what is now possible, or even worse never understood how to build software to begin with.

In years gone by, the platforms really limited the ability of developers to build cool user interfaces that still made sense on the budget.  I was originally drawn to Flex because it can do things that simply weren’t possible on the web only a few short years ago.  This probably factors into the decisions that even smart, experienced managers are still making today, as many of them have previous attempts at doing cool things that led to ballooned budgets and jeopardized projects.

So, there is the obvious onus on developers to sell their ideas and educate their organizations on what is possible now that the platforms have capabilities way beyond getting data in and out of the database.  However, with that said, the real limitation of enterprise software will always be that the teams building most systems are part of companies that do not exist to build software, and often just don’t understand the processes, the platforms, the code, the users, etc.  In those cases, it is unlikely that they will be able to overcome their limitations to build cool, highly usable systems.  So, while I am optimistic that the advances that have come with the RIA revolution will trickle into the enterprise, it is unlikely that they will have the same impact on business applications as we are seeing in consumer applications built by companies that exist solely to build quality software.

If you enjoyed Doug in writing, check him out in this recent Flasher Magazine video interview. Also, look for him in a future DrunkOnSoftware.com interview.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (AIR, Drunk On Software, Flex, RIA, Software Development) by jonr on March-23-2009

In the latest installment of Drunk On Software, James Ward and I sit down with Anthony Franco, of EffectiveUI, to chat about RIAs and the software landscape in general.  Anthony offers a number of interesting insights for those that aspire to build quality software.  It was fun chatting with Anthony.  Hopefully it is enjoyable to watch.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn


Filed Under (ActionScript, Flex) by jonr on March-13-2009

When googling for solutions to any number of Flex challenges, I commonly find posts that include monkey patching as part of the solution.  Monkey patching is basically replacing a Flex class with your own.  For example, if you want to change something in UIComponent you can create a mx.core.UIComponent in your project, and the Flex compiler will use your class instead of the frameworks class.  So, basically you take the source code from the framework and modify it to meet your needs.

While it is interesting to have this option, its seems like a horrific idea to actually do this on a real enterprise project.  With this sort of solution upgrading the Flex SDK will be painful at best, and impossible at worst.  I think the only time I would ever do this is to get a bug fix into my code before it is available in a release, with the intent to throw away my class once the next release of the SDK is available.

From all the posts out there, it does appear this is a common thing to do in the Flex community.  So, am I missing something here, or is this as evil of an approach as it seems?

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn