My understanding is your model is a model of the application data, and the data resulting from a call to an event is rendered in place of the view. The controller orchestrates everything up through the data rendering, then your front-end technology consumes the data for display.
I guess in a general sense we're still talking MVC concepts, but the framework itself doesn't render the view, and you are not accessing any of the framework from the view. On Mon, Jul 20, 2009 at 2:26 PM, Dean H. Saxe <[email protected]>wrote: > The data is the model. The view is Flex/Ajax. > > -dhs > > -- > Dean H. Saxe > [email protected] > "A true conservationist is a person who knows that the world is not given > by his fathers, but borrowed from his children." -- John James Audubon > > > > > On Jul 20, 2009, at 2:21 PM, Jonathan Burnham wrote: > > I'd argue that by using Flex or Ajax you are not using MVC anymore, but you >> are using a remote event-driven framework. The M & C would still be there, >> but the framework doesn't render a view - it's rendering data. >> >> On Mon, Jul 20, 2009 at 2:04 PM, Dean H. Saxe < >> [email protected]> wrote: >> ORM has nothing to do with MVC. ORM is all about mapping objects to >> relational databases. One can use MVC without objects and without a >> relational database. Conversely, one can use an ORM without using MVC. So >> the two sets of frameworks should not be confused. >> >> -dhs >> >> -- >> Dean H. Saxe >> [email protected] >> "A true conservationist is a person who knows that the world is not given >> by his fathers, but borrowed from his children." -- John James Audubon >> >> >> >> >> >> On Jul 20, 2009, at 1:56 PM, Douglas Knudsen wrote: >> >> I'd argue that if you can't use one of these MVC frameworks with Flex or >> AJAX, it might not be so MVC, eh? :) >> >> Also to point out, ORMs are really a extension of these tools mentioned, >> they are not MVC frameworks on their own. >> >> >> Douglas Knudsen >> http://www.cubicleman.com >> this is my signature, like it? >> >> >> On Mon, Jul 20, 2009 at 11:31 AM, Teddy R. Payne <[email protected]> >> wrote: >> Flex calling a framework is a nice feature. Model-Glue, unless it has >> changed recently, takes advantage of ColdSpring. >> >> Using the RemoteObjectProxy in ColdSpring made it pretty simple to create >> a webservice that calls the result of several dependent CFC objects created >> in the application to be available as a webservice. The RemoteObjectProxy >> also obfuscates the original CFC and it dependent objects as the invocation >> code doesn't exist in the generated proxy. >> >> I see from the ColdBox architectural framework graphic that ColdBox >> mentions LightWire. I would have to see how this would be achieved in >> LightWire. >> >> So, without using a Flex framework, my CFC calls are definitely made >> easier when I consume a RemoteObject in Flex. The caveat here is that >> ColdSpring or LightWire is YAF (Yet Another Framework). >> >> Teddy >> >> >> >> >> ------------------------------------------------------------- >> >> To unsubscribe from this list, manage your profile @ >> http://www.acfug.org?fa=login.edituserform<http://www.acfug.org/?fa=login.edituserform> >> >> For more info, see http://www.acfug.org/mailinglists >> Archive @ http://www.mail-archive.com/discussion%40acfug.org/ >> List hosted by http://www.fusionlink.com >> ------------------------------------------------------------- >> >> >> >> >> > > > ------------------------------------------------------------- > To unsubscribe from this list, manage your profile @ > http://www.acfug.org?fa=login.edituserform<http://www.acfug.org/?fa=login.edituserform> > > For more info, see http://www.acfug.org/mailinglists > Archive @ http://www.mail-archive.com/discussion%40acfug.org/ > List hosted by http://www.fusionlink.com > ------------------------------------------------------------- > > > >
