Patrick McElhaney wrote: > I think the latter implementation would handicap you from understanding > the true power of MVC. For example, this is how I might implement a > shopping cart in MVC. > > parent > model > products > orders > view > catalog > cart > checkout > orderstatus > controller > shopper
Patrick, I think I see what you are saying. But where in this example would you handle the adding/changing quantity/remove functions of the shopping cart? Add another folder under model to handle that? > There are no one-to-one-to-one relationships between the model, > view and controller circuits. Instead they all work together to > form the application. > > > My second question is, did anyone ever find a way around having to > > reference queries and result sets using "caller.myquery" and in the > > output using "caller.myquery.productid"? Or is this just a > > side effect of the MVC setup and it must be that way? > Pass the query into the circuit as an attribute. > > <cfmodule > template="#fusebox.rootpath##self# > fuseaction="catalog.showItems" > items="#attributes.items#"> Not sure I understand what you mean here...wouldn't the items attribute of the cfmodule have to be something like: items="#caller.myqueryname#"? Thanks for the clarification on the MVC structure. --- ==^================================================================ 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 ==^================================================================
