Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- becki:linux:dojo [2010-06-30 13:59]
becki
+++ becki:linux:dojo [2011-03-08 06:49] (aktuell)
becki
@@ Zeile 2: / Zeile 2: @@
 ===== Links ==
-[[dojo>quickstart/index|Tutorial]], [[dojo>manual/index|Reference]] --- [[http://api.dojotoolkit.org/|API Reference]] --- [[http://dojocampus.org/explorer/|Feature explorer]] (incomplete?) ---  [[http://o.dojotoolkit.org/book/dojo-book-0-9/hello-world-tutorial|hello world (outdated)]] --- [[http://dev.aol.com/dojo|Dojo Lib from AOL's CDN]] --- [[http://www.sitepen.com/blog/series/dojo-quick-start-guide/|Old quick start]] --- [[javascript]]
+[[dojo>quickstart/index|Tutorial]] --- [[dojo>quickstart/dojo-basics|dojo-basics]] --- [[dojo>manual/index|Reference]] --- [[http://api.dojotoolkit.org/|API Reference]] --- [[http://dojocampus.org/explorer/|Feature explorer]] (incomplete?) --- [[http://dev.aol.com/dojo|Dojo Lib from AOL's CDN]] --- [[http://www.sitepen.com/blog/series/dojo-quick-start-guide/|Old quick start]] --- [[javascript]]
 ===== Why Dojo? ==
@@ Zeile 22: / Zeile 22: @@
 FIXME Does this table make sense at all?
+===== Use Dojo from your Own Server ==
+Download the "Dojo Toolkit Release" from http://dojotoolkit.org/download#getdojo and install it on your server to ''/var/www/htdocs/lib/''
+See also: http://docs.dojocampus.org/quickstart/install#use-dojo-from-your-own-server Note that the ''themeTester.html'' mentioned there does //not// exist in the install.
 ===== Make a custom Build ==
@@ Zeile 32: / Zeile 38: @@
 ==== Make a cross-domain Build ==
-The following exemplary steps build a cross-domain build with standard profile to be installed on the machine of the brower. Hence the browser machine needs a webserver as well! The actual dojo app can live on a space limited device where the browser connects to:
+The following exemplary steps build a cross-domain build with standard profile to be installed on the machine of the browser. Hence the browser machine needs a webserver as well! The actual dojo app can live on a space limited device where the browser connects to:
   - [[http://dojotoolkit.org/download/|Download]] and extract latest stable //source// release
@@ Zeile 71: / Zeile 77: @@
 </code>
-Cd into ''dojo-svn/dojo-svn/util/buildscripts/'' and issue the following command (you will use different locales):
+Cd into ''dojo-svn/dojo-svn/util/buildscripts/'' and issue the following command (you will use different languages in ''localeList''):
   ./build.sh profile=exorsus action=clean,release localeList=en-us,de-de cssOptimize=comments
-<note tip>Tip: Save the build profile file and the build command in the repostitory of your web app and just create symlinks from ''dojo-svn/...'' to the files in your web app!</note>
 The build is created in ''dojo-svn/release/''
+<note tip>Tip: Save the build profile file and the build command in the source tree of your own web app and just create symlinks from ''dojo-svn/...'' to the files in your web app!</note>
 === Deploy ==
@@ Zeile 89: / Zeile 95: @@
       |-- dijit
       |   `-- themes
-      |       |-- dijit.css
       |       `-- tundra
       |           |-- images
       |           |   |-- accordionItemActive.gif
       |           |   |-- ...
-      |           |   |-- ... everything except the .psd files ...
+      |           |   |-- ... everything except the .psd files
       |           |   |-- ...
       |           |   `-- warning.png
@@ Zeile 100: / Zeile 105: @@
       `-- dojo
           |-- dojo.js
-          `-- exodojo.js
+          |-- exodojo.js
+          `-- nls
+              |-- exodojo_ROOT.js
+              |-- ...
+              |-- ... everything that begins with the name of your layer file
+              |-- ...
+              `-- exodojo_xx.js
 The example assumes that you work with the tundra theme. Of course you have to take the files of the theme you use!
-<note important>You need to maintain the same directory structure on your webserver as given in ''dojo-svn/release/''!</note>
+<note important>You need to maintain the same directory structure in the web root of your webserver as given in ''dojo-svn/release/''!</note>
 <note tip>Tip: The ''images/'' subdir of the tundra theme contains (useless?) Photoshop images (''*.psd''). Remove them to save space!</note>
@@ Zeile 128: / Zeile 139: @@
   * Name unused css modules with the ''cssImportIgnore'' command line attribute when calling ''build.sh''. You can easily spot unused css modules by looking at ''dojo-svn/dijit/themes/tundra/tundra.css''.
   * Unused images may be picked out from ''dojo-svn/dijit/themes/images/''. For, you look in ''dojo-svn/dijit/themes/tundra/tundra.css'' for all references to the ''image'' subdir and there you remove all images which are //not// referenced.
+===== Dijit ==
+Dijit widgets are wrappers around native DOM nodes.
+''dojo.byId()'' returns the DOM node, whereas [[dojo>dijit/byId|dijit.byId()]] returns the Dijit widget.
+Dijit widgets have an attribute called ''domNode'' to access the DOM node. [[dojo>dijit/info|More]]
+===== Events ==
+Normal DOM events are lowercase (like ''onclick''). Whereas Dojo widget events are camel case (''onClick'').
+''dojo.connect'' is a more powerful replacement for native event handling. More: [[dojo>quickstart/events|JavaScript events and Dojo]] / [[javascript#events|Javascript events]]
+===== Todo ==
+  * Check: [[http://www.ibm.com/developerworks/web/tutorials/wa-dojotoolkit/|Build an Ajax application with the Dojo Toolkit]]

In Becki sei Wiki

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Unterschiede

Seiten-Werkzeuge