Odoo Experience 2017
-
New App: Online Appointments
-
Empower your App by Inheriting from 8 Mixins
Thibault Delavallee, Software Developer Team Leader - OdooDone
-
Porting Odoo To Python 3: An Overview
Olivier Dony - Software & SaaS Engineer, Security team, OdooDone
-
Accounting & Localisations: What's new in Odoo 11?
Quentin De Paoli - Odoo DeveloperDone
-
ORM Performance: Optimizations and Best Practices
Raphael Collet (rco)Done
-
Best Practices to Develop Odoo Unit Tests
Thibault François - Technical Consultant Team Leader, OdooDone
-
A Single Page App Using the Odoo JS Framework
Damien Bouvy (dbo)Done
-
The Odoo JS Framework
Gery Debongnie - Lead Developer, OdooDone
-
Ask Me Anything: Antony Lesuisse and Fabien Pinckaers
Antony Lesuisse - Chief Technical Officer, OdooDone
-
Odoo.sh: AMA
Damien Bouvy (dbo)Done
This talk is mostly for developers but all expertise levels are welcome. During this talk, you will have a short overview of :
- the way Studio works
- what kind of compromise we had to make.
Also, I think that this talk should explain that the main reason that Odoo Studio was even possible is that a large part of the Odoo interface is declarative, is stored in a database (so it is dynamic) and is extensible (via xpath). For this talk, we can give some examples of pain points (for example, monetary fields need a currency field to even work), we can give some examples of the challenges that we faced (how to build a xpath that will not break, or how to clean up the view created by studio, how to name new fields, etc ...)
We can also mention that Odoo Studio was the motivation for creating the new views: we needed a clean separation of concerns between the rendering and the rest of the views. In short, this talk is just a look behind the way Studio works.