Many thanks.

oops, didn’t mean to insult your controller :)

Why don’t you make a controller tied to the business you are trying to perform and have a map between and event string and a command. The reason I don’t like my view’s directly firing a command is sometimes my views get used over different applications, so the command that gets fired based on an event may change.

You could even throw up a controller on the fly when you create the particular view

controller = controllerFactory.getGetController();
controller.addCommand(‘login’, loginCommand);
controller.addCommand(‘changePassword’, changePasswordCommand);
view.addEventListener(controller);

I tend to have a few small controllers rather than one huge one. Plus in a real application most views don’t exist at compile time so you need a way to dynamically map events and commands.

One thing I’m doing and I’m still not sure its ‘honest’ is allowing my command to publish business events not ‘click’ but events like ‘UserRolesLoaded’;

For example: once the user has logged into my application I do a lot of preloading of data for performance, I want the user to take 1 hit after login to intialize the application. I have to load a lot of stuff and for example, I load all the possible roles a user can be assigned to (its a role based authorization administration system). So after they login my application dispatches a ‘getAllRoles’ event which is mapped to the GetAllRoles command, once this command has finished it dispatches a ‘UserRolesLoaded’ event. This issue I have here is I don’t really want my application as a ‘listener’ of the command, I actually want some ‘system events’ to be global so instead of my command
displatching the event my master controller does

e.g

SystemController.getInstance.dispatchEvent({type:’UserRolesLoaded’});

So now my applcation can do this :
SystemController.getInstance.addEventListener(‘UserRolesLoaded’, Delegetate.create(this, onRolesLoaded);

I hope this is clear but what I think I have is something loosely coupled but also not too heavy. The only issue I have now is my commands are sometimes invoked from a view and sometimes due to a system event so inside my command I have to check if viewref is null before doing anything as sometimes there may not be a viewRef.

I think I’ve got basically what you did with your ARP extensions I just didn’t find the view being tightly coupled to a command like your extensions would work for the type of projects I do where I do have a lot of view re-use but commands change often.

i took a very alike approach that you handle the whole app with one Application class (which contains many views), but i do have many view-controller pairs (usaually i see those pair as some kind of windows form) although they may be combined in one class (in flash).

I don’t think it’s wrong to ‘bend’ the approach since framework are there to help us get the things done, as long as it works. (personaly i have a very-heavily-bent-ARP-alike framework, with Application and Form template class doing all the underlying stuff, but what matters is that framework helped me to gain productivity by 2-5 times :-)