Nicolas Bayet
4813f42997
Jinja as a templating engine was problematic in differents respect:
- introduce external dependency to Odoo (less controll)
- add another templating mechanism in the stack
- specific feature in qweb cannot be reused
- difficulty in rendering easily editable templates
- more knowledge required with no betterment
By replacing jinja with qweb we can now build tools to edit a qweb
that will work with the previously jinja encoded document
(essentially `mail.template` records).
There is a catch however. Some email fields (eg. email_to) used jinja
syntax for rendering dynamic variables (ie. ${object.something} and
${object.something_that_should_not_be_escaped | safe}).
We still want user to use dynamic variables for some char fields (eg.
subject, from, to, ...). We made a new rendering engine called
"inline_template" that will render an expression enclosed by `{{` and
`}}`.
To be able to edit the templates from the backend interface, a
plugin to the Odoo editor has been made for seamlessly edit the
document.
This qweb plugin includes:
- make dynamic variables (eg. `<t t-out="variable"/>`) not editable
(for preventing the user to shoot himself in the foot)
- group and hide related logical branching (ie. t-if, t-elif, and t-else)
in order to see only one at once
- a floating select input to switch visibility of a particular logical
branching
Task-27033
X-original-commit: odoo/odoo@68182baff4
Part-of: odoo/odoo#77377
29 lines
1.3 KiB
XML
29 lines
1.3 KiB
XML
<?xml version='1.0' encoding='utf-8'?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<record id="digest.digest_digest_default" model="digest.digest">
|
|
<field name="kpi_hr_recruitment_new_colleagues">True</field>
|
|
</record>
|
|
</data>
|
|
|
|
<data>
|
|
<record id="digest_tip_hr_recruitment_0" model="digest.tip">
|
|
<field name="name">Tip: Let candidates apply by email</field>
|
|
<field name="sequence">1300</field>
|
|
<field name="group_id" ref="hr_recruitment.group_hr_recruitment_manager" />
|
|
<field name="tip_description" type="html">
|
|
<div>
|
|
<p class="tip_title">Tip: Let candidates apply by email</p>
|
|
<p class="tip_content">
|
|
By setting an alias to a job position, emails sent to this address create applications automatically. You can even use multiple trackers to get statistics according to the source of the application: LinkedIn, Monster, Indeed, etc.
|
|
<t t-set="record" t-value="object.env['hr.job'].search([('alias_name', '!=', False)], limit=1)" />
|
|
<t t-if="record and record.alias_domain">
|
|
<a t-attf-href="mailto:{{record.alias_id.display_name}}" target="_blank" style="color: #875a7b; text-decoration: none;">Try sending an email</a>
|
|
</t>
|
|
</p>
|
|
</div>
|
|
</field>
|
|
</record>
|
|
</data>
|
|
</odoo>
|