Merge lp:~sebastien.beau/openerp-product-attributes/openerp-product-attributes-product-dimension into lp:~product-core-editors/openerp-product-attributes/7.0
Status: | Rejected |
---|---|
Rejected by: | Maxime Chambreuil (http://www.savoirfairelinux.com) on 2013-12-01 |
Proposed branch: | lp:~sebastien.beau/openerp-product-attributes/openerp-product-attributes-product-dimension |
Merge into: | lp:~product-core-editors/openerp-product-attributes/7.0 |
Diff against target: |
140 lines (+120/-0) 4 files modified
product_dimension/__init__.py (+23/-0) product_dimension/__openerp__.py (+34/-0) product_dimension/product.py (+34/-0) product_dimension/product_view.xml (+29/-0) |
To merge this branch: | bzr merge lp:~sebastien.beau/openerp-product-attributes/openerp-product-attributes-product-dimension |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Maxime Chambreuil (http://www.savoirfairelinux.com) | Disapprove on 2013-07-22 | ||
Guewen Baconnier @ Camptocamp | 2013-06-24 | Needs Information on 2013-06-25 | |
Review via email:
|
Description of the change
Add a module for adding dimension field on product. Needed for e-commerce
Marc Cassuto (SFL) (mcassuto) wrote : | # |
Hi Guewen, Sébastien,
I wonder if we should not reuse existing code :
https:/
This code also deal with the volume issue...
My 2 cents,
Marc
==
Marc Cassuto, Ing. MBA Itil
SAVOIR-FAIRE LINUX
Consultant solutions ERP
T: 514-276-5468 #180
----- Original Message -----
> From: "Guewen Baconnier @ Camptocamp" <email address hidden>
> To: "Sébastien BEAU - http://
> Sent: Tuesday, June 25, 2013 2:42:47 AM
> Subject: Re: [Openerp-community] [Merge]
> lp:~sebastien.beau/openerp-product-attributes/openerp-product-attributes-product-dimension into
> lp:openerp-product-attributes
>
> Review: Needs Information
>
> Hi Sébastien,
>
> My impression is that the dimensions should be centimeters.
> At least we should have a configurable precision.
>
> I think you can remove this TODO:
>
> #TODO add a function field for volume? an onchange?
>
> If someone need a 'volume' field, he will add it, would it be an
> onchange or a function field, but I don't see any value for this
> comment.
> --
> https:/
> Your team OpenERP Community is subscribed to branch
> lp:openerp-product-attributes.
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>
> Hi Guewen, Sébastien,
>
> I wonder if we should not reuse existing code :
> https:/
> standardized-
>
> This code also deal with the volume issue...
>
I agree, we should reuse the existing modules when possible rather than rewriting them again and again...
We also have product_size already in this repository.
> We also have product_size already in this repository.
You have three model in the same module involved,
Better is to have that single feature, product demensions into a
different module,
And that you come with your module depending on this new module,
product_dimension.
Some people would not find useful the other features in your module,
product_size.
Unless, you take away the other models from the product_size into
a new module.
Regards.
Hi sorry for my late answer.
@Marc, I didn't know about this existing module http://
@Maxime regarding the product_size, I agree with Humberto I think there is too much feature inside (even if the module is small).
I think it will be better to have two separated module product_dimension (or product_size) and than product_
Maybe the best solution is to use the module product_dimensions from SFL (already translated) and refactor the module product_size on it and than rename correctly the two module (product_dimension and product_
What do you think?
+1 for product_size and derivatives. The shorter, the better.
Quentin THEURET @Amaris (qtheuret) wrote : | # |
+1 with Sébastien's comment.
> Hi sorry for my late answer.
> @Marc, I didn't know about this existing module
> http://
> standardized-
>
> @Maxime regarding the product_size, I agree with Humberto I think there is too
> much feature inside (even if the module is small).
> I think it will be better to have two separated module product_dimension (or
> product_size) and than product_
>
> Maybe the best solution is to use the module product_dimensions from SFL
> (already translated) and refactor the module product_size on it and than
> rename correctly the two module (product_dimension and product_
> or product_size and product_size_lot)
>
> What do you think?
Seems reasonable.
Can we close this MP?
debaetsr (rubendebaets) wrote : | # |
Hello!
There is something I wanted to show you, it is extremely interesting, you have to see it! Take a look here <http://
ruben
Unmerged revisions
- 207. By Sébastien BEAU - http://www.akretion.com on 2013-06-24
-
[ADD] add product_dimension module
Hi Sébastien,
My impression is that the dimensions should be centimeters.
At least we should have a configurable precision.
I think you can remove this TODO:
#TODO add a function field for volume? an onchange?
If someone need a 'volume' field, he will add it, would it be an onchange or a function field, but I don't see any value for this comment.