1 | ------------------------------------------------------------------------------- |
---|
2 | Project Name: dojox.mvc |
---|
3 | ------------------------------------------------------------------------------- |
---|
4 | Version 0.1 |
---|
5 | Release date: May 16th, 2011 |
---|
6 | ------------------------------------------------------------------------------- |
---|
7 | Project state: experimental (code and API subject to change in future releases) |
---|
8 | ------------------------------------------------------------------------------- |
---|
9 | Credits: |
---|
10 | Rahul Akolkar (original author) |
---|
11 | Ed Chatelain |
---|
12 | Charlie Wiecha |
---|
13 | |
---|
14 | ------------------------------------------------------------------------------- |
---|
15 | Project description: |
---|
16 | |
---|
17 | Enterprise Rich Internet Applications (RIAs) often focus more on rich data |
---|
18 | vs. the rich media aspects of RIAs more typical of consumer applications. |
---|
19 | For example, such RIAs depend on implementing the well-known CRUD operations |
---|
20 | on data stored in back-end systems. The dojox.mvc project focuses on |
---|
21 | separation of MVC concerns on the client, thereby on easing development |
---|
22 | of data-rich applications and accelerating the authoring of applications to |
---|
23 | Create, Read, Update, and Delete data using a set of Dojo-based patterns. |
---|
24 | |
---|
25 | This project is useful across form factors. For example, it may be used with |
---|
26 | dijit as well as dojox.mobile. |
---|
27 | |
---|
28 | We begin by introducing a first-class client-side data model based on |
---|
29 | dojo.Stateful and extending Dojo Form widgets with support for the |
---|
30 | Model-View-Control (MVC) pattern key to separating data from presentation in |
---|
31 | user interface design. This basic MVC pattern allows for the flexible reuse of |
---|
32 | each of the Model, View, and Control artifacts by application authors in |
---|
33 | varying configurations. |
---|
34 | |
---|
35 | We also add support for a set of commonly needed MVC widgets and containers |
---|
36 | such as: |
---|
37 | - Output: a data-bound output widget |
---|
38 | - Group: an aggregation of widgets with the same parent data binding context |
---|
39 | - Repeat: a model-bound repeater widget that binds to a data collection |
---|
40 | - Generate: an example of UI generation from a supplied data model |
---|
41 | |
---|
42 | For more, see descriptive class documentation at the top of the following |
---|
43 | files: |
---|
44 | dojox/mvc/StatefulModel.js |
---|
45 | dojox/mvc/_DataBindingMixin.js |
---|
46 | |
---|
47 | For an introductory page on the included samples, see: |
---|
48 | dojox/mvc/tests/mvc_index.html |
---|
49 | |
---|
50 | For mobile demos, see: |
---|
51 | dojox/mvc/tests/mobile/demo/demo.html |
---|
52 | |
---|
53 | ------------------------------------------------------------------------------- |
---|
54 | Dependencies: |
---|
55 | |
---|
56 | Dojo Core (base, dojo.Stateful) |
---|
57 | Dijit (dijit._WidgetBase, dijit.form.*) |
---|
58 | |
---|
59 | ------------------------------------------------------------------------------- |
---|
60 | Documentation: |
---|
61 | |
---|
62 | Documentation resides at: |
---|
63 | http://dojotoolkit.org/reference-guide/dojox/mvc.html |
---|
64 | |
---|
65 | ------------------------------------------------------------------------------- |
---|
66 | Installation instructions: |
---|
67 | |
---|
68 | Grab the following from the Dojo SVN Repository: |
---|
69 | http://svn.dojotoolkit.org/src/dojox/trunk/mvc.js |
---|
70 | http://svn.dojotoolkit.org/src/dojox/trunk/mvc/* |
---|
71 | |
---|
72 | Install into the following directory structure: |
---|
73 | /dojox/mvc.js |
---|
74 | /dojox/mvc/* |
---|
75 | |
---|
76 | ...which should be at the same level as your Dojo checkout. |
---|
77 | |
---|
78 | then dojo.require("dojox.mvc") in your application to load basic support for |
---|
79 | data bindings. Other components (such as MVC containers i.e. Group, Repeat) |
---|
80 | should be required as per application need. |
---|
81 | |
---|
82 | ------------------------------------------------------------------------------- |
---|