website.snippet: The methods described in javascript will be called automatically from the data-method_name = value on li snippets options. The methods are called in the order relative to children of xml (eg: <li data-method1=value1> ... <li data-method2=value2> ... </ li>, the method1 is then called method2). Methods receive two arguments: type (over, click, reset) and value. data-snippet-id-option becomes data-snippet-id. Several xml options can use the same data-snippet-id.
add a new gallery snippet
convert website_sale to the new option system
- Do not include css in less source because malformed css will break
less compilation
- Always recompose compiled css, even if not in debug mode
- Less and sass compilers mode @at-rules on top in order to comply
to css 2.1, those @at-rules where left-over during the recompostion
because they lost their marker. Those are now handled as virtual
inline stylesheets.
[FIX] Asset bundles compilation bug + support for mixed preprocessing languages
- moving imports to the top of the source to compile breaks the assets recomposition trough markers
- improved performance by avoiding useless assets fragments recomposition
- added support for mixed preprocessing languages in the same bundle
- RFQ wording imp
- products tree view in purchase form view: set account_analytic_id
for group_analytic_accounting only + add a context for the partner
- purchase: res_config: wording imp + config view imp
[IMP] Make autoreload work in --dev mode
- Replaced `pyinotify` by conditionally imported `watchdog`
- On code reload, restart process without losing --database argument (was crasing `odoo start` command)
- Removed `--auto-reload` in favor of `--dev`
[MERGE] Read ir.ui.view's arch from disk in development mode
A new switch named `--dev` has been added to the openerp.cli's arguments.
This development mode's purpose is to activate some specific behaviours in order to ease development.
For the moment, the only effect of `--dev` is to make the ir.ui.view's arch function field read the data from the original xml file (if any), allowing the developer to change a view and check the effect without having to update it's database.
This feature will currently work only with existing views. If you add a view you still have to update your database.