janneman wrote: > I still suggest to solve this issue where it is originated, thus into the > source. Do not make a workaround that doesn't solve the real problem, this > only makes a extra layer around the bug.
I couldn't agree more. The changes have to be made in the source eventually, and making them directly here makes it a lot easier to : - trace and justify the changes - double check that the term is adequate for the code - update the code documentation, help texts etc. - make the changes consistent across the whole application Of course it is a bit too technical for domain experts but they have better things to do : - write the glossary of terms - file bug reports For the glossary, IMHO it must be part of the official documentation. The first thing we could do would be to collect the existing terminology, so it can be easily reviewed by experts. Maybe we could script this out of the code... -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=45971#45971 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
