01:00 - EDI framework: manage any exchange
10:30 - Odoo and the NewRetail Revolution: Navigating the Future with SmartPOS, Kiosks, KDS and much more
Luis F MiléoDone
12:00 - Asynchronous e-commerce cart with offline mode
12:30 - When the filestore is not enough: the new OCA storage modules - Technical track
09:30 - Beyond Odoo Development Essentials
11:00 - Defining the proper reconciliation of payment providers.
11:30 - Server Management: Harnessing the Power of Remote Server Control
David Jimenez GomarizDone
11:00 - How to organize an Odoo project as a regular Python app
10:00 - How To Contribute Code to the OCA - Technical
10:30 - How to migrate an Odoo database across multiple versions (for newbies)
hugues de keyzerDone
Thomas is a software engineer and tech lead at Acsone. He spends part of his workdays staring at colorful dependency graphs and hunting for refactoring opportunities.
Odoo is well known for the modular architecture encouraged by its framework.
When it comes to organizing custom code, however, the best way to do it is not necessarily obvious to developers and several approaches are possible. Is the modular structure of the Odoo official apps a good guide? Does the structure of OCA addons apply to custom code? What are the impacts of different approaches on project maintenance and migration projects?
In this talk we will address such questions and more. We will also illustrate the use of graph analysis tools to reason about modularity in large scale projects and guide refactoring initiatives.