You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

144 lines
4.8 KiB

10 years ago
10 years ago
  1. .. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
  2. :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
  3. :alt: License: AGPL-3
  4. ===========================
  5. 2D matrix for x2many fields
  6. ===========================
  7. This module allows to show an x2many field with 3-tuples
  8. ($x_value, $y_value, $value) in a table
  9. ========= =========== ===========
  10. \ $x_value1 $x_value2
  11. ========= =========== ===========
  12. $y_value1 $value(1/1) $value(2/1)
  13. $y_value2 $value(1/2) $value(2/2)
  14. ========= =========== ===========
  15. where `value(n/n)` is editable.
  16. An example use case would be: Select some projects and some employees so that
  17. a manager can easily fill in the planned_hours for one task per employee. The
  18. result could look like this:
  19. .. image:: /web_widget_x2many_2d_matrix/static/description/screenshot.png
  20. :alt: Screenshot
  21. The beauty of this is that you have an arbitrary amount of columns with this
  22. widget, trying to get this in standard x2many lists involves some quite ugly
  23. hacks.
  24. Usage
  25. =====
  26. Use this widget by saying::
  27. <field name="my_field" widget="x2many_2d_matrix" />
  28. This assumes that my_field refers to a model with the fields `x`, `y` and
  29. `value`. If your fields are named differently, pass the correct names as
  30. attributes::
  31. <field name="my_field" widget="x2many_2d_matrix" field_x_axis="my_field1" field_y_axis="my_field2" field_value="my_field3" />
  32. You can pass the following parameters:
  33. field_x_axis
  34. The field that indicates the x value of a point
  35. field_y_axis
  36. The field that indicates the y value of a point
  37. field_label_x_axis
  38. Use another field to display in the table header
  39. field_label_y_axis
  40. Use another field to display in the table header
  41. field_value
  42. Show this field as value
  43. show_row_totals
  44. If field_value is a numeric field, calculate row totals
  45. show_column_totals
  46. If field_value is a numeric field, calculate column totals
  47. field_att_<name>
  48. Declare as many options prefixed with this string as you need for binding
  49. a field value with an HTML node attribute (disabled, class, style...)
  50. called as the `<name>` passed in the option.
  51. .. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas
  52. :alt: Try me on Runbot
  53. :target: https://runbot.odoo-community.org/runbot/162/8.0
  54. Example
  55. =======
  56. You need a data structure already filled with values. Let's assume we want to
  57. use this widget in a wizard that lets the user fill in planned hours for one
  58. task per project per user. In this case, we can use ``project.task`` as our
  59. data model and point to it from our wizard. The crucial part is that we fill
  60. the field in the default function::
  61. class MyWizard(models.TransientModel):
  62. _name = 'my.wizard'
  63. def _default_task_ids(self):
  64. # your list of project should come from the context, some selection
  65. # in a previous wizard or wherever else
  66. projects = self.env['project.project'].browse([1, 2, 3])
  67. # same with users
  68. users = self.env['res.users'].browse([1, 2, 3])
  69. return [
  70. (0, 0, {'project_id': p.id, 'user_id': u.id, 'planned_hours': 0})
  71. # if the project doesn't have a task for the user, create a new one
  72. if not p.task_ids.filtered(lambda x: x.user_id == u) else
  73. # otherwise, return the task
  74. (4, p.task_ids.filtered(lambda x: x.user_id == u)[0].id)
  75. for p in projects
  76. for u in users
  77. ]
  78. task_ids = fields.Many2many('project.task', default=_default_task_ids)
  79. Now in our wizard, we can use::
  80. <field name="task_ids" widget="x2many_2d_matrix" field_x_axis="project_id" field_y_axis="user_id" field_value="planned_hours" />
  81. Note that all values in the matrix must exist, so you need to create them
  82. previously if not present, but you can control visually the editability of
  83. the fields in the matrix through `field_att_disabled` option with a control
  84. field.
  85. Known issues / Roadmap
  86. ======================
  87. * it would be worth trying to instantiate the proper field widget and let it render the input
  88. Bug Tracker
  89. ===========
  90. Bugs are tracked on `GitHub Issues
  91. <https://github.com/OCA/web/issues>`_. In case of trouble, please
  92. check there if your issue has already been reported. If you spotted it first,
  93. help us smashing it by providing a detailed and welcomed feedback.
  94. Credits
  95. =======
  96. Contributors
  97. ------------
  98. * Holger Brunn <hbrunn@therp.nl>
  99. * Pedro M. Baeza <pedro.baeza@tecnativa.com>
  100. Maintainer
  101. ----------
  102. .. image:: https://odoo-community.org/logo.png
  103. :alt: Odoo Community Association
  104. :target: https://odoo-community.org
  105. This module is maintained by the OCA.
  106. OCA, or the Odoo Community Association, is a nonprofit organization whose
  107. mission is to support the collaborative development of Odoo features and
  108. promote its widespread use.
  109. To contribute to this module, please visit https://odoo-community.org.