I worked on this project earlier this year, and I never found time to publish it. But since a month or two, I see that many questions arise on blogs and forums about PureMVC Pipes utility. I think that we need more examples of simple implementation of this utility. That is why I have added an example to the list for those whom wish to have a good start with this utility.
I've made this project for myself to understand the basic of Pipes. My needs were primarily to allow some modules to communicate among them, something that none of the examples I tested show.
You can view a live demo of the project, it has been published with ViewSource activated (on right-click menu).
Eclipse foundation recently have released Eclipse E4 Milestone 1 with the support of so called ActionScript development environment for SWT. It means that you can now export Java applications for the Flash Player. There is some pretty good instructions to run some demos. I've played with it last night. This post is intended to give you a quick overview of the whole thing with an ActionScript developer point of view.
The installation process is easy. You mainly have to download Eclipse SDK 3.5M4, install some updates, the Adobe Flex SDK 3 and configure the Eclipse environment. It takes less than an hour if you have a good connection and sufficient knowledge of what we are talking about. Just do not forget anything and cross your finger, as the E4/SWT team said: "[..] both the tools and the port are in the pre-alpha stage. You are living on the bleeding edge. Good luck!".
«Working sets» is an underused Flex Navigator functionality that could save you a lot of time when your Flex workspace contains many projects.
As its name says, it allows you to create sets of Flex projects to work on. The magic is that when a «working set» is selected, Flex navigator only shows projects related to this set. You could access all your classes and files in an instant.
It is not as cool as Java navigator filters (implemented in Flex navigator but not working) nor as Eclipse switching workspace that could share the same settings (not implemented yet), but it does its job when needed.
I will show you how to configure the whole thing.
Un petit tour sur le blog de Ted Patrick nous livre une information intéressante : la prochaine version du lecteur Flash 9 (nom de code FrogStar) allié à de nouvelles fonctionnalités d'export apportées par Flex 3 (nom de code Moxie) permettra de mettre en cache le jeu des composants Adobe utilisés par Flex. En clair, une fois que l'utilisateur aura téléchargé un des composants Flex sur un site (le votre ou un autre), il n'aura plus à le télécharger de nouveau lorsqu'un site (le votre ou un autre) en fera usage. À la place le lecteur Flash ira chercher la version correspondante dans son cache.