Skip to Content
You need to be registered to interact with the community.
All Posts People Badges
Ključne besede (View all)
odoo accounting v14 pos v15
About this forum
This question has been flagged
1 Odgovori
3059 Prikazi
Avatar
John Doe (jd)

Searching the Internet for module development documentation and tutorials yields results that can differ the 2013 OpenERP Technical Memento for OpenERP 7.

I am currently using the fleet module as main example for module development, but I wonder which would be the preferred modules as representative of the current API. They should ideally be up to date, small and simple modules. The fleet module is somewhat simple and relatively small, but comparing the OpenERP Technical Memento it does not seem to be fully up to date.

It would be uneasy developing a module relying in many OpenERP 6 / OpenERP 6.1 characteristics working in OpenERP 7 and (guess) Odoo 8 but candidatable for deprecation in upcoming Odoo 9 or Odoo 10 releases.

Avatar
Opusti
Avatar
Ben Bernard
Best Answer

Here are some few examples (module, file, model). Indeed only a few ;)

  • account, account_invoice.py, account.invoice
  • event, event.py, event.event
  • base, res_users.py, res.users (mixed api)

It's like make a POC and move on. Event new modules in 8 or 9 still use classic orm api.

-- edit --

Remove disambiguity in listing.

Avatar
Opusti
John Doe (jd)
Avtor

What do you mean by _mixed API_? Isn't _account\_invoice_ too a _mixed API_? Did you mean _eInvocing & Payments (account_voucher)_ or _eInvoicing (account)_ by stating _account\_invoice_? Thou kind answer helps me, but keep in mind the question referred to modules (openerp/apps), not models (database tables).

John Doe (jd)
Avtor

Not even sure you tell Proof of Concept or Point of Contact, but it's OK ö/

Ben Bernard

account_invoice in module account. event is a technical name module. res_users in module base. What I mean with mixed api is not fully rewritten in new api. Proof of Concept.

John Doe (jd)
Avtor

Nice, I just wasn't totally sure you were not referring to models extended by inheritance, since 'res_users' is a model so core that I guess many modules extend it. I'm used to work with the 'account_move_line model' now and is a relevant example of model inheritance: module 'account' and relationship with modules 'analytic' and 'hr_payroll_account'.

Ben Bernard

Thanks, I update my answer. What you asking, module, is too general. At first I try to be more spesific, but fail.