Package: odoo10-addon-web-widget-x2many-2d-matrix
.. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html:alt: License: AGPL-3===========================2D matrix for x2many fields===========================This module allows to show an x2many field with 3-tuples($x_value, $y_value, $value) in a table========= =========== ===========\          $x_value1   $x_value2========= =========== ===========$y_value1 $value(1/1) $value(2/1)$y_value2 $value(1/2) $value(2/2)========= =========== ===========where `value(n/n)` is editable.An example use case would be: Select some projects and some employees so thata manager can easily fill in the planned_hours for one task per employee. Theresult could look like this:.. image:: /web_widget_x2many_2d_matrix/static/description/screenshot.png:alt: ScreenshotThe beauty of this is that you have an arbitrary amount of columns with thiswidget, trying to get this in standard x2many lists involves some quite uglyhacks.Usage=====Use this widget by saying::<field name="my_field" widget="x2many_2d_matrix" />This assumes that my_field refers to a model with the fields `x`, `y` and`value`. If your fields are named differently, pass the correct names asattributes::<field name="my_field" widget="x2many_2d_matrix" field_x_axis="my_field1" field_y_axis="my_field2" field_value="my_field3"><tree><field name="my_field"/><field name="my_field1"/><field name="my_field2"/><field name="my_field3"/></tree></field>You can pass the following parameters:field_x_axisThe field that indicates the x value of a pointfield_y_axisThe field that indicates the y value of a pointfield_label_x_axisUse another field to display in the table headerfield_label_y_axisUse another field to display in the table headerx_axis_clickableIt indicates if the X axis allows to be clicked for navigating to the field(if it's a many2one field). True by defaulty_axis_clickableIt indicates if the Y axis allows to be clicked for navigating to the field(if it's a many2one field). True by defaultfield_valueShow this field as valueshow_row_totalsIf field_value is a numeric field, it indicates if you want to calculaterow totals. True by defaultshow_column_totalsIf field_value is a numeric field, it indicates if you want to calculatecolumn totals. True by defaultfield_att_<name>Declare as many options prefixed with this string as you need for bindinga field value with an HTML node attribute (disabled, class, style...)called as the `<name>` passed in the option... image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas:alt: Try me on Runbot:target: https://runbot.odoo-community.org/runbot/162/8.0Example=======You need a data structure already filled with values. Let's assume we want touse this widget in a wizard that lets the user fill in planned hours for onetask per project per user. In this case, we can use ``project.task`` as ourdata model and point to it from our wizard. The crucial part is that we fillthe field in the default function::from odoo import fields, modelsclass MyWizard(models.TransientModel):_name = 'my.wizard'def _default_task_ids(self):# your list of project should come from the context, some selection# in a previous wizard or wherever elseprojects = self.env['project.project'].browse([1, 2, 3])# same with usersusers = self.env['res.users'].browse([1, 2, 3])return [(0, 0, {'project_id': p.id,'user_id': u.id,'planned_hours': 0,'message_needaction': False,'date_deadline': fields.Date.today(),})# if the project doesn't have a task for the user, create a new oneif not p.task_ids.filtered(lambda x: x.user_id == u) else# otherwise, return the task(4, p.task_ids.filtered(lambda x: x.user_id == u)[0].id)for p in projectsfor u in users]task_ids = fields.Many2many('project.task', default=_default_task_ids)Now in our wizard, we can use::<field name="task_ids" widget="x2many_2d_matrix" field_x_axis="project_id" field_y_axis="user_id" field_value="planned_hours"><tree><field name="task_ids"/><field name="project_id"/><field name="user_id"/><field name="planned_hours"/></tree></field>Note that all values in the matrix must exist, so you need to create thempreviously if not present, but you can control visually the editability ofthe fields in the matrix through `field_att_disabled` option with a controlfield.Known issues / Roadmap======================* It would be worth trying to instantiate the proper field widget and let it render the input* Let the widget deal with the missing values of the full Cartesian product,instead of being forced to pre-fill all the possible values.* If you pass values with an onchange, you need to overwrite the model's method`onchange` for making the widget work::@api.multidef onchange(self, values, field_name, field_onchange):if "one2many_field" in field_onchange:for sub in [<field_list>]:field_onchange.setdefault("one2many_field." + sub, u"")return super(model, self).onchange(values, field_name, field_onchange)Bug Tracker===========Bugs are tracked on `GitHub Issues<https://github.com/OCA/web/issues>`_. In case of trouble, pleasecheck there if your issue has already been reported. If you spotted it first,help us smashing it by providing a detailed and welcomed feedback.Credits=======Contributors------------* Holger Brunn <hbrunn@therp.nl>* Pedro M. Baeza <pedro.baeza@tecnativa.com>Maintainer----------.. image:: https://odoo-community.org/logo.png:alt: Odoo Community Association:target: https://odoo-community.orgThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whosemission is to support the collaborative development of Odoo features andpromote its widespread use.To contribute to this module, please visit https://odoo-community.org.