Friday, May 15, 2020
4 changes · master
Enhancements to existing features
The IoT Box can now recognize and support new connected devices through configurable interfaces instead of requiring direct changes to core device-detection files. This makes upgrades easier for partners and improves support for specialized devices such as barcode scanners by letting more specific drivers take priority.
Original PR description
### Support devices on new interfaces without having to modify `driver.py` Until now, to detect new types of devices on the IoT Box, we had to modify driver.py. If partners wanted to connect a new…
### Support devices on new interfaces without having to modify `driver.py` Until now, to detect new types of devices on the IoT Box, we had to modify driver.py. If partners wanted to connect a new type of device, they had to modify directly the files on the Box, meaning that after each new build they had to re-apply all their modifications. We remove the loops that detected the connected devices and replace them by `Interfaces`. All interfaces will be loaded from the connected Odoo instance with the corresponding drivers. ### Support new devices by extending existing ones Previously, we tested the `supported` methods of all drivers sequentially in alphabetical order of file names. If you wanted to extend a driver, the `supported` method of your driver could never be tested if the one of its parent was tested first. We've now added a priority order to drivers so that by default the extending driver will always be tested before the extended driver. You can still do something similar to what `is_tested_last` did by manually setting the priority of a driver to 0. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Analytic default settings are now included directly in Accounting, HR expenses, and Purchase instead of requiring separate add-on modules. This reduces setup steps after enabling analytics and makes related workflows available without extra manual installation.
Original PR description
Merge account_analytic_default into account Merge account_analytic_default_hr_expense into hr Merge account_analytic_default_purchase into purchase Prevent having to manually install default modules after activating analytics Task: 2182900
The color picker used in website and editor screens has been streamlined into a smaller, more consistent palette. Users get clearer color previews, simpler reset behavior, and more consistent interactions when editing text, backgrounds, and snippets.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The IoT Box can now detect devices through flexible interfaces loaded from Odoo, reducing the need for manual changes on each box. This makes it easier for partners to support new or customized devices and helps preserve those integrations across future updates.
Original PR description
### Support devices on new interfaces without having to modify `driver.py` Until now, to detect new types of devices on the IoT Box, we had to modify driver.py. If partners wanted to connect a new…
### Support devices on new interfaces without having to modify `driver.py` Until now, to detect new types of devices on the IoT Box, we had to modify driver.py. If partners wanted to connect a new type of device, they had to modify directly the files on the Box, meaning that after each new build they had to re-apply all their modifications. We remove the loops that detected the connected devices and replace them by `Interfaces`. All interfaces will be loaded from the connected Odoo instance with the corresponding drivers. ### Support new devices by extending existing ones Previously, we tested the `supported` methods of all drivers sequentially in alphabetical order of file names. If you wanted to extend a driver, the `supported` method of your driver could never be tested if the one of its parent was tested first. We've now added a priority order to drivers so that by default the extending driver will always be tested before the extended driver. You can still do something similar to what `is_tested_last` did by manually setting the priority of a driver to 0.