From a5ffd62175a09402fbe37ec8c2077873e0a35903 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sat, 18 Dec 2010 15:12:46 -0500 Subject: model->resource; make docs render without warnings --- docs/narr/introduction.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'docs/narr/introduction.rst') diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst index 0d8077fc4..3ade3726c 100644 --- a/docs/narr/introduction.rst +++ b/docs/narr/introduction.rst @@ -178,10 +178,11 @@ frameworks, :app:`Pyramid` also generally fits into this class. The :app:`Pyramid` authors believe that the MVC pattern just doesn't really fit the web very well. In a :app:`Pyramid` application, there is a - model, which stores data, and views, which present the data stored in the - model. However, no facility provided by the framework actually maps to - the concept of a "controller". So :app:`Pyramid` is actually an "MV" - framework rather than an "MVC" framework. "MVC", however, is close enough - as a general classification moniker for purposes of comparison with other - web frameworks. - + resource tree, which represents the site structure, and views, which tend + to present the data stored in the resource tree and a user-defined "domain + model". However, no facility provided *by the framework* actually + necessarily maps to the concept of a "controller" or "model". So if you + had to give it some acronym, I guess you'd say :app:`Pyramid` is actually + an "RV" framework rather than an "MVC" framework. "MVC", however, is + close enough as a general classification moniker for purposes of + comparison with other web frameworks. -- cgit v1.2.3