> Yep, if you were a sophisticated CF and Flash developer(which > I`m not) I guess you would be thinking the whole project in > terms of the MVC controller approach and breaking both Flash > and CF into a presentation layers first, developing that > first, then your handlers say menu buttons/links/dynamic > stuff in CF and Flash listening for input, then the > controller layer how all this is handled in the background by > Flash/CF...but I`m noexpert, I believe this MVC approach is > an object oriented one first developed in c++ or java..I > guess I need further info on this topic but I find it can get > very abstract and hard to follow, good example is fusebox the > way it separates out an application into different parts like > the above
So then you are now talking about a "real-world" scenario aren't you! In other words, creating a scenario like the one I am describing may not be the most helpful way of doing it. Separating out the data (model), control (controller) and UI (view) elements is inherently helpful. Maybe using "MVC" as a methodology is useful up to a point with CF and web apps, but in the real world it's not that good... Comments? Paul -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
