[IMP] barcodes: controller use the elaphe lib to generate barcode #529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the issue/feature this PR addresses:
There is a framework to generate barcode, useful in many cases, e.g. if I want to generate Aztec/DataMatrix/Pharmacode barcode or many other types, I have these options in the elaphe library to use. The elaphe is a python binding of Barcode Writer In Pure PostScript. This framework provides a lot of settings to customize and create a barcode, just passing this information as options in the generating method.
Current behaviour before PR:
The current barcode generating method in Odoo uses the Reportlab and if I want to generate a Data Matrix code I need to update the Reportlab library to 3.3.0 version, but if I want to change the version/format I can't because it doesn't provide these options. This is only one of much more examples that we can find.
Desired behaviour after PR is merged:
Keep the current behaviour only adding more settings and options of barcode types, initially.
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr