[ADD] field_utils to web_timeline

[UPD] Version number

[UPD] README

web_timeline/README.rst

@@ -40,6 +40,13 @@ the possible attributes for the tag:
 * colors (optional): it allows to set certain specific colors if the expressed
   condition (JS syntax) is met.
   
+Optionally you can declare a custom template, which will be used to render the 
+timeline items. You have to name the template 'timeline-item'. 
+These are the variables available in template rendering:
+
+* ``record``: to access the fields values selected in the timeline definition.
+* ``field_utils``: used to format and parse values (see available functions in ``web.field_utils``).
+
 You also need to declare the view in an action window of the involved model.
 
 Example:

web_timeline/__manifest__.py

@@ -4,7 +4,7 @@
 {
     'name': "Web timeline",
     'summary': "Interactive visualization chart to show events in time",
-    "version": "11.0.1.1.1",
+    "version": "11.0.1.2.1",
     'author': 'ACSONE SA/NV, '
               'Tecnativa, '
               'Monk Software, '

web_timeline/static/src/js/timeline_renderer.js

@@ -7,6 +7,8 @@ var time = require('web.time');
 var utils = require('web.utils');
 var session = require('web.session');
 var QWeb = require('web.QWeb');
+var field_utils = require('web.field_utils');
+
 
 var _t = core._t;
 
@@ -282,7 +284,8 @@ var CalendarRenderer = AbstractRenderer.extend({
         if (this.arch.children.length) {
             if(this.qweb.has_template('timeline-item')) {
                 content = this.qweb.render('timeline-item', {
-                    'record': evt
+                    'record': evt,
+                    'field_utils': field_utils
                 });
             } else {
                 console.error(_t('Template "timeline-item" not present in timeline view definition.'));