This module adds extensions in order to render available to the programmer a new tag in qweb views: "t-ignore-branding". Everything inside this tag will be ignored by the qweb evaluator, allowing the code to be evaluated on the fly.
The final result of this will be dynamic parameters in your widgets. This would allow widgets to be defined as "Show the last 5 entries of this model" or "Show all the data that has an attribute corresponding to the selected attibute". Widgets therefore will display parameter-dependant (1,2, or n parameters) information, and most importantly keep it updated on every pageload.
Creating a Parametric Snippet:
Create a normal snippet and in the snippet_body_section create a div that will contain the parametric part of the snippet content. Identify this div with a specific class, such as "parametricTemplate". This div will be empty ( we will inject via JS our template call code.)
Create a template stanza with the content of your snippet.
Create a snippet options entry with a data-snippet-option-id and a data-selector option.
Examples of modules that use this tag (will be updated)
website_snippet_blog_display_post <https://github.com/gfcapalbo/website/tree/8.0-website_snippet_blog_display_post>. website_twitter_no_ext_links <https://github.com/gfcapalbo/website/tree/8.0-website_twitter_no_ext_links> .
For further information, please visit:
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback here.
Thanks to Holger Brunn <email@example.com> for the parametric t tag idea.
Thanks to Laurent Mignon <firstname.lastname@example.org> for extending also website.qweb.field.html to render t-call elements inserted by snippets using the parametic approach and stored on the related model itself.
- Giovanni Francesco Capalbo <email@example.com>
- Holger Brunn <firstname.lastname@example.org>
- Laurent Mignon <email@example.com>
Do not contact contributors directly about help with questions or problems concerning this addon, but use the community mailing list or the appropriate specialized mailinglist for help, and the bug tracker linked in Bug Tracker above for technical issues.
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit https://odoo-community.org.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.