El 30/12/14 a les 14:39, Cédric Krier ha escrit:
On 30 Dec 13:58, Jean C wrote:
>2014-12-30 13:00 GMT+01:00 Vincent Bastos<[email protected]>:
>
> >I am not saying that they are correct, but I curious to hear people's
> >thoughts around this topic.
>
>
>Names are tough :
>http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
I even think we should remove the required on the name of Party.
We have code for this case.
Sounds good to me.
>That said, we had the same requirements from our (french speaking) clients.
>We dealt with it by adding a first_name field, using the name field for the
>last name, and overriding get_rec_name to display both if needed.
The best solution is to convince your customer that their requirements
are wrong.
A possible generic solution will be to use a list of type of name (maybe
a Dict field) that could be used to autofill the real name with maybe
some sort of formatting depending on some context like the language, the
primary country etc.
For me it's better to create specific fields on custom module (and
override rec_name and full name if needed). For example:
https://bitbucket.org/zikzakmedia/trytond-party_type/src/28d0479d00511c05ffa00171e91785ad23a8da19/party.py?at=default
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
