XFAs in the view circuits always go to controller circuits. In anything but a tiny application, my controller circuits mirror my view circuits, eliminating the issue of one huge controller circuit, just as you thought, Balzas.
-----Original Message----- From: Balazs Wellisch [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 30, 2002 2:44 AM To: [EMAIL PROTECTED] Subject: RE: MVC True, but MVC with fusebox, as far as I know, is Hal's. Anyway, the point is I'd like to see a more extensive example of how the controller circuit is constructed. Hal's paper explains the concept very well, but I still would like to see a more complete "real world" example if there's one out there. I'd like to know if XFAs in the view circuits are allowed to call fuseactions in model circuits directly, or are they supposed to always go through the controller circuit. If so, wouldn't that quickly bloat the controller circuit for larger applications? Instead of having this giant controller could I break it up into several smaller controllers? I'm sure I'll have a bunch of other questions, but it's getting late... Balazs -----Original Message----- From: Neil Clark - =TMM= [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 11:06 PM To: [EMAIL PROTECTED] Subject: RE: MVC MVC as a concept is not 'Hals' :-) it's a standard OOP design tactic..... -----Original Message----- From: Balazs Wellisch [mailto:[EMAIL PROTECTED]] Sent: 30 May 2002 06:52 To: Fusebox@Topica. Com Subject: MVC Does anyone know where I could get my hands on an example application using Hal's MVC design? Thanks, Balazs ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
