Re: [WebDNA] Webdna and CMS
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108078
interpreted = N
texte = >> - MVC design will save vast amounts of maintenance headache; = separation of logic from presentation (separate the webdna from the = HTML/CSS/JS that spits out to the browser as much as possible). >=20 > For the most part, I think in our context, we mostly could benefit = from the use of a MV system (separating the WebDNA from = controlling/viewing templates as much as possible to allow versatility = on the front end). What would be the Controller aspect?.. javascript = handlers, AJAX, Flash I suppose. >=20 > Anyway, I'm curious how WebDNA'ers perceive the MVC architecture when = related to WebDNA or PHP apps. I see 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) I'll try to put a little code/food-for-thought together, and post it = here later.. today hopefully. -G=
Associated Messages, from the most recent to the oldest:
>> - MVC design will save vast amounts of maintenance headache; = separation of logic from presentation (separate the webdna from the = HTML/CSS/JS that spits out to the browser as much as possible). >=20 > For the most part, I think in our context, we mostly could benefit = from the use of a MV system (separating the WebDNA from = controlling/viewing templates as much as possible to allow versatility = on the front end). What would be the Controller aspect?.. javascript = handlers, AJAX, Flash I suppose. >=20 > Anyway, I'm curious how WebDNA'ers perceive the MVC architecture when = related to WebDNA or PHP apps. I see 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) I'll try to put a little code/food-for-thought together, and post it = here later.. today hopefully. -G=
Govinda
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:
japanese characters (1997)
Cart questions (1997)
PIXO support (1997)
Document Contains no data, or showcart error. (1997)
Bulk Processing Offline (2004)
WebCommerce: Folder organization ? (1997)
Entering the Serial Number (2003)
RE: Error: template (1997)
can you take a look (2003)
Fun with Dates - revisited (1997)
different browser, different result (2000)
[WriteFile] problems (1997)
Locking up with WebCatalog... (1997)
My solution... (1996)
Mac vs. Unix Line Endings (2002)
Document Contains No Data! (1997)
math versus text (2005)
The Form authentication trick (2000)
Navigator 4.01 (1997)
WebCatalog host... (2000)