Community mailing list archives
Re: Usability/design in relation to res.partnerby
Nhomar,You forgot the most important one, web_m2x_option to stop all those creations.
On Tue, Aug 18, 2015 at 3:23 PM, Nhomar Hernández <email@example.com> wrote:
2015-08-17 20:06 GMT-05:00 Graeme Gellatly <firstname.lastname@example.org>:But anyway, those methods haven't changed a great deal in the last 5 years, despite the model change, and they are pretty easily accessible and extensively customised. I've never known two people in the same organisation to want the same partner view, let alone two organisations. Better to be easily extensible than rigid with a model that doesn't fit a lot of people. When they released the model I must admit I wasn't happy, so I got out Martin Fowler's book from the library to see how to do it better. For the most part I couldn't, though that's not to say the views and methods couldn't be improved.Absolutly agreed! with this point.BTW. We can talk A LOT about variants to manage the same model in differents ways, one time you understand that it is an almos mandatory customization if you do not understand how it works your live become easiest.IOH, I do not say it is perfect at all, a lot of thing can be better thought, for example create mistaken partners is so easy, then manage huge amounts of contacts with persons which love the order is difficult, but at the end 2 or 3 comunaty tools will help you a lot, partner_do_merge is one, and partner-contact repository has some useful modules.Regards.