Permalink
Browse files

fixing some kind of breakage

  • Loading branch information...
Website Account
Website Account committed Jan 11, 2012
2 parents 1e78972 + ce7a671 commit b8b1a084b82754bfb506ac31e65baca66fa87398
Showing with 1,067 additions and 35 deletions.
  1. +5 −5 build/buildSystem.rst
  2. +3 −1 developer/contributors.rst
  3. +4 −3 dijit/_WidgetBase.rst
  4. +6 −4 dojo/on.rst
  5. +21 −13 dojo/parser.rst
  6. +987 −0 dojox/calendar.rst
  7. +6 −1 dojox/charting.rst
  8. +8 −0 dojox/widget/Wizard.rst
  9. +7 −7 loader/amd.rst
  10. +1 −1 loader/index.rst
  11. +19 −0 releasenotes/1.8.rst
View
@@ -743,7 +743,7 @@ package config, it will consume the following properties of that object:
* ``directories.lib``, indicating the packages ``location`` property value.
* ``main``, indicating the package's ``main`` property value
* ``version``, indicating the package's version
-* ``dojo.profile``, indicating the default profile associated with the package
+* ``dojoBuild``, indicating the default profile associated with the package
Relative paths are computed with respect to the path at which the package.json resource resides.
@@ -756,17 +756,17 @@ this:
~/dev/dtk/util/buildscripts:./build.sh --package .../../dojo
-This is possible because of the dojo package.json resource contains the property dojo.profile which indicates the
+This is possible because of the dojo package.json resource contains the property dojoBuild which indicates the
default profile for the package. As usual, it should be a relative filename and is computed with respect to the path at
which the package.json resource resides.
-The design of the ``dojo.profile`` property is quite handy. For example, the authors of the acme program may not be
-experts on how best to build dojo or dijit. The idea of a default profile as indicated by the ``dojo.profile`` property
+The design of the ``dojoBuild`` property is quite handy. For example, the authors of the acme program may not be
+experts on how best to build dojo or dijit. The idea of a default profile as indicated by the ``dojoBuild`` property
solves this problem even when the package.json resource is not mentioned explicitly. Here's how it works.
When the build system is given a profile that contains a set of packages, it automatically attempts to find and consume
each package's package.json resource. The system looks for the file "package.json" in the directory given by the package
-configuration ``location`` property. If a package.json resource is found and that resource contains a ``dojo.profile``
+configuration ``location`` property. If a package.json resource is found and that resource contains a ``dojoBuild``
property, then the build system automatically consumes that default profile for that package. The build system will use
any properties in the default profile that are not explicitly mentioned a profile provided at the command line; this
allows an easy way to selectively override profile property values found in the default profile for a particular
@@ -114,6 +114,7 @@ Individuals who have signed Dojo CLAs
* Dangoor, Kevin
* Davis, Conor
* Davis, David Wayne
+* Davis, Lee
* Davor, HRG
* DeJarnett, Philip
* Della-Franca, Sean
@@ -638,7 +639,7 @@ Corporations or Organizations with a CCLA on file
* GCGF
* Global Media Systems
* GreenPlum
-* IBM: Adam Peller, Becky Gibson, David Boloker, William Keese, Christopher Mitchell, Douglas Hays, Jared Jurkiewicz, William Higgins, Richard Backhouse
+* IBM: Adam Peller, Becky Gibson, David Boloker, William Keese, Christopher Mitchell, Douglas Hays, Jared Jurkiewicz, William Higgins, Richard Backhouse, Christophe Jolif
* Indico Group
* Laszlo Systems, Inc.
* Leorent, GmbH: Michael Rasmussen
@@ -663,6 +664,7 @@ Corporations or Organizations with a CCLA on file
* SITA
* SitePen, Inc.
* SnapLogic, Inc.
+* SOASTA, Inc.
* Spider Strategies
* Sun Microsystems, Inc.
* SUPSI
View
@@ -78,14 +78,15 @@ That provides you the following extension points (methods) you can override and
This is often used for layout widgets like BorderContainer.
If the widget does JS sizing, then startup() should call resize(), which does the sizing.
-- destroy
- Implement destroy if you have special tear-down work to do (the superclasses will take care of most of it for you.
+- uninitialize
+ Implement uninitialize if you have special tear-down work to do (the superclasses will take care of most of the widget cleanup for you). While it may be tempting to override the destroy method directly, the uninitialize method is there explicitly as a stub for this very purpose.
+
Examples on how to destroy a widget:
.. js ::
var widget = new dijit.form.TextBox({name: "firstname"}, "inputId");
- widget.destroy();
+ widget.destroy(); // uninitialize will automatically be called for you
.. js ::
View
@@ -36,13 +36,13 @@ The basic usage looks like:
on(document, "click", clickHandler);
});
-The return value from the on function is a signal handler that has a cancel() method that can be used to stop listening for the events. For example, to listen for a single click, one could do:
+The return value from the on function is a signal handler that has a remove() method that can be used to stop listening for the events. For example, to listen for a single click, one could do:
.. js ::
var signal = on(document, "click", function(){
- // cancel after first event
- signal.cancel();
+ // remove listener after first event
+ signal.remove();
// now perform any other action
});
@@ -120,6 +120,8 @@ The on.selector function can be used to apply event delegation when extension ev
on(node, on.selector(".myClass", mouse.enter), myClassHoverHandler);
});
+The on.selector function can also be used with custom selector functions, by providing a function instead of a selector string as the first argument. The function will be called each time the indicated event takes place, and provide the event's target as the single argument. If the selector function has a corresponding node that matches for the event target, it can return that node. If the selector does not match, it should return a falsy value.
+
emit function
-----------------
@@ -355,7 +357,7 @@ dojo/on migration
Converting from dojo.connect
----------------------------
-dojo/on can replace dojo.connect when connect is used for connecting to DOM nodes and event emitting objects (see the :ref:`dojo/Evented <dojo/Evented>` page for more information). If you're connecting to a plain method, use dojo/aspect instead. Also, note that some event emitting objects, like dijits, have their own event naming conventions and may need to be changed to remove "on" from the names and lower-case the remaining event names used with dojo.connect for some event emitting objects like dijits.
+dojo/on can replace dojo.connect when connect is used for connecting to DOM nodes and event emitting objects (see the :ref:`dojo/Evented <dojo/Evented>` page for more information). If you're connecting to a plain method, use :ref:`dojo/aspect <dojo/aspect>` instead. Also, note that some event emitting objects, like dijits, have their own event naming conventions and may need to be changed to remove "on" from the names and lower-case the remaining event names used with dojo.connect for some event emitting objects like dijits.
Transitioning to Dojo 2.0
-------------------------
View
@@ -15,7 +15,7 @@ Inside your HTML you mark nodes for the parser by setting the data-dojo-type att
.. html ::
- <input data-dojo-type="dijit.form.TextBox" name="nm" value="hello world">
+ <input data-dojo-type="dijit/form/TextBox" name="nm" value="hello world">
The parser can scan the entire DOM for ``data-dojo-type`` attributes, and create new instances from nodes like this.
@@ -41,7 +41,7 @@ To include the Dojo parser on your page, require the module `dojo.parser`:
.. js ::
- // Dojo 1.7 (AMD)
+ // Dojo 1.7+ (AMD)
require("dojo/parser", function(parser){
// write your code here
});
@@ -119,9 +119,17 @@ Attributes which correspond to native HTML attributes appear directly in the mar
.. html ::
+ <!-- Dojo 1.8+ -->
+ <input data-dojo-type="dijit/form/TextBox" name="dept"
+ data-dojo-props="scrollOnFocus: true"/>
+
+.. html ::
+
+ <!-- Dojo < 1.8 -->
<input data-dojo-type="dijit.form.TextBox" name="dept"
data-dojo-props="scrollOnFocus: true"/>
+**Note** as of Dojo 1.8, the parser accepts the Module ID (MID) for the `data-dojo-type` attribute.
Boolean parameters
~~~~~~~~~~~~~~~~~~
@@ -130,27 +138,27 @@ Due to HTML subtleties, for boolean parameters that are false, it's best not to
.. html ::
- <input data-dojo-type="dijit.form.Button">
+ <input data-dojo-type="dijit/form/Button">
Further, in standard HTML (as opposed to XHTML), the special parameters `checked` and `disabled` and `selected` should be specified as single keywords without a value:
.. html ::
- <input data-dojo-type="dijit.form.Button" disabled>
- <input data-dojo-type="dijit.form.CheckBox" checked>
+ <input data-dojo-type="dijit/form/Button" disabled>
+ <input data-dojo-type="dijit/form/CheckBox" checked>
In XHTML they should be specified in the official format of repeating the attribute name as the value:
.. html ::
- <input data-dojo-type="dijit.form.Button" disabled="disabled"/>
- <input data-dojo-type="dijit.form.CheckBox" checked="checked"/>
+ <input data-dojo-type="dijit/form/Button" disabled="disabled"/>
+ <input data-dojo-type="dijit/form/CheckBox" checked="checked"/>
Although specifying disabled="true" will disable a widget, note that the following syntax should not be used as it's unreliable whether it evaluates to true or false:
.. html ::
- <input data-dojo-type="dijit.form.Button" disabled=""/>
+ <input data-dojo-type="dijit/form/Button" disabled=""/>
Date parameters
@@ -242,7 +250,7 @@ To execute code on instantiation, use the same format but don't specify an event
Execute Code on Change of Property
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-**New in 1.7** To execute code when a value changes for a property for objects that support ``object.watch()`` the ``type="dojo/watch"`` can be used:
+To execute code when a value changes for a property for objects that support ``object.watch()`` the ``type="dojo/watch"`` can be used:
.. html ::
@@ -260,7 +268,7 @@ The ``.watch()`` function always passes three arguments when it is called, repre
Execute Code when an Event Occurs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-**New in 1.7** While similar to ``dojo.connect()``, the ``type="dojo/on"`` can be used to specify ``on`` behaviour:
+While similar to ``dojo.connect()``, the ``type="dojo/on"`` can be used to specify ``on`` behaviour:
.. html ::
@@ -288,7 +296,7 @@ For functions that take (named) parameters, specify them in an `data-dojo-args`
.. html ::
- <div data-dojo-type="dijit.tree.TreeStoreModel" store="store">
+ <div data-dojo-type="dijit/tree/TreeStoreModel" store="store">
<script type="dojo/method" data-dojo-event="getChildren" data-dojo-args="item, onComplete">
return store.fetch({query: {parent: store.getIdentity(item)}, onComplete: onComplete});
</script>
@@ -407,7 +415,7 @@ Parser API notes
The main API to the parser, parse(), was discussed above.
-``NEW in 1.3:`` Beginning in release 1.3 of dojo, you can manually call dojo.parser.instantiate on any node - and pass in an additional mixin to specify options, such as data-dojo-type, etc. The values in the mixin would override any values in your node. For example:
+Beginning in release 1.3 of dojo, you can manually call dojo.parser.instantiate on any node - and pass in an additional mixin to specify options, such as data-dojo-type, etc. The values in the mixin would override any values in your node. For example:
.. html ::
@@ -421,7 +429,7 @@ You can manually call the parser's instantiate function (which does the "Magical
Calling instantiate in this way will return to you a list of instances that were created. Note that the first parameter to instantiate is an array of nodes...even if it's one-element you need to wrap it in an array
-``NEW in 1.4:`` You specify that you do not want subwidgets to be started if you pass _started: false in your mixin. For example:
+You specify that you do not want subwidgets to be started if you pass _started: false in your mixin. For example:
.. js ::
Oops, something went wrong.

0 comments on commit b8b1a08

Please sign in to comment.