Comments on: AS3 Framework Comparisons – Robotlegs

By: eco_bach

eco_bach — Mon, 19 Apr 2010 03:03:36 +0000

I’m excited about the potential of IOC dependency injection type frameworks like Robotlegs, but right now for maximum extensibility and code re-use, I think PureMVC still has the edge. I think it also boils down to which framework you’re comfortable with and whether the metadata-injection approach is easier to grasp.

By: Shaun

Shaun — Fri, 20 Nov 2009 18:06:12 +0000

Indeed. Luckily, with Robotlegs you don’t have to start with that kind of PureMVC-ish setup:

You can prototype in a Swiz-like fashion (ie injecting directly into your views, and using Controllers instead of Commands), and then move over to a more de-coupled approach as parts of your application settle down.

By: admin

admin — Fri, 20 Nov 2009 16:02:44 +0000

I agree with your assessment. Its not necessarily complexity, but the amount of classes you have to write, even if they’re simple, does have a burden on how quick it is to setup your project and get things going. I like commands … sometimes, and sometimes I prefer the simplicity of controllers. Thanks again Richard for the example!

By: Richard Lord

Richard Lord — Fri, 20 Nov 2009 07:51:28 +0000

The main cause of the difference is that PureMVC and Robotlegs (using it’s reference MVCS implementation) both require the use of mediators on your views – something you’ll want on large projects. The other frameworks don’t require any separation of display logic from mxml. Also, frameworks that use the command pattern (PureMVC, Cairngorm & Robotlegs) will naturally need more classes.

However, more classes doesn’t mean more complex if those classes are simpler.