From 47a3592417bbb3d5abd784ee8ba7d9d1e2644479 Mon Sep 17 00:00:00 2001 From: Sylvain LE GAL Date: Mon, 10 Oct 2016 11:59:22 +0200 Subject: [PATCH] [WIP] --- .travis.yml | 2 +- barcodes_generate/__openerp__.py | 21 +++++++++------------ 2 files changed, 10 insertions(+), 13 deletions(-) diff --git a/.travis.yml b/.travis.yml index bc7ac93b..6db3363f 100644 --- a/.travis.yml +++ b/.travis.yml @@ -33,7 +33,7 @@ install: - export PATH=${HOME}/maintainer-quality-tools/travis:${PATH} - travis_install_nightly - printf '[options]\n\nrunning_env = dev' > ${HOME}/.openerp_serverrc - - pip install unidecode pyserial pycountry + - pip install unidecode pyserial pycountry pyBarcode script: - travis_run_tests diff --git a/barcodes_generate/__openerp__.py b/barcodes_generate/__openerp__.py index f91c0d73..cd84ded4 100644 --- a/barcodes_generate/__openerp__.py +++ b/barcodes_generate/__openerp__.py @@ -13,31 +13,28 @@ Generate Barcodes for Products and Customers ============================================ -This module depends on a backport of the V9 modules of Odoo 'barcodes'. - -It expends Odoo functionnality, to allow user to generate barcode depending -on a given barcode rule. +This module expends Odoo functionnality, allowing user to generate barcode +depending on a given barcode rule. For exemple, a typical pattern for products is "23.....{NNNDD}" that means that the EAN13 code will begin by '23', followed by 5 digits and after 5 others digits to define the variable price. (EAN13 has a third char for control). With this module, it is possible to: -- Affect a pattern (barcode.rule) to a product.product or a res.partner -- To generate an EAN13 depending on the defined pattern and a custom ID + +* Affect a pattern (barcode.rule) to a product.product or a res.partner +* To generate an EAN13 depending on the defined pattern and a custom ID Note ---- -Dependency to point_of_sale is required because ean13 field, defined in 'base' -module (in the res.partner model), is defined in a point_of_sale view. - -The same design error is present in odoo 9.0 with the renamed 'barcode' field. +Dependency to point_of_sale is required because barcode field, defined in 'base' +module (in the res.partner model), is defined in a 'point_of_sale' view. It's a relative problem, because product barcodes generation will occures mostly in a Point of Sale context. -You could comment 'point_of_sale' dependency if you use this module without -point of sale. +You could comment 'point_of_sale' dependency if you want to use this module +without point of sale. Copyright Note --------------