-
10:00 - 10:45 - Making Odoo fast, analyzing Odoo's speed
Alexandre FayolleDone
-
12:10 - 12:40 - Queue job: concepts and best practices
Quentin Groulard and Zina RasoamananaDone
-
10:50 - 11:20 - Multitenancy in Odoo: one instance to rule them all.
Alexandre NuttinckDone
-
10:00 - 10:30 - Where to start to contribute to OCA
Julie LeBrun (OCA)Done
-
10:45 - 11:15 - How to install the Shopinvader eCommerce stack with a Docker image
Sébastien BeauDone
-
10:45 - 11:15 - How to Contribute - Technical
Daniel ReisDone
-
12:20 - 12:50 - Seamlessly Linking External Folders to Odoo Records with fsspec: A Generic, Extensible Approach
Laurent MignonDone
-
14:00 - 14:30 - Bulletin Board. A map based App with OWL
Nikolaus Weingartmair.Done
-
11:30 - 12:00 - EDI Framework, managing data exchanges in a single place
Héctor Villarreal OrtegaDone
-
09:30 - 10:00 - From the Product Form Jungle to a Guided Walk
Pierre VerkestDone
Lead Developer at Foodles, responsible for developing and maintaining custom Odoo modules related to stocks and logistics with occasional contributions to the OCA. Previous experience includes SaaS development in the healthcare and AI music industries, as well as R&D in social robotics.
The way inheritance works in Odoo is very powerful but messes up with the IDE's ability to statically analyze which fields and functions are available to a given record in a given module. To improve the developer experience, I have developed a script that automatically generates all the typing classes for all Odoo models based on the module's dependency tree. These can then be used as type hints to help the IDE suggest which fields and functions are available for the specific record in this specific module.
I will present how this script works, its pros, its limitations, and future plans.
