diff options
| author | Chris McDonough <chrism@plope.com> | 2010-12-18 02:27:14 -0500 |
|---|---|---|
| committer | Chris McDonough <chrism@plope.com> | 2010-12-18 02:27:14 -0500 |
| commit | fb6a5ce52a275f7798e82a34b5907ea118cbd2ff (patch) | |
| tree | 29e80d0eb681676d1e0eb2707ca764dbf5491864 /docs/narr/introduction.rst | |
| parent | bf89764a7e3ccab6133c9ad43b8d9af4f5c4083b (diff) | |
| download | pyramid-fb6a5ce52a275f7798e82a34b5907ea118cbd2ff.tar.gz pyramid-fb6a5ce52a275f7798e82a34b5907ea118cbd2ff.tar.bz2 pyramid-fb6a5ce52a275f7798e82a34b5907ea118cbd2ff.zip | |
model -> resource; resource -> asset
Diffstat (limited to 'docs/narr/introduction.rst')
| -rw-r--r-- | docs/narr/introduction.rst | 24 |
1 files changed, 11 insertions, 13 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst index 7c725690d..0d8077fc4 100644 --- a/docs/narr/introduction.rst +++ b/docs/narr/introduction.rst @@ -144,10 +144,9 @@ it only supplies a mechanism to map URLs to :term:`view` code, along with a set of conventions for calling those views. You are free to use third-party components that fit your needs in your applications. -The concepts of :term:`view` and :term:`model` are used by -:app:`Pyramid` mostly as they would be by Django. -:app:`Pyramid` has a documentation culture more like Django's than -like Zope's. +The concept of :term:`view` is used by :app:`Pyramid` mostly as it would be +by Django. :app:`Pyramid` has a documentation culture more like Django's +than like Zope's. Like :term:`Pylons` version 1.0, but unlike :term:`Zope`, a :app:`Pyramid` application developer may use completely imperative @@ -177,13 +176,12 @@ frameworks, :app:`Pyramid` also generally fits into this class. .. sidebar:: You Say :app:`Pyramid` is MVC, But Where's The Controller? - The :app:`Pyramid` authors believe that the MVC pattern just - doesn't really fit the web very well. In a :app:`Pyramid` - application, there are models, which store data, and views, which - present the data stored in models. 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. + 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. |