QWeb templates that show up in the 'qweb' key of a module's manifest now support server side inheritance and xpath evaluation QWeb templates that show up in the xmlDependencies of a JS widget are not impacted at all by theses changes, as they are served through the Werkzeug sharedMiddleware A similar syntax than ir.ui.view has been implemented in the QWeb templates - each template must have a root node, whatever tag works - the root node of a template must have a t-name containing the name of the template The name -- without the module's name -- may contain dots pretty much anywhere Though what is recommended is only underscores in template names - if a template is to inherit from a parent, the root node has a t-inherit directive containing either the full name of the template it inherits from which is module_name.template_name or the name of the template, no module name necessary, if the parent template is in the same module - there are 2 modes of inheriting primary: copy the behavior of the parent into the template extension: modifies the parent in place Task: 1999528 closes odoo/odoo#33892 Signed-off-by: VincentSchippefilt <VincentSchippefilt@users.noreply.github.com> Co-authored-by: Julien Mougenot <jum@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com>
21 lines
520 B
Python
21 lines
520 B
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from . import pycompat
|
|
from . import win32
|
|
from . import appdirs
|
|
from . import pdf
|
|
from .config import config
|
|
from .misc import *
|
|
from .translate import *
|
|
from .graph import graph
|
|
from .image import *
|
|
from .sql import *
|
|
from .float_utils import *
|
|
from .mail import *
|
|
from .func import *
|
|
from .debugger import *
|
|
from .xml_utils import *
|
|
from .date_utils import *
|
|
from .convert import *
|
|
from .template_inheritance import * |