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.

102 lines
3.4 KiB

  1. # -*- coding: utf-8 -*-
  2. ##############################################################################
  3. #
  4. # OpenERP, Open Source Management Solution
  5. # This module copyright (C) 2012-2015 Therp BV (<http://therp.nl>).
  6. #
  7. # This program is free software: you can redistribute it and/or modify
  8. # it under the terms of the GNU Affero General Public License as
  9. # published by the Free Software Foundation, either version 3 of the
  10. # License, or (at your option) any later version.
  11. #
  12. # This program is distributed in the hope that it will be useful,
  13. # but WITHOUT ANY WARRANTY; without even the implied warranty of
  14. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  15. # GNU Affero General Public License for more details.
  16. #
  17. # You should have received a copy of the GNU Affero General Public License
  18. # along with this program. If not, see <http://www.gnu.org/licenses/>.
  19. #
  20. ##############################################################################
  21. {
  22. "name": "Support branding",
  23. "summary": "Adds your branding to an Odoo instance",
  24. "category": "Dependecy/Hidden",
  25. "version": "2.0",
  26. "license": "AGPL-3",
  27. "author": "Therp BV,Odoo Community Association (OCA)",
  28. "website": 'http://therp.nl',
  29. "description": """Support branding
  30. ================
  31. If you run an Odoo support company and you support customers without an OPW,
  32. you can brand the Odoo instance accordingly using this module. This module will
  33. add a line `Supported by $yourcompany` in the menu footer and add a button to
  34. mail exception messages to your support email address.
  35. Configuration
  36. =============
  37. This module is controlled by config parameters:
  38. support_branding.company_name
  39. Your company's name
  40. support_branding.company_url
  41. Your company's website
  42. support_branding.company_color
  43. The color to show your company's name in (CSS syntax)
  44. support_branding.support_email
  45. The (optional) mailaddress to contact for support
  46. support_branding.release
  47. The (optional) version number of your deployment
  48. You probably want to depend on this module in your customer specific module and
  49. add the following XML::
  50. <record id="support_branding.config_parameter_company_name"
  51. model="ir.config_parameter">
  52. <field name="value">Your company</field>
  53. </record>
  54. <record id="support_branding.config_parameter_company_url"
  55. model="ir.config_parameter">
  56. <field name="value">https://yourwebsite.com</field>
  57. </record>
  58. <record id="support_branding.config_parameter_company_color"
  59. model="ir.config_parameter">
  60. <field name="value">#000</field>
  61. </record>
  62. <record id="support_branding.config_parameter_support_email"
  63. model="ir.config_parameter">
  64. <field name="value">support@yourwebsite.com</field>
  65. </record>
  66. <record id="support_branding.config_parameter_support_email"
  67. model="ir.config_parameter">
  68. <field name="value">support@yourwebsite.com</field>
  69. </record>
  70. <record id="config_parameter_release" model="ir.config_parameter">
  71. <field name="value">42</field>
  72. </record>Configuration
  73. Note that the email button is only visible if you configure an email address,
  74. the default is empty!""",
  75. "depends": [
  76. 'web',
  77. ],
  78. "qweb": [
  79. 'static/src/xml/base.xml',
  80. ],
  81. "js": [
  82. 'static/src/js/support_branding.js',
  83. ],
  84. "css": [
  85. 'static/src/css/support_branding.css',
  86. ],
  87. "data": [
  88. "data/ir_config_parameter.xml",
  89. ],
  90. }