Flex My Day - David Deraedt's Flex Architecture Playground

I'm not giving up just yet ! ;) If you've read my previous posts about the Presentation Model pattern, you know that I ran into some difficulties when trying to develop an decent implementation of this pattern. Since then, I had the occasion to validate the various advantages offered by the Presentation Model pattern in real life applications (namely, a separate object hierarchy allows to share common presentation behavior much better than the autonomous views, facilitates separation of concerns, testing, etc...). Also after reading some recent posts about Flex architecture GUI patterns, like Jesse Warden's (be sure to read the comments), I definitely think that the Presentation Model pattern needs more attention.

These last few days, I spent some time playing around with the Get Satisfaction API. I liked it so much that I decided to create an open source flex library for it.

If you haven't heard of Get Satisfaction yet, then go ahead and take a look at their website. It's a centralized crowd sourced costumer service for any product of any company. The service is both interesting and very well executed.

Their API is a REST API, which allows developers to make pretty basic but yet useful read and write queries such as getting the list of companies registered with their service, accessing the replies for topic about a particular product, post a response, etc...

Following the sample application source code we've discussed in the second part of this series, I'd like to take a moment to talk about some issues that were raised during that implementation of the Presentation Model pattern in a Cairngorm application.

In the first part of this series, we've shortly discussed the reasons why we may need a separate presentation layer for applications, and what pattern we'll use for this : the Presentation Model pattern.

There's been a lot of discussions lately about the various GUI patterns and their implementations by Flex architecture frameworks, Cairngorm and PureMVC in particular.

I think that this topic is absolutely essential to cairngorm since this framework has often been criticized (including by me) for its lack of proper mechanism for managing the presentation layer.

After O'Reilly France had closed its doors some weeks ago, I was informed that I now owned all copyrights regarding the french translations of the following pocketguides :

• Apollo for Flex developers
• Apollo for JavaScript developers

I also own my original work Bien démarrer avec AIR Beta 1. Unfortunately, for some reason, Colin Moock's essential as3 does not seem to be concerned.

As a consequence I'm releasing these original PDFs as free downloads.

• • AIR
  • O'Reilly
  • Pocketguides
  • Translation
  • Add new comment
  • Read more
  • 373 reads
  • 3 attachments

After lots of delays (and headaches), I've finally released the v 1.0 and the source code of FCG, my Flex code generator.

Note : Beta users will have to manually upgrade to v 1.0 by reinstalling the AIR file from the project's page, as the update mechanism has switched to the official Adobe AIR update framework.

As promised, here are the powerpoint presentations for the two Adobe eSeminar I just gave at Adobe France.

Reminder : these are in french, folks !

Hope you find it useful...

***

Comme promis, voici les présentations powerpoint des deux eSeminars que j'ai donné récemment chez Adobe France.

J'espère qu'elles sauront vous être utiles...

Hi all ;)

I just got back from San Francisco where I've had a great time. This city is fantastic. I really wish I didn't have to leave, actually.

Back in France, I'll be giving another eSeminar for Adobe on internationalisation in Flex application, next Friday, called Les stratégies de localisation d'une application Flex.

We'll talk about all sorts of things concerning translation and how to prepare your Flex / AIR apps for it.

You can sign up here to attend the seminar.

I'll be in San Francisco from June 13th till June 22nd. Just in case you're wondering, this is not a business trip, and I have no plan to move there (yet ;) ).

However, if you'd like to meet me there, feel free to contact me via my contact page.