[Checkins] SVN: grokcore.view/trunk/README.txt Add a note about the directory resource "static" not being registered

Jan-Wijbrand Kolman janwijbrand at gmail.com
Fri Apr 10 15:37:46 EDT 2009


Log message for revision 99099:
  Add a note about the directory resource "static" not being registered
  when the directory itself does not exist.

Changed:
  U   grokcore.view/trunk/README.txt

-=-
Modified: grokcore.view/trunk/README.txt
===================================================================
--- grokcore.view/trunk/README.txt	2009-04-10 17:41:43 UTC (rev 99098)
+++ grokcore.view/trunk/README.txt	2009-04-10 19:37:46 UTC (rev 99099)
@@ -101,12 +101,12 @@
 Static resources
 ----------------
 
-Browser pages often need additional static resources like CSS and
-JavaScript files.  These can be conveniently placed into a directory
-called ``static`` in the package that contains the view code.  This
-directory will automatically be registered as a resource directory.
-It is available as the ``static`` variable in all views of this
-package and you can refer to files inside this directory like so::
+Browser pages often need additional static resources like CSS and JavaScript
+files. These can be conveniently placed into a directory called ``static`` in
+the package that contains the view code. When this directory exists it will
+automatically be registered as a resource directory. It then is available as
+the ``static`` variable in all views of this package and you can refer to files
+inside this directory like so::
 
   <img src="hello.png" tal:attributes="src static/hello.png" />
 
@@ -192,7 +192,8 @@
     The response object, typically provides ``IHTTPResponse``.
 
 ``static``
-    Directory resource representing the package's ``static`` directory.
+    Directory resource representing the package's ``static`` directory or None
+    if no such directory was found during grokking.
 
 ``redirect(url)``
     Redirect to the given URL.



More information about the Checkins mailing list