On 05/03/2010 09:14 PM, P. Christeas wrote:
On Monday 03 May 2010, Davide Corio wrote:
is there a reason why __terp__ is now replaced with __openerp__ and not
__openobject__ ?
Yec, a certain one:
since the community days, we have decided to drop the term "openobject" and
only use the "openerp". This is done so that there is only one word, less
confusion.
I think this is wrong and that it must be __openobject__.py since the
framework *is* openobject and every single module is an openobject's
module, not an openerp's module. "openerp" is suite of them.
The reason there's confusion is because people don't know almost nothing
about openobj even if they are using it. I think we as developers must
publicize it more and more.
IMHO, calling the main file of a module "__openobject__.py" is the first
step to do in this direction, as well as renaming any root element of
XMLs as "<openobject />".
My 2cents :)
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
