On 1/15/06, Cameron Childress <[EMAIL PROTECTED]> wrote: > Seems to me that it's the same thing as referring directly to view > filenames rather than having a <views/> section and defining them > there, then using the name in the event.
Are you confusing Mach II (which has <view-page> and <page-view>) with Model-Glue (which has a <views> section that directly includes the view template - just like Fusebox does)? Moving your views around happens less often than refactoring your model code so the abstraction that Mach II provides is almost never needed (and is extremely annoying when you have lots of small views!). Model-Glue's message / listener separation is very different because it lets you add multiple listeners for a single message and as you build out your apps, you'll quickly find that you'll want different names for messages - to make event handlers easy to read - then you'll want for listener methods - to make controller code easy to read. That's especially true when you broadcast one message and have several different listeners (in different controllers) all acting on it... Does that help clarify? -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
