NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[IMP] settings: simplify the developer mode page

Browse Source 
task-3849915

closes odoo/documentation#9237

X-original-commit: e16a66706a
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit is contained in:
XPL
2024-05-02 14:43:58 +00:00
parent 4d8cba6f8a
commit ffcb7b2267
11 changed files with 53 additions and 87 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/developer/reference/backend/performance.rst
+4 -4
View File
@@ -40,7 +40,7 @@ including tests.
#. Before starting a profiling session, the profiler must be enabled globally on the database.
This can be done in two ways:
- Open the :ref:`developer mode tools <developer-mode/mode-tools>`, then toggle the
- Open the :ref:`developer mode tools <developer-mode/tools>`, then toggle the
:guilabel:`Enable profiling` button. A wizard suggests a set of expiry times for the
profiling. Click on :guilabel:`ENABLE PROFILING` to enable the profiler globally.
@@ -51,7 +51,7 @@ including tests.
#. After the profiler is enabled on the database, users can enable it on their session. To do
so, toggle the :guilabel:`Enable profiling` button in the :ref:`developer mode tools
<developer-mode/mode-tools>` again. By default, the recommended options :guilabel:`Record
<developer-mode/tools>` again. By default, the recommended options :guilabel:`Record
sql` and :guilabel:`Record traces` are enabled. To learn more about the different options,
head over to :ref:`performance/profiling/collectors`.
@@ -127,7 +127,7 @@ Analyse the results
To browse the profiling results, make sure that the :ref:`profiler is enabled globally on the
database <performance/profiling/enable>`, then open the :ref:`developer mode tools
<developer-mode/mode-tools>` and click on the button in the top-right corner of the profiling
<developer-mode/tools>` and click on the button in the top-right corner of the profiling
section. A list view of the `ir.profile` records grouped by profiling session opens.
.. image:: performance/profiling_web.png
@@ -172,7 +172,7 @@ Whereas the profiler is about the *when* of profiling, the collectors take care
Each collector specializes in collecting profiling data in its own format and manner. They can be
individually enabled from the user interface through their dedicated toggle button in the
:ref:`developer mode tools <developer-mode/mode-tools>`, or from Python code through their key or
:ref:`developer mode tools <developer-mode/tools>`, or from Python code through their key or
class.
There are currently four collectors available in Odoo:
content/developer/tutorials/discover_js_framework/01_owl_components.rst
+2 -2
View File
@@ -91,8 +91,8 @@ As a first exercise, let us modify the `Playground` component located in
.. tip::
The Odoo JavaScript files downloaded by the browser are minified. For debugging purpose, it's
easier when the files are not minified. Switch to
:ref:`debug mode with assets <developer-mode/url>` so that the files are not minified.
easier when the files are not minified. Switch to :ref:`debug mode with assets
<developer-mode/activation>` so that the files are not minified.
This exercise showcases an important feature of Owl: the `reactivity system <{OWL_PATH}/doc/reference/reactivity.md>`_.
The `useState` function wraps a value in a proxy so Owl can keep track of which component