What is Mate?

Mate is a tag-based, event-driven Flex framework.

Flex applications are event-driven. Mate framework has been created to make it easy to handle the events your Flex application creates. Mate allows you to define who is handling those events, whether data needs to be retrieved from the server, or other events need to be triggered.

In addition, Mate provides a mechanism for dependency injection to make it easy for the different parts of your application to get the data and objects they need.


Version 0.9 Released

Version 0.9 has been released. Thanks to Cliff Meyers and Nick Matelli for their contributions!

What's changed:

  • Added PropertyGetter tag
  • Added "useFault" property to MockRemoteObject: when true, any unhandled error in the mock service call will dispatch a fault; when false, error will be rethrown. Default behavior is useFault=true and is backwards compatible
  • Added support for localization (BabelFx framework)

360|Flex session posted

360|Flex has posted the latest session I gave in Washington DC. The session was called "Breaking down your application with Mate".

Unless you attended 360, you'll need to pay $2.5 to view it. Disclaimer: this is all managed by 360|Flex.

Virtual Panel: State of the Art in Enterprise Flex Frameworks

I was interviewed, along with other frameworks' contributors, by Dionysios Synodinos from InfoQ about developing enterprise applications with Flex.

You can read the full article at InfoQ.

Maven Repository

If you are building a Mate project with Maven, you can add the dependency as follows:

In the repositories section:


In the dependencies section:


As new versions of Mate are released, the maven folder will be updated to contain them, so you will just need to change the version on the dependency node.

Photo Gallery With Photo Caching

Pete Mackie has written a great tutorial on how to create a photo gallery on InsideRIA. It not only covers the basics, but also the use of the Presentation Model pattern. It uses PHP on the backend for those who always wonder how that part is done, but it should still apply to all backends that use remoting.