I agree with Pedro base_location provides the base data model to manage this problematic. The major difference is the entry point that goes from zip to city.
It is also True we can adapt the base_location to support city entry point. It is also True it will add a small layer of complexity on a simple addon. Add a city field on partner, company view Add two new on_change on the respective view Add a group management to be able to manage the views Add more complex constraint to manage data integrity. Both are small addons so making this adaptation will be in proportion quite a work. I'm in favor of convergence when possible and meaningful. In that case as there both small addons I will not be shocked to commit the new one, but I'm in favour to extend base_location as we have make the effort to merge better_zip and location. Regards Nicolas -- https://code.launchpad.net/~savoirfairelinux-openerp/partner-contact-management/city-move/+merge/196023 Your team Savoir-faire Linux' OpenERP is subscribed to branch lp:~savoirfairelinux-openerp/partner-contact-management/city-move. -- Mailing list: https://launchpad.net/~savoirfairelinux-openerp Post to : [email protected] Unsubscribe : https://launchpad.net/~savoirfairelinux-openerp More help : https://help.launchpad.net/ListHelp
