odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity

[DOC] qweb rationale 

bzr revid: al@openerp.com-20121208084846-1g1oksufswazkvko
This commit is contained in:
Antony Lesuisse 2012-12-08 09:48:46 +01:00
parent a325343c42
commit a2508290c2
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
addons/web/doc/index.rst
View File

@ -12,17 +12,18 @@ Contents:
:maxdepth: 1 :maxdepth: 1
module module
testing
widget widget
async async
rpc rpc
qweb qweb
client_action client_action
form_view
testing
search_view search_view
list_view list_view
form_view
changelog-7.0 changelog-7.0

5
addons/web/doc/qweb.rst
View File

@ -16,6 +16,11 @@ XML-based templating language, similar to `Genshi
OpenERP Web (and it's possible to use :class:`~instance.web.Widget` OpenERP Web (and it's possible to use :class:`~instance.web.Widget`
without relying on the QWeb integration). without relying on the QWeb integration).
The rationale behind using QWeb instead of a more popular template syntax is
that its extension mechanism is very similar to the openerp view inheritance
mechanism. Like openerp views a QWeb template is an xml tree and therefore
xpath or dom manipulations are easy to performs on it.
Here's an example demonstrating most of the basic QWeb features: Here's an example demonstrating most of the basic QWeb features:
.. code-block:: xml .. code-block:: xml