From a2508290c27054328a220ac4e90bbd9915485a87 Mon Sep 17 00:00:00 2001 From: Antony Lesuisse Date: Sat, 8 Dec 2012 09:48:46 +0100 Subject: [PATCH] [DOC] qweb rationale bzr revid: al@openerp.com-20121208084846-1g1oksufswazkvko --- addons/web/doc/index.rst | 7 ++++--- addons/web/doc/qweb.rst | 5 +++++ 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/addons/web/doc/index.rst b/addons/web/doc/index.rst index 2e4367ef78f..75a7194406e 100644 --- a/addons/web/doc/index.rst +++ b/addons/web/doc/index.rst @@ -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 diff --git a/addons/web/doc/qweb.rst b/addons/web/doc/qweb.rst index 47e5fe7d48f..61668dcb9be 100644 --- a/addons/web/doc/qweb.rst +++ b/addons/web/doc/qweb.rst @@ -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