<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/gamification/static/src, 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] *: remove image_64 and clean views</title>
<updated>2019-09-19T10:23:39+00:00</updated>
<author>
<name>Sébastien Theys</name>
<email>seb@odoo.com</email>
</author>
<published>2019-09-19T10:23:39+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=b6288e54461426d7aac6cfc549cee3e90309a093'/>
<id>b6288e54461426d7aac6cfc549cee3e90309a093</id>
<content type='text'>
There are too many image sizes. Since they are stored resized this takes time to
generate when saving a new image, it's more rows on the attachment table, more
files on the disk, ...

64px is close enough to 128px that it can be removed without a big impact on
download size.

It will even reduce download and number of requests when both images are
displayed because now only one has to be downloaded and then benefit from cache.

The difference between the two is typically around 1.5kB which is negligible
these days, especially when the request overhead is around 0.5kB already, not
even taking into account other factors such as latency.

If a 64px image must absolutely be returned, it is still possible to pass the
size parameters to the image route. But the current guideline is to handle
resizing in the views when necessary.

Views
=====

- remove width and height attributes when existing CSS rules are overriding them
  (eg. `.oe_kanban_avatar` in the right context)
- add CSS rules instead of width and height attributes when possible
- use `object-fit: cover;` where width and height are forced to avoid distortion
  of non-square images
- for products, use `object-fit: contain;` instead, keep ratio but without crop
- add new CSS rules where the expected size was max 64px*64px before due to the
  image size itself
- remove `img-fluid` where using size classes to avoid conflicting rules

task-2060865

closes odoo/odoo#36147

Signed-off-by: Sébastien Theys (seb) &lt;seb@odoo.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There are too many image sizes. Since they are stored resized this takes time to
generate when saving a new image, it's more rows on the attachment table, more
files on the disk, ...

64px is close enough to 128px that it can be removed without a big impact on
download size.

It will even reduce download and number of requests when both images are
displayed because now only one has to be downloaded and then benefit from cache.

The difference between the two is typically around 1.5kB which is negligible
these days, especially when the request overhead is around 0.5kB already, not
even taking into account other factors such as latency.

If a 64px image must absolutely be returned, it is still possible to pass the
size parameters to the image route. But the current guideline is to handle
resizing in the views when necessary.

Views
=====

- remove width and height attributes when existing CSS rules are overriding them
  (eg. `.oe_kanban_avatar` in the right context)
- add CSS rules instead of width and height attributes when possible
- use `object-fit: cover;` where width and height are forced to avoid distortion
  of non-square images
- for products, use `object-fit: contain;` instead, keep ratio but without crop
- add new CSS rules where the expected size was max 64px*64px before due to the
  image size itself
- remove `img-fluid` where using size classes to avoid conflicting rules

task-2060865

closes odoo/odoo#36147

Signed-off-by: Sébastien Theys (seb) &lt;seb@odoo.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] gamification, *: remove KarmaError</title>
<updated>2019-09-12T13:49:02+00:00</updated>
<author>
<name>fja-odoo</name>
<email>fja@odoo.com</email>
</author>
<published>2019-09-10T16:30:45+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=424adb63e3ecd9ce6888c3246633a6414215f34d'/>
<id>424adb63e3ecd9ce6888c3246633a6414215f34d</id>
<content type='text'>
* = stock, test_website, web, website_forum, website_slides, base

Replace KarmaError with AccessError and remove the related override made
on crash_manager and ir_http.

task-2069890

closes odoo/odoo#36655

Signed-off-by: Jérémy Kersten (jke) &lt;jke@openerp.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* = stock, test_website, web, website_forum, website_slides, base

Replace KarmaError with AccessError and remove the related override made
on crash_manager and ir_http.

task-2069890

closes odoo/odoo#36655

Signed-off-by: Jérémy Kersten (jke) &lt;jke@openerp.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] gamification, web: Edge does not support obj spread operator</title>
<updated>2019-08-28T08:50:56+00:00</updated>
<author>
<name>Alexandre Kühn</name>
<email>aku@odoo.com</email>
</author>
<published>2019-08-20T08:48:15+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=6f6445be8cdd52dbd99b958bfd9c1a54540484f9'/>
<id>6f6445be8cdd52dbd99b958bfd9c1a54540484f9</id>
<content type='text'>
As of August 20 2019, Microsoft Edge partially supports ECMA2018.
For instance, `Promise.prototype.finally()` can be used, but the
spread operator does not work on objects.

Task-ID 2056070</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
As of August 20 2019, Microsoft Edge partially supports ECMA2018.
For instance, `Promise.prototype.finally()` can be used, but the
spread operator does not work on objects.

Task-ID 2056070</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] gamification, web: separate gamification/crash_manager</title>
<updated>2019-07-30T16:00:05+00:00</updated>
<author>
<name>fja-odoo</name>
<email>fja@odoo.com</email>
</author>
<published>2019-07-25T09:26:39+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=09681e566013433157fd96818ed7b767a14ef758'/>
<id>09681e566013433157fd96818ed7b767a14ef758</id>
<content type='text'>
Fix for: https://github.com/odoo/odoo/pull/32132

A reference to gamification was still made in the crash_manager.

Part of: https://github.com/odoo/odoo/pull/35209</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix for: https://github.com/odoo/odoo/pull/32132

A reference to gamification was still made in the crash_manager.

Part of: https://github.com/odoo/odoo/pull/35209</pre>
</div>
</content>
</entry>
<entry>
<title>[REF] *: rename all LESS files to SCSS</title>
<updated>2018-04-18T13:59:15+00:00</updated>
<author>
<name>qsm-odoo</name>
<email>qsm@odoo.com</email>
</author>
<published>2018-03-12T15:27:41+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=b04dec4025013c60e4857c1e177bb20d811cd41a'/>
<id>b04dec4025013c60e4857c1e177bb20d811cd41a</id>
<content type='text'>
This is a simple renaming without adaptation.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is a simple renaming without adaptation.
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] gamification: several layout issues</title>
<updated>2016-03-21T13:02:10+00:00</updated>
<author>
<name>Keyur Gajjar</name>
<email>kga@odoo.com</email>
</author>
<published>2015-12-14T13:32:31+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=82e35bce6c4fa2e6dca98309f7a9483a9a719eb9'/>
<id>82e35bce6c4fa2e6dca98309f7a9483a9a719eb9</id>
<content type='text'>
1/ ISSUES WITH BADGES:
Go to menu Employees &gt; Badges &gt; Select any Badge from kanban View.
Click on "GRANT THIS BADGE" button.
- When you grant a badge, the description field is not at the right place.
  It should be below the employee field
- Badges Form View: "Granted Employees" should be a stat button with a counter
- Badges form view is broken, field label/values are not at right place

2/ ISSUES WITH CHALLENGES:
Go to menu Employees &gt; Challenges
Challenges Kanban View
- Image Avatars are too big, make it smaller.
- Challenges Form View &gt; Advanced Options : fields Report frequency, Report Template
  and Send a Copy to are ugly
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
1/ ISSUES WITH BADGES:
Go to menu Employees &gt; Badges &gt; Select any Badge from kanban View.
Click on "GRANT THIS BADGE" button.
- When you grant a badge, the description field is not at the right place.
  It should be below the employee field
- Badges Form View: "Granted Employees" should be a stat button with a counter
- Badges form view is broken, field label/values are not at right place

2/ ISSUES WITH CHALLENGES:
Go to menu Employees &gt; Challenges
Challenges Kanban View
- Image Avatars are too big, make it smaller.
- Challenges Form View &gt; Advanced Options : fields Report frequency, Report Template
  and Send a Copy to are ugly
</pre>
</div>
</content>
</entry>
<entry>
<title>[MIG] gamification: migrated sass to less.</title>
<updated>2016-03-21T13:02:10+00:00</updated>
<author>
<name>Keyur Gajjar</name>
<email>kga@odoo.com</email>
</author>
<published>2015-12-14T13:30:15+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=bea7b198621a76f3f29853fc8725e9821ff375cc'/>
<id>bea7b198621a76f3f29853fc8725e9821ff375cc</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[REM] *: remove chat menu and timeline view</title>
<updated>2015-09-01T18:57:13+00:00</updated>
<author>
<name>Aaron Bohy</name>
<email>aab@odoo.com</email>
</author>
<published>2015-08-20T13:29:54+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=a0cbf891af58f029e2c52779617ad7eeb8d26eb3'/>
<id>a0cbf891af58f029e2c52779617ad7eeb8d26eb3</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] web: create generic controller '/web/content' and '/web/image'</title>
<updated>2015-08-21T20:06:52+00:00</updated>
<author>
<name>Christophe Matthieu</name>
<email>chm@odoo.com</email>
</author>
<published>2015-08-21T07:58:13+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=6baf611df1064a3ae5f6368d3a35b3c3d7779543'/>
<id>6baf611df1064a3ae5f6368d3a35b3c3d7779543</id>
<content type='text'>
Replace deprecate controllers like /web/binary/image, /web/binary/saveas...
Use ETag for all content with 'unique' option to cache the content if the content is never changed.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Replace deprecate controllers like /web/binary/image, /web/binary/saveas...
Use ETag for all content with 'unique' option to cache the content if the content is never changed.
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] web: split model.js into model.js and data_model.js. Web js modules must call web.DataModel.</title>
<updated>2015-07-10T14:32:35+00:00</updated>
<author>
<name>Christophe Matthieu</name>
<email>chm@odoo.com</email>
</author>
<published>2015-07-08T08:29:42+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=500c33b18406c2663366ce6eefc5d8e258d6f681'/>
<id>500c33b18406c2663366ce6eefc5d8e258d6f681</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
