11 components (called `cubes`) and following the well known object-oriented design |
11 components (called `cubes`) and following the well known object-oriented design |
12 principles. |
12 principles. |
13 |
13 |
14 Its main features are: |
14 Its main features are: |
15 |
15 |
16 * an engine driven by the explicit :ref:`data model <DefineDataModel>` of the application, |
16 * an engine driven by the explicit :ref:`data model |
|
17 <TutosBaseCustomizingTheApplicationDataModel>` of the application, |
|
18 |
17 * a query language named :ref:`RQL <RQL>` similar to W3C's SPARQL, |
19 * a query language named :ref:`RQL <RQL>` similar to W3C's SPARQL, |
18 * a :ref:`selection+view <DefineViews>` mechanism for semi-automatic XHTML/XML/JSON/text generation, |
20 |
19 * a library of reusable :ref:`components <cubes>` (data model and views) that fulfill common needs, |
21 * a :ref:`selection+view <TutosBaseCustomizingTheApplicationCustomViews>` |
|
22 mechanism for semi-automatic XHTML/XML/JSON/text generation, |
|
23 |
|
24 * a library of reusable :ref:`components <Cube>` (data model and views) that |
|
25 fulfill common needs, |
|
26 |
20 * the power and flexibility of the Python_ programming language, |
27 * the power and flexibility of the Python_ programming language, |
21 * the reliability of SQL databases, LDAP directories, Subversion and Mercurial for storage backends. |
28 |
|
29 * the reliability of SQL databases, LDAP directories, Subversion and Mercurial |
|
30 for storage backends. |
22 |
31 |
23 Built since 2000 from an R&D effort still continued, supporting 100,000s of |
32 Built since 2000 from an R&D effort still continued, supporting 100,000s of |
24 daily visits at some production sites, |cubicweb| is a proven end to end solution |
33 daily visits at some production sites, |cubicweb| is a proven end to end solution |
25 for semantic web application development that promotes quality, reusability and |
34 for semantic web application development that promotes quality, reusability and |
26 efficiency. |
35 efficiency. |
27 |
36 |
28 The unbeliever will read the :ref:`Tutorial`. |
37 The unbeliever will read the :ref:`Tutorials`. |
29 |
38 |
30 The hacker will join development at the forge_. |
39 The hacker will join development at the forge_. |
31 |
40 |
32 The impatient developer will move right away to :ref:`SetUpEnv`. |
41 The impatient developer will move right away to :ref:`SetUpEnv`. |
33 |
42 |