summaryrefslogtreecommitdiff
path: root/docs/narr/views.rst
AgeCommit message (Collapse)Author
2010-12-02add i.e., fix typoCasey Duncan
2010-12-02remove double negativeCasey Duncan
2010-12-02remove word whichCasey Duncan
2010-11-30simplify paragraph about default renderersCasey Duncan
2010-11-30simplify paragraph about dotted view namesCasey Duncan
2010-11-30break up run-onCasey Duncan
2010-11-30Merge https://github.com/Pylons/pyramidCasey Duncan
2010-11-29add commasCasey Duncan
2010-11-29minor reword for smoother flowCasey Duncan
2010-11-29add addCasey Duncan
2010-11-29add commaCasey Duncan
2010-11-29add reminder to add info/link about mako inheritanceCasey Duncan
2010-11-29add commaCasey Duncan
2010-11-29reword paragraph for clarityCasey Duncan
2010-11-29reword sentenceCasey Duncan
2010-11-29simplify sentenceCasey Duncan
2010-11-29deredundify sentenceCasey Duncan
2010-11-29simplify sentenceCasey Duncan
2010-11-28Normalized narrative doc, code with linenos while text+bash don'tBlaise Laflamme
2010-11-28Add note about httpexceptions not typically being raisedCasey Duncan
2010-11-28add commaCasey Duncan
2010-11-28Narrative doc cleanupBlaise Laflamme
2010-11-28If => SinceCasey Duncan
2010-11-28A => anCasey Duncan
2010-11-28Move Context-And-Request View Callable Definitions to a sidebarCasey Duncan
Remove earlier mentions of this alternate calling convention to avoid confusion
2010-11-27remove lie about json renderer calling view resultCasey Duncan
2010-11-27remove quotes for consistencyCasey Duncan
2010-11-27add commaCasey Duncan
2010-11-27reword paragraph about view callable return valuesCasey Duncan
2010-11-27lose the word 'named'Casey Duncan
2010-11-09- All references to Pyramid-the-application were changed from :mod:`pyramid`Chris McDonough
to :app:`Pyramid`. A custom role setting was added to ``docs/conf.py`` to allow for this. (internal)
2010-11-07Minor documentation fixes.Marius Gedminas
2010-11-04move declarative view docs to the declarative chapterChris McDonough
2010-11-02- Remove references to 'WebOb' Response and just call it 'Response', and noteChris McDonough
that it is imported from pyramid. API docs can mention its inheritance from webob (aka "Provide a webob.Response class facade for forward compat").
2010-11-01document IRendererInfo in API docsChris McDonough
2010-11-01for performance reasons (to avoid unnecessary ZCA lookups), pass the helper ↵Chris McDonough
object itself to a renderer rather than a dictionary derivation)
2010-10-31pass settings to renderer factory, as most template renderers need to look ↵Chris McDonough
at at least one setting to determine how to do rendering
2010-10-31- Renderer factories now accept a *dictionary* rather than an absolute resourceChris McDonough
specification or an absolute path. The dictonary contains the following keys: ``name`` (the ``renderer=`` value), ``package`` (the 'current package' when the renderer configuration statement was found), ``type``: the renderer type, and ``registry``: the current registry. Third-party ``repoze.bfg`` renderer implementations that must be ported to Pyramid will need to account for this. This change was made to support more flexible Mako template rendering.
2010-10-30Adding Mako environment variables.Ben Bangert
2010-10-29First set of Mako docs for narrative.Ben Bangert
2010-10-29docs renderingChris McDonough
2010-10-29bfg_view -> view_configChris McDonough
2010-10-25add httpexceptions docsChris McDonough
2010-10-25convert narrative docs to PyramidChris McDonough
2010-10-14typoChris McDonough
2010-10-13point at request API docsChris McDonough
2010-10-08tweakChris McDonough
2010-10-08rearrangeChris McDonough
2010-10-08be more explicit about responses earlierChris McDonough
2010-09-15FeaturesChris McDonough
-------- - Compatibility with WebOb 1.0. Requirements ------------ - Now requires WebOb >= 1.0. Backwards Incompatibilities --------------------------- - Due to changes introduced WebOb 1.0, the ``repoze.bfg.request.make_request_ascii`` event subscriber no longer works, so it has been removed. This subscriber was meant to be used in a deployment so that code written before BFG 0.7.0 could run unchanged. At this point, such code will need to be rewritten to expect Unicode from ``request.GET``, ``request.POST`` and ``request.params`` or it will need to be changed to use ``request.str_POST``, ``request.str_GET`` and/or ``request.str_params`` instead of the non-``str`` versions of same, as the non-``str`` versions of the same APIs always now perform decoding to Unicode.