On 2015-07-22 18:04, Sergi Almacellas Abellana wrote: > El 22/07/15 a les 17:49, Cédric Krier ha escrit: > >On 2015-07-22 13:25, Sergi Almacellas Abellana wrote: > >>>El 22/07/15 a les 12:53, Cédric Krier ha escrit: > >>>> >What do you mean by it doesn't work? > >>>> >Normally, if a field is invisible on a list view, the cell will be > >>>> >empty. Do you see values instead? > >>> > >>>No I don't see values, but I thought that's because it's a function field > >>>and the result will be always None for customer invoices. > >>> > >>>So I understand it's working correctly. > >>> > >>>BTW, I want to remove the column depending on the context (or on parent > >>>field). If i understand well this is not currently possible without > >>>replacing the full view. Do you think there is room for improvement here? > >No, I don't think it is right to implement that because it is similar to > >having two views. > > For us, having two views it's harder to maintain as there are a lot of > modules that extend the invoice form and invoice_lines_tree that should be > modified in order to support the new view introduced. > > That's why we try to remove.
Plus using context is always bad so we must not at all encourage this behaviour. Also I think there is a design issue if your fields are only meaningful for one type of invoice. I mean it is not a generic modification but just a customization so there is no problem about extention because customization always comes last. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
