« back to all changes in this revision
Viewing changes to partner_firstname/i18n/de.po
- Committer: Maxime Chambreuil
- Date: 2014-03-12 22:39:51 UTC
- mfrom: (32.3.6 jne-firstname)
- Revision ID: maxime.chambreuil@savoirfairelinux.com-20140312223951-980toa7d0d2fsi78
[MRG]
For Partner:
1) Create always the SQL constraint on 'lastname'
2) Better implementation of "_write_name" allowing more intuitive update of the partner name when processing from another model (ex: res_user), i.e., try to keep the firstname if unchanged
3) When duplicating a partner, avoid to repeat the firstname in the name
4) Beautify the inner form for children contacts (placing fields as in the main form)
5) Allow edition of the field name in the inner form if child is a company
For User:
1) Reintegrate the name as "required"
2) When duplicating a user, avoid to repeat the firstname in the related partner name
For Partner:
1) Create always the SQL constraint on 'lastname'
2) Better implementation of "_write_name" allowing more intuitive update of the partner name when processing from another model (ex: res_user), i.e., try to keep the firstname if unchanged
3) When duplicating a partner, avoid to repeat the firstname in the name
4) Beautify the inner form for children contacts (placing fields as in the main form)
5) Allow edition of the field name in the inner form if child is a company
For User:
1) Reintegrate the name as "required"
2) When duplicating a user, avoid to repeat the firstname in the related partner name
- files added:
- partner_firstname/tests
- files modified:
- partner_firstname/__openerp__.py
added
removed
partner_firstname/i18n/de.po
