[Jifty-commit] r2164 - jifty/trunk/lib/Jifty/Manual

jifty-commit at lists.jifty.org jifty-commit at lists.jifty.org
Wed Nov 15 15:24:20 EST 2006


Author: audreyt
Date: Wed Nov 15 15:24:20 2006
New Revision: 2164

Modified:
   jifty/trunk/lib/Jifty/Manual/UsingCSSandJS.pod

Log:
* Jifty::Manual::UsingCSSandJS - Fix the misspelled "app.css" to the correct
  "app.js"; minor reformatting.

Modified: jifty/trunk/lib/Jifty/Manual/UsingCSSandJS.pod
==============================================================================
--- jifty/trunk/lib/Jifty/Manual/UsingCSSandJS.pod	(original)
+++ jifty/trunk/lib/Jifty/Manual/UsingCSSandJS.pod	Wed Nov 15 15:24:20 2006
@@ -158,13 +158,22 @@
 =head2 Assembly of JS definitions
 
 Jifty maintains a complete list of JS files to include. This list may
-be retrieved or set by the accessor
-C<Jifty-E<gt>web-E<gt>javascript_libs>. There should, however, rarely
-arise a situation to do that, because Jifty already reserved two files
-that may get added to your application. C<app.css> which is initially
-empty can get all JS functions you need to define and
-C<app_behaviour.js> is intentionally reserved for defining behaviors
-for DOM objects using the C<behaviour.js> library.
+be retrieved or set by the accessor C<< Jifty->web->javascript_libs >>.
+There should, However, rarely arise a situation to do that, because
+Jifty already reserved two files that may get added to your application:
+
+=over 4
+
+=item F<app.js>
+
+Initially empty; put all JS functions you need to define here.
+
+=item F<app_behaviour.js>
+
+Reserved for defining behaviors for DOM objects using the C<behaviour.js>
+library.
+
+=back
 
 The assembly process of all JS definitions is done in L<Jifty::Web> by
 the method C<include_javascript>.


More information about the Jifty-commit mailing list