[DOC] qweb rationale
bzr revid: al@openerp.com-20121208084846-1g1oksufswazkvko
This commit is contained in:
parent
a325343c42
commit
a2508290c2
|
@ -12,17 +12,18 @@ Contents:
|
|||
:maxdepth: 1
|
||||
|
||||
module
|
||||
testing
|
||||
|
||||
widget
|
||||
|
||||
async
|
||||
rpc
|
||||
qweb
|
||||
client_action
|
||||
form_view
|
||||
|
||||
testing
|
||||
|
||||
search_view
|
||||
list_view
|
||||
form_view
|
||||
|
||||
changelog-7.0
|
||||
|
||||
|
|
|
@ -16,6 +16,11 @@ XML-based templating language, similar to `Genshi
|
|||
OpenERP Web (and it's possible to use :class:`~instance.web.Widget`
|
||||
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:
|
||||
|
||||
.. code-block:: xml
|
||||
|
|
Loading…
Reference in New Issue