-.. class:: View
-
- :class:`!View` is an abstract model that represents an item which can be "rendered", either in response to an :class:`HttpRequest` or as a standalone. It subclasses :class:`Entity`, and defines the following additional methods and attributes:
-
- .. attribute:: accepts_subpath
-
- Defines whether this :class:`View` can handle subpaths. Default: ``False``
-
- .. method:: handles_subpath(subpath)
-
- Returns True if the the :class:`View` handles the given subpath, and False otherwise.
-
- .. attribute:: nodes
-
- A generic relation back to nodes.
-
- .. method:: reverse([view_name=None, args=None, kwargs=None, node=None, obj=None])
-
- If :attr:`accepts_subpath` is True, try to reverse a URL using the given parameters using ``self`` as the urlconf.
-
- If ``obj`` is provided, :meth:`get_reverse_params` will be called and the results will be combined with any ``view_name``, ``args``, and ``kwargs`` that may have been passed in.
-
- This method will raise the following exceptions:
-
- - :class:`ViewDoesNotProvideSubpaths` if :attr:`accepts_subpath` is False.
- - :class:`ViewCanNotProvideSubpath` if a reversal is not possible.
-
- .. method:: get_reverse_params(obj)
-
- This method is not implemented on the base class. It should return a ``view_name``, ``args``, ``kwargs`` tuple suitable for reversing a url for the given ``obj`` using ``self`` as the urlconf. If a reversal will not be possible, this method should raise :class:`ViewCanNotProvideSubpath`.
-
- .. method:: attributes_with_node(node)
-
- Returns a :class:`QuerySetMapper` using the :class:`node <Node>`'s attributes as a passthrough.
-
- .. method:: render_to_response(request[, extra_context=None])
-
- Renders the :class:`View` as an :class:`HttpResponse`. This will raise :const:`philo.exceptions.MIDDLEWARE_NOT_CONFIGURED` if the `request` doesn't have an attached :class:`Node`. This can happen if :class:`philo.middleware.RequestNodeMiddleware` is not in :setting:`settings.MIDDLEWARE_CLASSES` or if it is not functioning correctly.
-
- :meth:`!render_to_response` will send the :obj:`view_about_to_render <philo.signals.view_about_to_render>` signal, then call :meth:`actually_render_to_response`, and finally send the :obj:`view_finished_rendering <philo.signals.view_finished_rendering>` signal before returning the ``response``.
-
- .. method:: actually_render_to_response(request[, extra_context=None])