8cc066173d
This commit changes the way assets are declared in Odoo modules. Before: assets were declared in template files. Template bundles were generated from primary templates, so technically any qweb template could have been called as an asset bundle, with the 't-call-assets' directive. Being standard qweb templates, they had access to standard HTML tags (script, link, with or without raw scripts or style definition), qweb directives (t-call, t-raw, etc.) and could be inherited by other templates. Now: assets are defined in the module's manifest and generated by the 't-call-assets' directive. More information on the new system can be found on the updated user documentation (see the "JavaScript Reference" section). Task: 2352566 Co-authored-by: Bruno Boi <boi@odoo.com> Co-authored-by: Julien Mougenot <jum@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com> Co-authored-by: Raphael Collet <rco@odoo.com> Co-authored-by: Simon Genin <ges@odoo.com>
14 lines
551 B
XML
14 lines
551 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<record id="asset_view_form_inherit_website" model="ir.ui.view">
|
|
<field name="name">ir.asset.form.inherit.website</field>
|
|
<field name="model">ir.asset</field>
|
|
<field name="inherit_id" ref="base.asset_view_form"/>
|
|
<field name="arch" type="xml">
|
|
<field name="directive" position="after">
|
|
<field name="website_id" options="{'no_create': True}" groups="website.group_multi_website"/>
|
|
</field>
|
|
</field>
|
|
</record>
|
|
</odoo>
|