| chat.freenode.net #tryton log beginning Mon May 15 00:00:01 CEST 2017 | ||
| 2017-05-15 02:28 -!- kobain(~kobain@unaffiliated/kobain) has joined #tryton | ||
| 2017-05-15 03:32 -!- thaneor(~ldlc6@r179-25-160-227.dialup.adsl.anteldata.net.uy) has joined #tryton | ||
| 2017-05-15 03:50 -!- apostatize(~visavis@gateway/vpn/privateinternetaccess/apostatize) has joined #tryton | ||
| 2017-05-15 05:13 -!- smarro(~sebastian@181.16.7.104) has joined #tryton | ||
| 2017-05-15 06:18 -!- thaneor(~ldlc6@r179-25-180-102.dialup.adsl.anteldata.net.uy) has joined #tryton | ||
| 2017-05-15 07:28 -!- dj_xatra(~dj_xatra@217.166.83.130) has joined #tryton | ||
| 2017-05-15 08:17 -!- rpit(~rpit@2a02:908:e672:7480:56ee:75ff:fe0d:d3c7) has joined #tryton | ||
| 2017-05-15 08:26 -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | ||
| 2017-05-15 09:03 -!- Timitos(~kpreisler@host-88-217-184-172.customer.m-online.net) has joined #tryton | ||
| 2017-05-15 09:12 -!- mrichez(~smuxi@mail.saluc.com) has joined #tryton | ||
| 2017-05-15 09:18 -!- nicoe(~nicoe@2a02:a03f:30b2:3c00:ee55:f9ff:fe7b:f7ac) has joined #tryton | ||
| 2017-05-15 09:22 -!- JanGB(~jan@ip92343817.dynamic.kabel-deutschland.de) has joined #tryton | ||
| 2017-05-15 09:43 -!- rpit(~rpit@2a02:908:e672:7480:7e7a:91ff:fec8:6289) has joined #tryton | ||
| 2017-05-15 10:24 -!- mrichez(~smuxi@mail.saluc.com) has joined #tryton | ||
| 2017-05-15 11:34 -!- rpit(~rpit@2a02:908:e672:7480:56ee:75ff:fe0d:d3c7) has joined #tryton | ||
| 2017-05-15 11:43 <sisalp> hello, I'd like to add the product variant description on the sale order line. Is there a ready to use solution for this ? | ||
| 2017-05-15 11:54 <pokoli> sisalp: not as a module, but it's not complex to code it :) | ||
| 2017-05-15 11:57 <sisalp> pokoli: do you know why it is not per default ? What is the purpose of product description if it is never used ? | ||
| 2017-05-15 12:02 <pokoli> sisalp: not sure, but description is required on sale lines but no description is required on product | ||
| 2017-05-15 12:02 <pokoli> sisalp: so we use rec_name that is always defined | ||
| 2017-05-15 12:12 <cedk> sisalp: the purpose is to describe the product… And there is no point to describe the product on a sale | ||
| 2017-05-15 12:28 <sisalp> cedk: In fact I need a multiline product specification on the proposal, order and invoice. With the description field, I perfectly manage the way it is presented and translated. | ||
| 2017-05-15 12:30 <sisalp> cedk : the product internal code and the name of the product model are not useful in my case. | ||
| 2017-05-15 12:32 <cedk> sisalp: in your case… | ||
| 2017-05-15 12:32 <sisalp> Is there any risk of a side effect on other modules if I modify the line description of orders and invoices ? | ||
| 2017-05-15 12:33 <sisalp> cedk: I imagine the generic solution would be to use description as first intention, and default it to rec_name in case there is no description. | ||
| 2017-05-15 12:37 <cedk> sisalp: for me, it is not a generic solution | ||
| 2017-05-15 12:38 <cedk> sisalp: most of the use case does not want to show a description on sale | ||
| 2017-05-15 12:38 <cedk> sisalp: also it was never defined that product description is intended to be display to customer | ||
| 2017-05-15 12:38 <cedk> it may include sensitive data | ||
| 2017-05-15 12:39 <sisalp> cedk: what is the aim of product description ? | ||
| 2017-05-15 12:41 <sisalp> for internal info, I started using Notes. | ||
| 2017-05-15 12:43 <cedk> sisalp: describe the product | ||
| 2017-05-15 12:47 <cedk> sisalp: it is the usage that defines it | ||
| 2017-05-15 12:48 <cedk> sisalp: but we can not make general change based on some usages | ||
| 2017-05-15 12:50 <sisalp> cedk: I expected that the Description column on a sale order and an invoice is also a description of what is sold. Indeed, we then may have different descriptions for sales, purchase, production, so we can live with Code/name as a generic solution. | ||
| 2017-05-15 12:52 <cedk> sisalp: it is the description of what is sold | ||
| 2017-05-15 12:56 <cedk> sisalp: but the default description is the rec_name of the product | ||
| 2017-05-15 12:56 <cedk> sisalp: there is an issue to get the supplier name for purchase | ||
| 2017-05-15 12:57 <cedk> a generic solution would be to have a module that allow to customize the description using a small template syntax | ||
| 2017-05-15 12:57 <JanGB> cedk, sisalp: we should have a module i.e. product_sale_description for that - I always put this in my installs, because most customer want to show a description on sales. In many cases sales must be more verbose to show a client what he will get if it is his first buy | ||
| 2017-05-15 12:57 <cedk> based on the product object | ||
| 2017-05-15 13:05 <JanGB> cedk, sisalp: for the internal informations we have a very complex module product_specification. Specification for internal use with technical infos - description as the 'narrative' exposed to clients | ||
| 2017-05-15 13:08 <sisalp> JanGB: before adding "sub-generic" we should be sure the generic implements the most expected function. | ||
| 2017-05-15 13:09 <JanGB> sisalp: yes - a setting 'Show description on sales' with a boolean | ||
| 2017-05-15 13:09 <JanGB> sisalp: the specification is for our very special needs - no chance to make it generic :) | ||
| 2017-05-15 13:12 <sisalp> JanGB: yes, provided we consider that my case is not so specific. For my case, I think I'll use description as the default, and rec_name if description is empty. | ||
| 2017-05-15 13:13 <JanGB> sisalp: Wait - I will publish ours. | ||
| 2017-05-15 13:23 <sisalp> JanGB: I just implemented and feel comfortable with it. In particular if description translation is left empty for a language, the rec_name is used instead. | ||
| 2017-05-15 13:23 <JanGB> sisalp: ok | ||
| 2017-05-15 13:31 -!- mariomop(~quassel@host130.181-10-41.telecom.net.ar) has joined #tryton | ||
| 2017-05-15 13:54 -!- smarro(~sebastian@181.16.7.104) has joined #tryton | ||
| 2017-05-15 15:36 -!- kstenger(~karla@r190-134-48-94.dialup.adsl.anteldata.net.uy) has joined #tryton | ||
| 2017-05-15 16:56 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 17:49 -!- andrespoliti(~andrespol@250-183-89-200.fibertel.com.ar) has joined #tryton | ||
| 2017-05-15 18:20 -!- thaneor1(~ldlc6@179.26.132.253) has joined #tryton | ||
| 2017-05-15 18:51 -!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton | ||
| 2017-05-15 19:55 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 20:07 -!- lukio(~lukio@iplan.gcoop.com.ar) has joined #tryton | ||
| 2017-05-15 20:14 <lukio> hi everybody, I want to set invisible a tag field when the state of an invoice is 'in'. I found a thread that says that the tag can't be override by view_attributes. Is there any other way to set a tag field as invisible? | ||
| 2017-05-15 20:16 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 20:26 <lukio> sorry, this is the thread that I talk about: https://groups.google.com/forum/#!topic/tryton/CRu4n-HKFa0 | ||
| 2017-05-15 20:44 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 21:01 <cedk> lukio: no, view_attributes is the only way | ||
| 2017-05-15 21:01 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 21:50 -!- JanGB(~jan@ip92343817.dynamic.kabel-deutschland.de) has joined #tryton | ||
| 2017-05-15 22:01 -!- semarie(~semarie@unaffiliated/semarie) has joined #tryton | ||
| 2017-05-15 22:41 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 23:07 -!- lukio(~lukio@iplan.gcoop.com.ar) has left #tryton | ||
| 2017-05-15 23:41 -!- smarro(~sebastian@181.16.7.104) has joined #tryton | ||
| 2017-05-15 23:48 -!- JosDzG(~Thunderbi@189.250.43.248) has joined #tryton | ||
| 2017-05-15 23:53 -!- inthend(~giita@41.250.57.149) has joined #tryton |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!