shaun smith

Warning: The style of architecture demonstrated in this video is not sexy. Nor is it in any way recommended. Also, I cheat by eating plenty copy-pasta, and I say “um” a LOT.

I’m still trying to figure about the best way to illustrate the simplicity and flexibility of the Robotlegs framework. In the meantime however, I thought I’d respond to this cool Swiz video by doing the same thing with Robotlegs – except ending up with a modular (as opposed to a static) app, and throwing in some git/GitHub love as a bonus.

I don’t have a nice mic, so I strapped a phone to the side of my head and left myself a really long voicemail. Anyhoo:

You can grab the (terrible) source over at:

http://github.com/darscan/SillyStockPriceExample

Help make RobotLegs the cleanest, smallest, most testable, and most kick-ass framework for Flash and Flex ever built – join the discussion group:

http://groups.google.com/group/robotlegs/topics

Or help fill up the Robotlegs Knowledgebase:

http://knowledge.robotlegs.org/

I’ve just started looking into Parsley: http://www.spicefactory.org/parsley/

First thought: version 2 is exactly what I’ve been trying to build with RobotLegs. Read more…

I’ve added a little page to the RobotLegs Wiki: RobotLegs Overview

RobotLegs AS3 is a Dependency Injection Driven MVCS Framework for Flash and Flex inspired by PureMVC.

Actors may be dependent on actors below them in the diagram, but should not be dependent on anything above them.

Commands, Services and Proxies may dispatch system events, but should never listen for them.

Mediators may both dispatch and listen for system events. Read more…

Constructor injection is theoretically superior:

Constructor Injection vs Setter Injection
Constructor vs Setter Injection – Constructor is Better
Setter injection versus constructor injection and the use of required

Before I built RobotLegs I was sold on constructor injection. My prototype, however, used SmartyPants-IOC which lacked constructor injection, so I bit my lip and used setter injection. In practice I found that often, especially with framework actors, it was incredibly convenient. Read more…

The State Of The Game

There are some great Flash and Flex application frameworks out there right now. Mate, Swiz and PureMVC (update: and Parsley!) stand out. The authors of these frameworks realized that the Flash Platform is different enough to the JVM to warrant a fresh approach to application design.

Read more…

Want a framework like PureMVC but without Singletons, Service Locators, or casting? Perhaps one with Dependency Injection and Automatic Mediator Registration?

Well, you might enjoy RobotLegs AS3: yet another lightweight micro-architecture for Rich Internet Applications.

Read more…

Warning: This is long and probably VERY boring.. unless you are an AS3 junkie, and you’re interested in so called “lightweight micro-architectural frameworks” for Flash and Flex.

A couple of weeks ago I played around with Mate and Swiz. I already knew a little about Dependency Injection (in theory anyway), but playing with those two frameworks really drove the point home: applications are potentially MUCH easier to write, and much more flexible, when you take advantage of Dependency Injection. Read more…

I’ve been using PureMVC for my Flash/Flex applications for quite a while now, and have generally found it to work quite well. Besides the obviously annoying abundance of boiler-plate code, it does a decent job of separating concerns, and has helped me to build better applications.

Lately, however, I’ve been building an application for which PureMVC has turned out to be a pretty poor fit. The term that some people have used to describe this kind of application is “Document-Based”.

Read more…