8ef0514ad1
This PR updates javascript code to be up to date with the codebase standards: - use the `static` keyword when possible - proper owl imports - removed unecessary `@odoo-module` directives Task ID: 2258359 closes odoo/documentation#11466 Signed-off-by: Bastien Fafchamps (bafa) <bafa@odoo.com>
48 lines
1.5 KiB
ReStructuredText
48 lines
1.5 KiB
ReStructuredText
|
|
.. _howtos/javascript_client_action:
|
|
|
|
======================
|
|
Create a client action
|
|
======================
|
|
|
|
A client action triggers an action that is entirely implemented in the client side.
|
|
One of the benefits of using a client action is the ability to create highly customized interfaces
|
|
with ease. A client action is typically defined by an OWL component; we can also use the web
|
|
framework and use services, core components, hooks,...
|
|
|
|
#. Create the :ref:`client action <reference/actions/client>`, don't forget to
|
|
make it accessible.
|
|
|
|
.. code-block:: xml
|
|
|
|
<record model="ir.actions.client" id="my_client_action">
|
|
<field name="name">My Client Action</field>
|
|
<field name="tag">my_module.MyClientAction</field>
|
|
</record>
|
|
|
|
#. Create a component that represents the client action.
|
|
|
|
.. code-block:: js
|
|
:caption: :file:`my_client_action.js`
|
|
|
|
import { registry } from "@web/core/registry";
|
|
|
|
import { Component } from "@odoo/owl";
|
|
|
|
class MyClientAction extends Component {
|
|
static template = "my_module.clientaction";
|
|
}
|
|
|
|
// remember the tag name we put in the first step
|
|
registry.category("actions").add("my_module.MyClientAction", MyClientAction);
|
|
|
|
.. code-block:: xml
|
|
:caption: :file:`my_client_action.xml`
|
|
|
|
<?xml version="1.0" encoding="UTF-8" ?>
|
|
<templates xml:space="preserve">
|
|
<t t-name="awesome_tshirt.clientaction">
|
|
Hello world
|
|
</t>
|
|
</templates>
|