Re: [WebDNA] Webdna and CMS
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108083
interpreted = N
texte = Govinda wrote: > My understanding is that the: > - Controller (C) part is where all the business logic decides that gets done what will get displayed. > - Model (M) part is where all the db interaction happens (whether we are reading or writing records) > - View (V) part is where we assemble the display output. Views display static things mixed with chunks of dynamic output that were handed it by the C (and the C may have been handed some of its data from an M) That's not exactly how I understand the idea behind MVC, though I don't claim to understand it exactly. ;-) However, I think it becomes a more ambiguous idea when it comes to web apps, especially when your web app combines data and scripting in one engine. Historically, the way I understand it, the model contains both the data layer and business logic. The controller handles the transfer of input. The view is both input/output (forms and HTML/CSS) However, like I said, I think the term leaves some room for an ambiguous definition when it comes to the web... with the main idea of making apps more manageable by grouping the different functions of an application. ('functions', in this case meaning, methods, aspects, of an app.) I like the idea of keeping a WebDNA page, WebDNA, and having as little of WebDNA in the actual HTML file/s as possible. Then, for controller, perhaps all the AJAX stuff is grouped together with unified input/output.. Also, This is where the idea of the WYSIWYG-like syntax would have been great (if it would have actually worked right) At that point, you'd have just the required (or whatever that syntax is ;-), and Dreamweaver wouldn't be confused about it. Too bad that is on the deprecated track and not the fixed track. Anyway, sounds like Tom Duke and I will be working on some ideas for MVC, so it will be interesting to hear/see how sees it as well. Donovan -- Donovan Brooke Euca Design Center www.euca.us www.keepitturning.co
Associated Messages, from the most recent to the oldest:
Govinda wrote: > My understanding is that the: > - Controller (C) part is where all the business logic decides that gets done what will get displayed. > - Model (M) part is where all the db interaction happens (whether we are reading or writing records) > - View (V) part is where we assemble the display output. Views display static things mixed with chunks of dynamic output that were handed it by the C (and the C may have been handed some of its data from an M) That's not exactly how I understand the idea behind MVC, though I don't claim to understand it exactly. ;-) However, I think it becomes a more ambiguous idea when it comes to web apps, especially when your web app combines data and scripting in one engine. Historically, the way I understand it, the model contains both the data layer and business logic. The controller handles the transfer of input. The view is both input/output (forms and HTML/CSS) However, like I said, I think the term leaves some room for an ambiguous definition when it comes to the web... with the main idea of making apps more manageable by grouping the different functions of an application. ('functions', in this case meaning, methods, aspects, of an app.) I like the idea of keeping a WebDNA page, WebDNA, and having as little of WebDNA in the actual HTML file/s as possible. Then, for controller, perhaps all the AJAX stuff is grouped together with unified input/output.. Also, This is where the idea of the WYSIWYG-like syntax would have been great (if it would have actually worked right) At that point, you'd have just the required (or whatever that syntax is ;-), and Dreamweaver wouldn't be confused about it. Too bad that is on the deprecated track and not the fixed track. Anyway, sounds like Tom Duke and I will be working on some ideas for MVC, so it will be interesting to hear/see how sees it as well. Donovan -- Donovan Brooke Euca Design Center www.euca.us www.keepitturning.co
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Authenticate (1997)
WebDelivery downloads alias, not original ? (1997)
redirect with frames (1997)
[OT] Friday Time Waster (2003)
WebDNA Solutions ... sorry! (1997)
A matter of time (1997)
Where is f2? (1997)
How to put the Trademark Symbol (%99) in Sendmail? (2003)
Emailer help....! (1997)
TCPConnect , can I get an example, pretty please. (2002)
WebDNA Solutions ... sorry! (1997)
[Way OT] Workstation Security (2002)
[WebDNA] SENDMAIL (2017)
Using Applescript to process WebCatalog functions (1998)
error: Too many nested [xxx] contexts (1997)
Web Merchant Docs? (2002)
Emailer help....! (1997)
read and write you own cookies with webcat (1997)
Database Options (1997)
WebDNA EMail Preference (2005)