[Jifty-commit] r1176 - in jifty/trunk: share/web/static/js share/web/templates/_elements

[jifty-commit at lists.jifty.org]

Author: trs
Date: Tue Jun  6 15:09:48 2006
New Revision: 1176

Added:
   jifty/trunk/share/web/static/js/app.js
Modified:
   jifty/trunk/   (props changed)
   jifty/trunk/share/web/static/js/app_behaviour.js
   jifty/trunk/share/web/templates/_elements/javascript

Log:
 r12717 at zot:  tom | 2006-06-06 15:09:29 -0400
 * Clean up app_behaviour.js
 * Add a default app.js and include it


Added: jifty/trunk/share/web/static/js/app.js
==============================================================================
--- (empty file)
+++ jifty/trunk/share/web/static/js/app.js	Tue Jun  6 15:09:48 2006
@@ -0,0 +1,2 @@
+/* Put your application's custom JS here... */
+

Modified: jifty/trunk/share/web/static/js/app_behaviour.js
==============================================================================
--- jifty/trunk/share/web/static/js/app_behaviour.js	(original)
+++ jifty/trunk/share/web/static/js/app_behaviour.js	Tue Jun  6 15:09:48 2006
@@ -1,27 +1,29 @@
-/* Uses Behaviour v1.0 (behaviour.js); see
-        http://ripcord.co.nz/behaviour/
+/*
+ * Doc below taken from http://ripcord.co.nz/behaviour/
+ *
+IMPORTANT: if you make DOM changes that mean that an element
+ought to gain or lose a behaviour, call Behaviour.apply()!
 
-   IMPORTANT: if you make DOM changes that mean that an element
-              ought to gain or lose a behaviour, call Behaviour.apply()!
-   (Actually, that *won't* make something lose a behaviour, so if that's necessary
-    you'll need to have an empty "fallback".  Ie, if "div#foo a" should have a special
-    onclick and other "a" shouldn't, then there ought to be an explicit "a" style
-    that sets onclick to a trivial function, if DOM changes will ever happen.)
-   (Also, with the current behaviour.js, the order of application of styles is undefined,
-    so you can't really do cascading.  I've suggested to the author that he change it;
-    if he doesn't, but we need it, it's an easy change to make the sheets arrays instead
-    of Objects (hashes).  For now this can be dealt with by loading multiple sheets (register
-    calls), though.)
+(Actually, that *won't* make something lose a behaviour, so if that's necessary
+you'll need to have an empty "fallback".  I.E. If "div#foo a" should have a
+special onclick and other "a" shouldn't, then there ought to be an explicit "a"
+style that sets onclick to a trivial function, if DOM changes will ever happen.)
+(Also, with the current behaviour.js, the order of application of styles is
+undefined, so you can't really do cascading.  I've suggested to the author
+that he change it; if he doesn't, but we need it, it's an easy change to make
+the sheets arrays instead of Objects (hashes).  For now this can be dealt with
+by loading multiple sheets (register calls), though.)
 */
 
+/* Here's an example... */
 
+
+/*
 var myrules = {
-    /*                '#braindump' : function(element){
-               Rico.Corner.round(element, {});//(order: '#00ff00',compact:true});
-              // Rico.Corner.round(element, {compact:true});
-               // Rico.Corner.round(element);
-                                
-               } */
-                };
+    "h2.rounded": function(element) {
+        Rico.Corner.round(element);
+    }
+};
         
 Behaviour.register(myrules);
+*/

Modified: jifty/trunk/share/web/templates/_elements/javascript
==============================================================================
--- jifty/trunk/share/web/templates/_elements/javascript	(original)
+++ jifty/trunk/share/web/templates/_elements/javascript	Tue Jun  6 15:09:48 2006
@@ -21,6 +21,7 @@
   /static/js/context_menu.js
   /static/js/bps_util.js
   /static/js/rico.js
+  /static/js/app.js
   /static/js/app_behaviour.js
 );