Hi all !
I was just wondering why Dolibarr offers to save product length, area (is
that the right word ? not surface ?) and volume and not length, width and
height, and have area and volume automatically calculated ?
I'm with a customer who want's to have his products dimensions but don't
want su
Hi,
this would just work for cubic products. We sell round glasses and
bottles. :)
Am 05.12.13 15:03, schrieb Maxime Kohlhaas:
Hi all !
I was just wondering why Dolibarr offers to save product length, area
(is that the right word ? not surface ?) and volume and not length,
width and height
To knwo the volume you need "depth" also
widht*height*depth (fr:depth n'est peux être la bonne traduction
hauteur*longeur*largeur)
To me it seems to be a good idea.
Florian HENRY
florian.he...@open-concept.pro
+33 6 03 76 48 07
http://www.open-concept.pro
Twitter : @_Open_Concept_
Secretaire d
Hi !
Thanks for the answer. Of course these 2 new fields I propose won't be
mandatory, so they won't bother you much.
Today the volume information is used in shipments, and I assume that even
if you are selling bottles, they have a length, width and height, which are
defined by the box or packing
On Thu, Dec 5, 2013 at 3:03 PM, Maxime Kohlhaas wrote:
> Hi all !
>
> I was just wondering why Dolibarr offers to save product length, area (is
> that the right word ? not surface ?) and volume and not length, width and
> height, and have area and volume automatically calculated ?
>
>
Hi, I was al
On Thu, Dec 5, 2013 at 3:08 PM, Philip Lehmann-Böhm wrote:
> Hi,
>
> this would just work for cubic products. We sell round glasses and
> bottles. :)
>
> But I think your round glasses are sold in a square box aren't they ? Also
its easy to implement a possibility to calculate a volume
of round
There are no boxes, we are selling them directly on a market. :)
Am 05.12.13 15:12, schrieb Maxime Kohlhaas:
Hi !
Thanks for the answer. Of course these 2 new fields I propose won't be
mandatory, so they won't bother you much.
Today the volume information is used in shipments, and I assume t
Then you'd have to have an UI element for the shape. And they are no
perfect cylinders.
We use the volume for the amount of content in the bottles/glasses.
Am 05.12.13 15:19, schrieb Sasa Ostrouska:
On Thu, Dec 5, 2013 at 3:08 PM, Philip Lehmann-Böhm
mailto:phi...@philiplb.de>> wrote:
On Thu, Dec 5, 2013 at 3:23 PM, Philip Lehmann-Böhm wrote:
> Then you'd have to have an UI element for the shape. And they are no
> perfect cylinders.
> We use the volume for the amount of content in the bottles/glasses.
>
> Thats why I telling it should not make you much difference between selli
In current version all dimensions can be used or not
People who want to enter length+width+heigth, yuo can do so. In such cases,
volume is autocalulcated.
People who don't want to enter immediatly a volume, and don't want to have
volume calculated, can also do this. All user have to do is to enter
This sounds good. People wanting some auto-volume-calculation are happy
and we are happy, too, then. :)
Am 05.12.13 16:38, schrieb Destailleur Laurent:
In current version all dimensions can be used or not
People who want to enter length+width+heigth, yuo can do so. In such
cases, volume is aut
We are using only either the volume or the weight, nothing else. For us,
the use case is to give some information about the content, not the
box/glass/bottle.
When we enter only the weight or volume, nothing goes wrong currently. :)
And as Destailleur posted, it's totally fine like this:
If you
I also find this rule ok, if need to calculate then input single
dimensions, otherwise just input the result. No one of this fields should
be mandatory IMHO.
Rgds
Saxa
On Thu, Dec 5, 2013 at 4:53 PM, Philip Lehmann-Böhm wrote:
> We are using only either the volume or the weight, nothing else.
13 matches
Mail list logo
