<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/web/models/__init__.py, branch 14.0</title>
<subtitle>The current checkout of upstream Odoo</subtitle>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/'/>
<entry>
<title>[IMP] base: Document layout preview improvements</title>
<updated>2020-09-01T08:58:40+00:00</updated>
<author>
<name>Simon Genin (ges)</name>
<email>ges@odoo.com</email>
</author>
<published>2020-07-30T20:21:03+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=c121a246f16899735306266a3a12b526e08e7620'/>
<id>c121a246f16899735306266a3a12b526e08e7620</id>
<content type='text'>
The document layout preview is a complete defferent simplified template
with its own css that replicates at best the different styles.
It does not have the external layout features and lack of fidelity.

The new preview actually use the real documents templates and put the
result in an iframe. It now has a high fidelity, though not perfect.

The goal is for a better onboarding, where clients see easely how
documents will look if they had an app to generate them. Of course, the
data on the document is a false invoice.

Refactor all this from base to web.

Task ID 2304177

closes odoo/odoo#56415

Signed-off-by: Lucas Perais (lpe) &lt;lpe@odoo.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The document layout preview is a complete defferent simplified template
with its own css that replicates at best the different styles.
It does not have the external layout features and lack of fidelity.

The new preview actually use the real documents templates and put the
result in an iframe. It now has a high fidelity, though not perfect.

The goal is for a better onboarding, where clients see easely how
documents will look if they had an app to generate them. Of course, the
data on the document is a false invoice.

Refactor all this from base to web.

Task ID 2304177

closes odoo/odoo#56415

Signed-off-by: Lucas Perais (lpe) &lt;lpe@odoo.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] base: Configure document layout</title>
<updated>2019-07-29T08:29:26+00:00</updated>
<author>
<name>Julien Mougenot</name>
<email>jum@odoo.com</email>
</author>
<published>2019-07-18T15:18:41+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=ed18095127b20da516fa5ada943b2dd6d5c84652'/>
<id>ed18095127b20da516fa5ada943b2dd6d5c84652</id>
<content type='text'>
The onboarding modal for setting up the few base fields of a company
has now been moved to a wizard
It is accessible from the general settings, but also in the onboarding
section of sale and account modules.

The following company settings are editable with that wizard:

- Set report **layout**:
The user can chose the overall look of the report. The current choices
are : *Standard* (default), *Background*, *Boxed* and *Clean*.

- Set company **logo**:
Changes the company logo.

- Set report **colors**:
The user can set the primary and secondary colors of the report through
a newly added widget allowing to pick a custom color.
When changing the **logo**, colors are automatically set to its most dominant
colors.
&gt; A "Reset colors" button also triggers the color calculation.

- Set report **font**:
Changes the overall font of the report. Only Google Fonts are used
for enhanced compatibility.

- Company **tagline**, also called "header"
- **Footer**
- **Paper format**
- Report **preview**:
A mockup of a final report
Automatically updates when changing **layout**, **logo**, **colors** or **font**

Co-authored by: Julien Mougenot &lt;jum@odoo.com&gt;

closes odoo/odoo#33863

Signed-off-by: VincentSchippefilt &lt;VincentSchippefilt@users.noreply.github.com&gt;


Co-authored-by: Lucas Perais &lt;lpe@odoo.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The onboarding modal for setting up the few base fields of a company
has now been moved to a wizard
It is accessible from the general settings, but also in the onboarding
section of sale and account modules.

The following company settings are editable with that wizard:

- Set report **layout**:
The user can chose the overall look of the report. The current choices
are : *Standard* (default), *Background*, *Boxed* and *Clean*.

- Set company **logo**:
Changes the company logo.

- Set report **colors**:
The user can set the primary and secondary colors of the report through
a newly added widget allowing to pick a custom color.
When changing the **logo**, colors are automatically set to its most dominant
colors.
&gt; A "Reset colors" button also triggers the color calculation.

- Set report **font**:
Changes the overall font of the report. Only Google Fonts are used
for enhanced compatibility.

- Company **tagline**, also called "header"
- **Footer**
- **Paper format**
- Report **preview**:
A mockup of a final report
Automatically updates when changing **layout**, **logo**, **colors** or **font**

Co-authored by: Julien Mougenot &lt;jum@odoo.com&gt;

closes odoo/odoo#33863

Signed-off-by: VincentSchippefilt &lt;VincentSchippefilt@users.noreply.github.com&gt;


Co-authored-by: Lucas Perais &lt;lpe@odoo.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] base, *: use a many2one for the company report layout</title>
<updated>2018-08-13T15:09:28+00:00</updated>
<author>
<name>Christophe Matthieu</name>
<email>chm@odoo.com</email>
</author>
<published>2018-07-26T07:55:01+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=61eef73b52c078daaae37f8d57e93830a2e53410'/>
<id>61eef73b52c078daaae37f8d57e93830a2e53410</id>
<content type='text'>
Before this rev. one could set the report layout on the company using a
hardcoded list (background, clean, standard, etc.). Other modules (typically
accounting modules) could add options in this list. The used template was built
on the layout key.

Now, the layout is a many2one field to a newly created model `report.layout`,
which is linked to a view with the layout architecture.

This gives more control to customize reports and create a new layout (without
creating a python module that extend the layout selection).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Before this rev. one could set the report layout on the company using a
hardcoded list (background, clean, standard, etc.). Other modules (typically
accounting modules) could add options in this list. The used template was built
on the layout key.

Now, the layout is a many2one field to a newly created model `report.layout`,
which is linked to a view with the layout architecture.

This gives more control to customize reports and create a new layout (without
creating a python module that extend the layout selection).
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] web, *: add kanban column progress bars</title>
<updated>2017-09-14T21:48:56+00:00</updated>
<author>
<name>qsm-odoo</name>
<email>qsm@odoo.com</email>
</author>
<published>2017-09-14T20:43:43+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=33f9e90bd5a9ad3e9239f1b414ea012bb94fa1c0'/>
<id>33f9e90bd5a9ad3e9239f1b414ea012bb94fa1c0</id>
<content type='text'>
* crm, project

Add a new feature which allows to put a progressbar in the kanban
columns. The progressbar shows with the same color the amount of
records whose value of a given field are the same in the column.
It also indicate the sum of another given field or simply the total
number of records. It also allows to subgroup the column content.

To define a progressbar, add this as a direct child of the kanban
arch:

&lt;progressbar field="&lt;name of the field to use for subgroups&gt;"
             colors="{&lt;one possible value for the above field&gt;: &lt;success, warning or danger&gt;, ...}"
             sum="&lt;name of the field to sum or nothing to use total number of records&gt;"/&gt;

Also:
- Properly update record model data's parentID when moving a record
- ...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* crm, project

Add a new feature which allows to put a progressbar in the kanban
columns. The progressbar shows with the same color the amount of
records whose value of a given field are the same in the column.
It also indicate the sum of another given field or simply the total
number of records. It also allows to subgroup the column content.

To define a progressbar, add this as a direct child of the kanban
arch:

&lt;progressbar field="&lt;name of the field to use for subgroups&gt;"
             colors="{&lt;one possible value for the above field&gt;: &lt;success, warning or danger&gt;, ...}"
             sum="&lt;name of the field to sum or nothing to use total number of records&gt;"/&gt;

Also:
- Properly update record model data's parentID when moving a record
- ...
</pre>
</div>
</content>
</entry>
<entry>
<title>[MOV] web(_editor): move image rendering from web_editor to web</title>
<updated>2017-08-24T15:06:07+00:00</updated>
<author>
<name>Thibault Delavallée</name>
<email>tde@odoo.com</email>
</author>
<published>2017-08-23T12:40:54+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=50f5d28c80527027b7591f091822a1e7cad6b19b'/>
<id>50f5d28c80527027b7591f091822a1e7cad6b19b</id>
<content type='text'>
Currently the image field rendering in QWeb using the /web/image
controller is done in web_editor. However there is no link between
the web editor and the rendering. The rendering can therefore be moved
directly in web.

During the move two options have been added to the rendering of image
field :

 * qweb_img_raw_data: fallback on standard base64 behavior that is
   otherwise impossible to achieve;
 * qweb_img_responsive: True by default, add the img-responsive
   class that is not always requested;

Thanks.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently the image field rendering in QWeb using the /web/image
controller is done in web_editor. However there is no link between
the web editor and the rendering. The rendering can therefore be moved
directly in web.

During the move two options have been added to the rendering of image
field :

 * qweb_img_raw_data: fallback on standard base64 behavior that is
   otherwise impossible to achieve;
 * qweb_img_responsive: True by default, add the img-responsive
   class that is not always requested;

Thanks.
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] Various P3-related import changes</title>
<updated>2017-04-28T07:06:53+00:00</updated>
<author>
<name>xmo-odoo</name>
<email>xmo@odoo.com</email>
</author>
<published>2017-04-28T07:06:53+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=b4429c2a91889bf60b56e0c7909c844d357363f7'/>
<id>b4429c2a91889bf60b56e0c7909c844d357363f7</id>
<content type='text'>
* LDAP import: python-ldap is not python3-compatible, pyldap is

  Warning: only supported from debian Stretch (current testing)?
  https://packages.debian.org/search?searchon=names&amp;keywords=pyldap

* implicitly relative imports
* imports of moved or removed stdlib modules

issue #8530
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* LDAP import: python-ldap is not python3-compatible, pyldap is

  Warning: only supported from debian Stretch (current testing)?
  https://packages.debian.org/search?searchon=names&amp;keywords=pyldap

* implicitly relative imports
* imports of moved or removed stdlib modules

issue #8530
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] web: remove void file, replace openerp tags, add license, clean imports</title>
<updated>2016-08-03T11:42:00+00:00</updated>
<author>
<name>fwi-odoo</name>
<email>fwi@odoo.com</email>
</author>
<published>2016-07-20T13:00:17+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=7d487c00a679980b96409e261322f93ba3e340f2'/>
<id>7d487c00a679980b96409e261322f93ba3e340f2</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[REF] point_of_sale,web(site): move session info into page source</title>
<updated>2016-05-30T07:23:07+00:00</updated>
<author>
<name>Géry Debongnie</name>
<email>ged@odoo.com</email>
</author>
<published>2016-05-25T10:18:48+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=9c68bc74827864a3c6c21be8ead1b2ed3d122d73'/>
<id>9c68bc74827864a3c6c21be8ead1b2ed3d122d73</id>
<content type='text'>
This commit introduces a mechanism to add information into the session
from a different module, without having to fetch it manually with a rpc.
This is intended to be used with small pieces of info required at the
start of the web client, such as currency informations.

To add information to the session, one can simply inherit from ir.http
and modify the session_info method.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This commit introduces a mechanism to add information into the session
from a different module, without having to fetch it manually with a rpc.
This is intended to be used with small pieces of info required at the
start of the web client, such as currency informations.

To add information to the session, one can simply inherit from ir.http
and modify the session_info method.
</pre>
</div>
</content>
</entry>
</feed>
