ActionScript 3.0, Adobe Flex

MATE CacheSetter.. a quick and dirty introduction

One of the newer classes in the MATE Flex Framework yet to be documented is the CacheSetter.
It’s nothing overly fancy, but it does exactly what it promises… it allows you to set the Cache from an ActionTag.

Let’s examine the code below… it’s a standard MATE EventMap with a couple of eventhandlers which offers to exit an AIR application when the User clicks anywhere on it… the applications for such a feature might be quite limited, but that’s what I could think of at 4:40 AM in Bangkok after almost 2 hours of being teleconferencing with the Flex Team sitting in California and it proves the point with the CacheSetter close to a minimal implementation.







For the sake of completion, I will also bring the code to the AIR application itself…




One of the more interesting and intricate details (and eventually why this exercise is interesting), is to see that it uses the Class reference as the cacheKey and that you eventually would be able to use any class or hashable object and chain as the cacheKey. If the cacheKey is NOT set explicitly it will default to use the class type of the Generator attribute, but if you are working with MATE the Cache class is one of the classes it makes the most sense to take an extra look at…

CacheSetter (Source)

Cache (Source)

Cache (Documentation

ActionScript 3.0

ActionScript API for Adobe Wave Service

While I was experimenting with the new Adobe Wave Service from Adobe… I decided to take some of the experimental code and create a reusable library.
It has a basic implementation handling authentication as well as broadcasting notifications.


I have named the project “asadobewave” which roughly stands for ActionScript Adobe Wave and I have made it available via the Google Code under the Mozilla license.

Check it out…

It has been moved to here…

ActionScript 3.0

Introducing Axiis… Open Source Data Visualization

Up to this point there has been only four more or less serious alternatives when it came to employing advanced Data Visualization in your Flex Apps, but not with Axiis another alternative has emerged.

Up to ths point we could either…

  1. Use the data visualization library native to the Flex SDK.
  2. Use Ilog Elixir.
  3. Use on of the the more or less unserious smaller contributions available out there typically limited to a single visualization.
  4. Write it ourselves.

Axiis, the 5. option now available, is an open source data visualization framework designed for beginner and expert developers alike.
Whether you are building elegant charts for executive briefings or exploring the boundaries of advanced data visualization research, Axiis has something for you.
Axiis provides both pre-built visualization components as well as abstract layout patterns and rendering classes that allow you to create your own unique visualizations.
Axiis is built upon the Degrafa graphics framework and Adobe Flex 3…


Check it out…

…thx to the always well informed Paw Suddergaard for initially pointing me to this great contribution to the preferred library of open source projects…

ActionScript 3.0, Adobe Flex

Introducing HydraMVC…

HydraMVC is one of the most recent newcomers to the scene of Application Frameworks and Architecture Blocks for Flex Applications.
Its definitely something I’m going to check out in parallel to my love affair with the Mate Flex Framework.


HydraMVC is the result of a total rewrite of the PureMVC API exclusively for Flex, allowing Flex developers to take advantage of the PureMVC paradigm while leveraging native Flex features.

In addition to using Events vs. an independent Observer pattern, HydraMVC also streamlines implementation, encapsulating much of the initialization code that needed to be written when implementing PureMVC.

HydraMVC was written out of a love / hate relationship with PureMVC; it’s not our intent to say it’s “better” than PureMVC, because the mission of the frameworks are entirely different. PureMVC intends to be language-agnostic, where HydraMVC is a compromise by design.

While HydraMVC is an MVC framework, the demos also imply a strategy for package structure, although the implementation of HydraMVC will work regardless of whatever package structure convention you use. The goal was to create a structure that scales well for large applications, but it also allows you to quickly develop small applications in a proper MVC.

ActionScript 3.0, Adobe Flex, Tools

FC / FB Workflow Optimizer… sources available

I have made the sources available for the Workflow Optimizer… its a crude implementation but it does the job.
It uses Flex, AIR, as3preferenceslib, as3corelib and the Mate Flex Framework.

Don’t hesitate to comment on the ideas or concepts.. but don’t comment the code: it’s not written with any other priority than functionality…

Check it out…

ActionScript 3.0, Tools

Flash Catalyst / Flash Builder Workflow Optimizer

Workflow Optimizer is a small and lightweight tool which helps Flash Designers and Flash Developers to work around some of the temporary limitations with Flash Catalyst.


The application allows you to automatically extract the contents of FXP / FXPL files and put them into a configurable directory and can hence replace some of the tedious export / import actions from Flash Catalyst to Flash Builder.

The application is written in Flash Builder 4 with Flex 4 and AIR, it uses the as3preferenceslib for persisting the directory and file information and it uses Mate Flex Framework as the application controller.

Next step is to add support for running as a service by adding some Merapi classes and examine even better ways to help optimize the FC / FB workflow.

You can download and install the latest version from the Adobe AIR Marketplace here…

Sources are available at Google Code…

You can download the binary from here…

Sources will soon follow…

ActionScript 3.0

Mate… Lightweight Schedule Extension

Some time ago I was in need of something to be run at regular intervals.
Among the many implementations I already had in my framework, I thought that including either my Workflow package (An ActionScript port of the Windows Workflow Foundation 3) or my processing package (eventually just a scheduling application block which allows processes to be managed Windows Service style.

I wanted something much more lightweight, so I decided to implement a Schedule Handler.
It extends the AbstractHandlers class, so all I had to do was initiate a timer and then run the sequence when the timer elapsed… more lightweight then that is hard to imagine.

package org.hellogroup.mate.actionLists
	import com.asfusion.mate.actionLists.AbstractHandlers;
	import com.asfusion.mate.actionLists.Scope;

	import flash.utils.Timer;

	public class Schedule extends AbstractHandlers
		private var timer:Timer = null;

		public function Schedule()

			this.timer = new Timer( 1000 );
			this.timer.addEventListener( TimerEvent.TIMER, this.handleTimer );

		public function get delay() : Number
			return timer.delay;

		public function set delay( value:Number ) : void
			this.timer.delay = value;

		override public function initialized( document:Object, id:String ) : void
			super.initialized( document, id );


		private function handleTimer( event:TimerEvent ) : void
			this.runSequence( new Scope( event, true, ), this.actions );

The class is included in the downloads in my previous post…