Timeline for Is it fair to call a database or a document a "Model", as in Model/View/Controller?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2013 at 12:26 | comment | added | DougM | Yes, exactly. The model, by and large, is workable. it's the co-mingling of the view and controller that is most alarming. | |
| Aug 5, 2013 at 3:07 | comment | added | Mark Brackett | @DougM - that sounds more like an issue at the Controller and View side of things than the Model. I'm not real familiar with recent vintage VFP or Access, but a common pattern for stuff like this would be data binding. Not exactly MVC (actually MVP) but effective if your tooling supports it. A more MVC approach would be to segment down to subviews and subcontrollers (eg., a controller for just page1 handling txtThing and a controller for pgFrame managing all of its subcontrollers). | |
| Aug 4, 2013 at 23:42 | comment | added | DougM | I'm actually most worried at this stage about not having ANY sensible patterns. "THIS.pgFrame.page1.txtThing.value" is prevalent, and only the shortest example. | |
| Aug 4, 2013 at 20:25 | history | answered | Mark Brackett | CC BY-SA 3.0 |