From 49f7a9f657b011080666475f836982665615dc7c Mon Sep 17 00:00:00 2001 From: qsm-odoo Date: Thu, 9 Mar 2017 15:12:58 +0100 Subject: [REF] web, mail: use field registry in views, not renderers Before this commit, the AbstractField specialization to use to instantiate a field was determined in the renderers. Now this is regrouped in BasicView. Note: renderers are still left free to not use the determined Class (like Kanban and not editable List which instantiate widgets only if the "widget" attribute is present). --- addons/web/static/src/js/views/basic/basic_renderer.js | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'addons/web/static/src/js/views/basic/basic_renderer.js') diff --git a/addons/web/static/src/js/views/basic/basic_renderer.js b/addons/web/static/src/js/views/basic/basic_renderer.js index 7b57f16dd84..d8ddf02d169 100644 --- a/addons/web/static/src/js/views/basic/basic_renderer.js +++ b/addons/web/static/src/js/views/basic/basic_renderer.js @@ -104,8 +104,7 @@ return AbstractRenderer.extend({ * Actual rendering. Supposed to be overridden by concrete renderers. * The basic responsabilities of _renderView are: * - use the xml arch of the view to render a jQuery representation - * - instantiate a widget from the widgets_registry for each field in the - * arch + * - instantiate a widget from the registry for each field in the arch * * Note that the 'state' field should contains all necessary information * for the rendering. The field widgets should be as synchronous as -- cgit v1.2.3