From ae901436a61563968cc31cc636f1fbeb5e85b528 Mon Sep 17 00:00:00 2001 From: Paul Everitt Date: Sun, 11 Aug 2013 09:53:00 -0400 Subject: Per discussion with Chris, just wrap up "getting started" as the Quick Tour. Still need to do more linking and perhaps add a section on root factories, authorization, authentication. --- docs/getting_started/views.rst | 30 ------------------------------ 1 file changed, 30 deletions(-) delete mode 100644 docs/getting_started/views.rst (limited to 'docs/getting_started/views.rst') diff --git a/docs/getting_started/views.rst b/docs/getting_started/views.rst deleted file mode 100644 index f30caea8a..000000000 --- a/docs/getting_started/views.rst +++ /dev/null @@ -1,30 +0,0 @@ -================================ -Handling Web Requests With Views -================================ - -Free-standing functions are the regular way to do views. Many times, -though, you have several views that are closely related. For example, -a document might have many different ways to look at it, -or a form might submit to different targets, or a REST handler might -cover different operations. - -Grouping these together makes logical sense. A view class lets you -group views, centralize some repetitive defaults, share some state -assignments, and use helper functions as class methods. - -As an example, imagine we have some views around saying hello to a -person, then editing that person or perhaps deleting that person. They -might logically belong together. We could do these as independent -functions, but let's do them together as a view class: - - -...and some routes that wire up the views to URLs: - - -...and a form in ``hello_world.jinja2`` that submits to the second view: - - -Just to review: - -- The ``/howdy/amy`` URL matches the ``hello`` route, handled by the - ``hello_view`` class method. \ No newline at end of file -- cgit v1.2.3