Zend_Dojo_Data: dojo.data EnvelopesDojo provides data abstractions for data-enabled widgets via its dojo.data component. This component provides the ability to attach a data store, provide some metadata regarding the identity field and optionally a label field, and an API for querying, sorting, and retrieving records and sets of records from the datastore. dojo.data is often used with XmlHttpRequest to pull dynamic data from the server. The primary mechanism for this is to extend the QueryReadStore to point at a URL and specify the query information. The server side then returns data in the following JSON format:
Zend_Dojo_Data provides a simple interface for building such structures programmatically, interacting with them, and serializing them to an array or JSON. Zend_Dojo_Data UsageAt its simplest, dojo.data requires that you provide the name of the identifier field in each item, and a set of items (data). You can either pass these in via the constructor, or via mutators: Example #1 Zend_Dojo_Data initialization via constructor
Example #2 Zend_Dojo_Data initialization via mutators
You can also add a single item at a time, or append items, using addItem() and addItems(). Example #3 Appending data to Zend_Dojo_Data
Individual items may be one of the following:
You can attach collections of the above items via addItems() or setItems() (overwrites all previously set items); when doing so, you may pass a single argument:
If you want to specify a field that will act as a label for the item, call setLabel(): Example #4 Specifying a label field in Zend_Dojo_Data
Finally, you can also load a Zend_Dojo_Data item from a dojo.data JSON array, using the fromJson() method. Example #5 Populating Zend_Dojo_Data from JSON
Adding metadata to your containersSome Dojo components require additional metadata along with the dojo.data payload. As an example, dojox.grid.Grid can pull data dynamically from a dojox.data.QueryReadStore. For pagination to work correctly, each return payload should contain a numRows key with the total number of rows that could be returned by the query. With this data, the grid knows when to continue making small requests to the server for subsets of data and when to stop making more requests (i.e., it has reached the last page of data). This technique is useful for serving large sets of data in your grids without loading the entire set at once. Zend_Dojo_Data allows assigning metadata properties as to the object. The following illustrates usage:
Advanced Use CasesBesides acting as a serializable data container, Zend_Dojo_Data also provides the ability to manipulate and traverse the data in a variety of ways. Zend_Dojo_Data implements the interfaces ArrayAccess, Iterator, and Countable. You can therefore use the data collection almost as if it were an array. All items are referenced by the identifier field. Since identifiers must be unique, you can use the values of this field to pull individual records. There are two ways to do this: with the getItem() method, or via array notation.
If you know the identifier, you can use it to retrieve an item, update it, delete it, create it, or test for it:
You can loop over all items as well. Internally, all items are stored as arrays.
Or even count to see how many items you have:
Finally, as the class implements __toString(), you can also cast it to JSON simply by echoing it or casting to string:
Available MethodsBesides the methods necessary for implementing the interfaces listed above, the following methods are available.
|