Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
becki:linux:dojo [2010-12-07 20:26] becki |
becki:linux:dojo [2011-03-08 06:49] (aktuell) becki |
||
---|---|---|---|
Zeile 2: | Zeile 2: | ||
===== Links == | ===== 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? == | ===== Why Dojo? == | ||
Zeile 38: | Zeile 38: | ||
==== Make a cross-domain Build == | ==== 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 | - [[http://dojotoolkit.org/download/|Download]] and extract latest stable //source// release | ||
Zeile 139: | 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''. | * 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. | * 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]] | ||