-
Notifications
You must be signed in to change notification settings - Fork 0
/
__openerp__.py
executable file
·77 lines (76 loc) · 3.2 KB
/
__openerp__.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
# -*- encoding: utf-8 -*-
##############################################################################
#
# OpenERP, Open Source Management Solution
# Copyright (C) 2004-2008 Tiny SPRL (<http://tiny.be>). All Rights Reserved
# $Id$
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
##############################################################################
{
"name" : "Products with multi-level variants",
"version" : "1.0",
"author" : "Tiny",
"category" : "Generic Modules/Inventory Control",
"description":"""OpenERP is already supporting a product variants at the core level. But
without this module, variants are only mono-axial. OpenERP indeed uses the product.tempate
as the model object and the product.variant as the instance variant.
Using this module, you can now easily deal with multi-axial variants.
A product.template, now has a set of dimensions (like Color, Size, anything you want).
For each dimension, a product.template has a set of dimension values (like Red, Green
for the Color dimension). For each dimension, you can accept or not custom dimension
values. The sale interface product configurator will take it into account.
Once the product.template is set up, you can use a 'generator' button that will populate
the space of the variants. You could also choose to populate only some combinations
by hand instead.
Each variant can have an extra price that will be taken into account when computing
the base listed price. Yet to be implemented: a price extra per variant dimension value.
Finally, this module is better used along with the product_variant_configurator which
will help the salesman selecting the appropriate variant in the sale order line
using dimension criteria instead of having to crawl the full space of variants.
""",
"depends" : [
"base",
"product",
"stock",
"sale",
"purchase",
"mrp",
"procurement",
],
"init_xml" : [],
"demo_xml" : ["demo_data.xml"],
"update_xml" : [
"security/ir.model.access.csv",
"product_view.xml",
"orders_view.xml",
"wizard/create_product_view.xml",
"wizard/detail_product_production.xml",
"mrp_view.xml",
"stock_view.xml",
"procurement_view.xml",
],
"active": False,
"installable": True,
"js": ['static/src/js/loader.js',
'static/src/js/multi.js',
'static/src/js/multi_template_widget.js',
],
"css": ['static/src/css/multi.css'],
'qweb' : [
"static/src/xml/*.xml",
],
}
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4: