Gorash
5410b7c238
XML files are now declared in python module manifests. During the qweb 't-call-asset' directive, assetbundle will fetch the declared xml files, apply the inheritance (t-inherit) and create a javascript service (for eg: 'web.assets_backend.bundle.xml') which is added at the end of the *.js mimifier file. When the debug mode is activated, comments are added in the template indicating which file the template comes from as well as the inheritances applied to it. **** JavaScript: assets.js (module @web/core/assets) takes care of loading libraries, javascripts and styles. `loadJS(url)` (loads the javascript and returns a resolved promise when the templates are also loaded via the '*.bundle.xml' service) `loadCSS(url)` (loads the style a resolved promise when the file is loaded) `loadXML(xml, app=assets.defaultApp)` (load template into application/owl, used by the `*.bundle.xml` services) `getBundle(bundleName)` (get the bundle descriptor) `loadBundle(desc)` (load the files and bundle from a descriptor) templates (XML element content all owl templates) A new `ready(serviceName)` method on boot.js lets you know when a service is loaded are the require. The xmlDependencies attribute no longer exists. Python: The xmls taken into account by assetbundle.py, applying `t-inherit` inheritances and adding an `name_of_the_bundle.bundle.xml` service in the generated JavaScript file. **** Every manifest changes is into the next commit, except 'web_tour' in this current commit as example. Part-of: odoo/odoo#95500
38 lines
1.8 KiB
XML
38 lines
1.8 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
|
|
<template id="project_sharing_portal" name="Project Sharing View in Portal">
|
|
<t t-call="portal.frontend_layout">
|
|
<t t-set="no_footer" t-value="true"/>
|
|
<t t-call="project.project_sharing"/>
|
|
</t>
|
|
</template>
|
|
|
|
<template id="project_sharing" name="Project Sharing View">
|
|
<!-- We need to forward the request lang to ensure that the lang set on the portal match the lang delivered -->
|
|
<iframe width="100%" height="100%" frameborder="0" t-attf-src="/{{ request.context['lang'] }}/my/projects/{{ str(project_id) }}/project_sharing{{ '?task_id=' + task_id if task_id else '' }}"/>
|
|
</template>
|
|
|
|
<template id="project_sharing_embed" name="Project Sharing View Embed">
|
|
<t t-call="web.layout">
|
|
<t t-set="head_project_sharing">
|
|
<script type="text/javascript">
|
|
odoo.__session_info__ = <t t-out="json.dumps(session_info)"/>;
|
|
// Prevent the menu_service to load anything. In an ideal world, Project Sharing assets would only contain
|
|
// what is genuinely necessary, and not the whole backend.
|
|
odoo.loadMenusPromise = Promise.resolve();
|
|
</script>
|
|
<base target="_parent"/>
|
|
<t t-call-assets="web.assets_common" t-js="false"/>
|
|
<t t-call-assets="project.webclient" t-js="false"/>
|
|
<t t-call-assets="web.assets_common" t-css="false"/>
|
|
<t t-call-assets="project.webclient" t-css="false"/>
|
|
<t t-call="web.conditional_assets_tests"/>
|
|
</t>
|
|
<t t-set="head" t-value="head_project_sharing + (head or '')"/>
|
|
<t t-set="body_classname" t-value="'o_web_client o_project_sharing'"/>
|
|
</t>
|
|
</template>
|
|
|
|
</odoo>
|