Any listener registered in the mach-ii system can act as a "controller" in the sense you are describing because of their ability to announceEvents.
Right, but bear in mind that a listener is only passed the current event and can only announce new events - it can't clear the event queue and it can't abort the current event handler, both of which are important for a controller. That's why a filter is more appropriate - it gets the event context so it can manipulate the event queue and even abort the current event handler. Event filters are the if-then-else of Mach II :)
Someone commented on the mach-ii list to think of listeners as the wiring (and therefore sometimes the logical switching mechanism) between the model (the application's cfcs) and the controller (the XML).
Yes, that part is accurate.
I suppose that gives you the freedom to structure your app in a variety of ways,
Yes, the talk I'm am going around giving at the moment (SCCFUG conference next week, MXDU later, CFUN-04 in June and a variety of user groups) talks about "many ways to skin a cat".
Implicit invocation is a bit of a different world from the pipe and filter stuff of
switch / case statements. It doesn't have as much of a "central nervous system". i'm still getting used to it.
Yes, it's a big shift for anyone who has not built desktop apps using an event model but it brings a lot of flexibility and makes restructuring and enhancing applications much, much easier down the line...
Regards, Sean
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
