Chris McDonough
2010-12-26 4062f104319f471952657947c8eaa29e0622d1e3
wording
1 files modified
12 ■■■■■ changed files
docs/narr/assets.rst 12 ●●●●● patch | view | raw | blame | history
docs/narr/assets.rst
@@ -75,11 +75,13 @@
There is a second form of asset specification: a *relative* asset
specification.  Instead of using an "absolute" asset specification which
includes the package name, in certain circumstances you can omit the package
name.  For example, you might be able to use ``templates/mytemplate.pt``
instead of ``myapp:templates/some_template.pt``.  Such asset specifications
are usually relative to a "current package."  The "current package" is
usually the package which contains the code that *uses* the asset
specification.
name from the specification.  For example, you might be able to use
``templates/mytemplate.pt`` instead of ``myapp:templates/some_template.pt``.
Such asset specifications are usually relative to a "current package."  The
"current package" is usually the package which contains the code that *uses*
the asset specification.  :app:`Pyramid` APIs which accept relative asset
specifications typically describe what the asset is relative to in their
individual documentation.
.. index::
   single: add_static_view