+
+\
diff --git a/base_comment_template/readme/USAGE.rst b/base_comment_template/readme/USAGE.rst
deleted file mode 100644
index 30343d7ae..000000000
--- a/base_comment_template/readme/USAGE.rst
+++ /dev/null
@@ -1,44 +0,0 @@
-#. Go to *Settings* and activate the developer mode.
-#. Go to *Settings > Technical > Reporting > Comment Templates*.
-#. Create a new record.
-#. Define the Company the template is linked or leave default for all companies.
-#. Define the Partner the template is linked or leave default for all partners.
-#. Define the Model, Domain the template is linked.
-#. Define the Position where the template will be printed:
-
- * above document lines
- * below document lines
-
-You should have at least one template with Default field set, if you choose a Partner the template is deselected as a Default one.
-If you create a new template with the same configuration (Model, Domain, Position) and set it as Default, the previous one will be deselected as a default one.
-
-The template is a html field which will be rendered just like a mail template, so you can use variables like {{object}}, {{user}}, {{ctx}} to add dynamic content.
-
-Change the report related to the model from configuration and add a statement like:
-
-
-
-
-
-
-
-
-
-
-
-
-You should always use t-if since the method returns False if no template is found.
-
-If you want to use Qweb templates, or different context, you can specify it just like in
-mail.render.mixin with parameters:
-
-- engine: "inline_template", "qweb" or "qweb_view",
-- add_context: dict with your own context,
-- post_process: perform a post processing on rendered result
-
-so you could use it :
-
-
-
-
-
diff --git a/base_comment_template/static/description/index.html b/base_comment_template/static/description/index.html
index 04b9ea851..487b5e8f0 100644
--- a/base_comment_template/static/description/index.html
+++ b/base_comment_template/static/description/index.html
@@ -8,10 +8,11 @@
/*
:Author: David Goodger (goodger@python.org)
-:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $
+:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
+Despite the name, some widely supported CSS2 features are used.
See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to
customize this style sheet.
@@ -274,7 +275,7 @@ pre.literal-block, pre.doctest-block, pre.math, pre.code {
margin-left: 2em ;
margin-right: 2em }
-pre.code .ln { color: grey; } /* line numbers */
+pre.code .ln { color: gray; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
@@ -300,7 +301,7 @@ span.option {
span.pre {
white-space: pre }
-span.problematic {
+span.problematic, pre.problematic {
color: red }
span.section-subtitle {
@@ -368,20 +369,25 @@ ul.auto-toc {
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:72251979ce578742037aa71ca933ba9c4ed9951b7e3f68951ca232766f72d000
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
-
-
Add a new mixin class to define templates of comments to print on documents.
-The comment templates can be defined like make templates, so you can use variables from linked models.
+
+
Add a new mixin class to define templates of comments to print on
+documents. The comment templates can be defined like make templates, so
+you can use variables from linked models.
Two positions are available for the comments:
- above document lines (before_lines)
- below document lines (after_lines)
-
The template are general, and can be attached to any Model and based on some domain defined in the template.
-You can define one default template per Model and domain, which can be overwritten for any company and partners.
-It has a priority field (smaller number = higher priority)
-
In existing reports, if you add this line will get the comment template if you created one like
+
The template are general, and can be attached to any Model and based on
+some domain defined in the template. You can define one default template
+per Model and domain, which can be overwritten for any company and
+partners. It has a priority field (smaller number = higher priority)
+
In existing reports, if you add this line will get the comment template
+if you created one like
-- <span t-out=”o.get_comment_template(‘position’,company_id=o.company_id, partner_id=o.parnter_id )”/> ( or without any parameter)
+- <span
+t-out=”o.get_comment_template(‘position’,company_id=o.company_id,
+partner_id=o.parnter_id )”/> ( or without any parameter)
This module is the base module for following modules:
@@ -406,7 +412,8 @@ It has a priority field (smaller number = higher priority)
-
Go to Settings > Technical > Reporting > Comment Templates and start designing you comment templates.
+
Go to Settings > Technical > Reporting > Comment Templates and start
+designing you comment templates.
This module is the base module for following modules:
- sale_comment_template
@@ -421,8 +428,10 @@ It has a priority field (smaller number = higher priority)
- Go to Settings and activate the developer mode.
- Go to Settings > Technical > Reporting > Comment Templates.
- Create a new record.
-- Define the Company the template is linked or leave default for all companies.
-- Define the Partner the template is linked or leave default for all partners.
+- Define the Company the template is linked or leave default for all
+companies.
+- Define the Partner the template is linked or leave default for all
+partners.
- Define the Model, Domain the template is linked.
- Define the Position where the template will be printed:
- above document lines
@@ -430,33 +439,44 @@ It has a priority field (smaller number = higher priority)
-You should have at least one template with Default field set, if you choose a Partner the template is deselected as a Default one.
-If you create a new template with the same configuration (Model, Domain, Position) and set it as Default, the previous one will be deselected as a default one.
-The template is a html field which will be rendered just like a mail template, so you can use variables like {{object}}, {{user}}, {{ctx}} to add dynamic content.
-Change the report related to the model from configuration and add a statement like:
-
-- <t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘before_lines’)” t-as=”comment_template_top”>
-- <div t-out=”o.render_comment(comment_template_top)” />
-
+You should have at least one template with Default field set, if you
+choose a Partner the template is deselected as a Default one. If you
+create a new template with the same configuration (Model, Domain,
+Position) and set it as Default, the previous one will be deselected as
+a default one.
+The template is a html field which will be rendered just like a mail
+template, so you can use variables like {{object}}, {{user}}, {{ctx}} to
+add dynamic content.
+Change the report related to the model from configuration and add a
+statement like:
+
+
<t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position ==
+‘before_lines’)” t-as=”comment_template_top”>
+
<div t-out=”o.render_comment(comment_template_top)” />
+
</t>
-
-- <t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘after_lines’)” t-as=”comment_template_bottom”>
-- <div t-out=”o.render_comment(comment_template_bottom)” />
-
+
+
<t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position ==
+‘after_lines’)” t-as=”comment_template_bottom”>
+
<div t-out=”o.render_comment(comment_template_bottom)” />
+
</t>
-You should always use t-if since the method returns False if no template is found.
-If you want to use Qweb templates, or different context, you can specify it just like in
-mail.render.mixin with parameters:
+You should always use t-if since the method returns False if no template
+is found.
+If you want to use Qweb templates, or different context, you can specify
+it just like in mail.render.mixin with parameters:
- engine: “inline_template”, “qweb” or “qweb_view”,
- add_context: dict with your own context,
- post_process: perform a post processing on rendered result
so you could use it :
-
-- <t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position == ‘before_lines’)” t-as=”comment_template_top”>
-- <div t-out=”o.render_comment(comment_template_top, engine=’qweb’, add_context={my dict}, postprocess=True)” />
-
+
+
<t t-foreach=”o.comment_template_ids.filtered(lambda x: x.position ==
+‘before_lines’)” t-as=”comment_template_top”>
+
<div t-out=”o.render_comment(comment_template_top, engine=’qweb’,
+add_context={my dict}, postprocess=True)” />
+
</t>
+
+