Hello, about "Beligian" English in source code itself: https://bugs.launchpad.net/openobject-addons/+bug/326160https://bugs.launchpad.net/openobject-addons/+bug/327259
when the data structure itself has issues, it's complex to make it evolve and will need a good planning and communication from Tiny (like associating small migration scripts to bzr revisions in those cases). The issue is similar with database tables and foreign keys not respecting a consistent naming convention (now a bit better, but old code is a pity, like order.line for order.order_line_ids...). Still, I can testimony that it's often worst in other places, anyone already looked at Openbravo full Spanish javascript code? So let's admit there is no perfection but improve in this, especially the end user terminology as it is the most apparent thing. But bad code names frightens power developers just the same way. Only those taking a step back and knowing how bad this is in say standard legacy ERP code will admit it's not too bad in OpenERP actually. Regards, ------------------------ Raphaël Valyi CEO and OpenERP consultant at http://www.akretion.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=45985#45985 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
