> What I mean is that it is unclear how you intend users of
> Cairngorm to take it out for a spin. Do I now stair at the
> included code for a while until I discover an entry point to
> hook into with a .mxml file I code up? Has that task been
> left as an exercise for the student ;-) or what?
Page 534.
You need to create an application, your application needs
to create a front controller, you need to register a command
with the front controller, and you need something (a button ?)
that broadcasts the event tied to that command.
There is also a sample application ships with the Cairngorm
ZIP file, in the samples directory - there you will find
Index.mxml that shows you what your MXML entry point should
look like, a com/ directory with all your actionscript code,
and a java/ directory with all your server side code.
Spend some time understanding how that 2 MXML file sample
application has been built, and how it interacts with the
files in the com.iterationtwo.cairngorm.* directory
structure.
In summary, the following code in Index.mxml:
<cairngorm:controller>
{ com.iterationtwo.demo.control.DemoControl }
</cairngorm:controller>
Creates a controller. Login.mxml has this code:
<mx:Button label="Login" click="doLogin()" />
It also (shriek) has some ActionScript 2.0 implementing that method:
public function doLogin()
{
EventBroadcaster.getInstance().broadcastEvent( "login" );
}
If you then view the source for com/iterationtwo/demo/control/DemoControl.as
you'll see how the "login" event is tied to the LoginCommand.as file.
You should be able to work the rest out from there.
Good luck,
Steven
