- max_value: maximum value of the gauge [default: 100]
- max_field: get the max_value from the field that must be present in the view; takes over max_value
- gauge_value_field: if set, the value displayed below the gauge is taken from this field instead of the base field used for the gauge. This allows to display a number different from the gauge.
- force_set: is value is 0, display a text 'Click to set' [default: True]
- label: lable of the gauge, displayed below the gauge value
- title: title of the gauge, displayed on top of the gauge
- on_change: action to call when cliking and setting a value (previously names action_change)
- on_click_label: optional label of the input displayed when clicking
Coming with an update of jobs that triggered those various changes and cleaning in the gauge widget.
bzr revid: tde@openerp.com-20140211140101-33259mv4i5c1ge7j
- new parameters: input_value_field is now called gauge_value_field, this is the field
displayed under the gauge
- new parameter: force_set: whether to force setting a value when the value is nul
- new parameter: on_click_label: label under the input when editing the gauge value
- action_change renamed on_click_action
bzr revid: tde@openerp.com-20140211100445-289mvmr8grcgns8x
distribute_branding is applied after view inheritance is applied, and does not
take it in account. As a result, altering an existing view "from the top"
(e.g. adding a div element preceding an existing div) will alter the xpath
leading to whatever element we need to deal with.
Move fakebar injection to the bottom of the body, where it can't have any
impact on preceding node paths.
bzr revid: xmo@openerp.com-20140210132855-lwh1ow1tq1e0pidp
Closing previously occured on search request (so that a user wouldn't be able
to select "old" data on new search request), but ``search`` is only triggered
after the search delay. Worked when delay was 0, with it being moved to 250 a
user can get results matching the previous search instead of the current one.
Trigger a closing of the current results list on any ``input`` event, which is
when text is entered in any of the searchview's ``InputView``.
bzr revid: xmo@openerp.com-20140210123416-cfc0x24bfkiv4lse
self.phantom_js(<page_to_load>, <code_to_run>, <global_object_to_wait>, **options)
example:
self.phantom_js("/", "openerp.module.mytest()", "openerp.module.mytest");
console.log('ok') or console.log('error') should be used to signal success or
failure. Other console.log's will be passed to the test logger.
bzr revid: al@openerp.com-20140210004517-jc2cobc31qshxchm
remove deprecated zipfile support
add preload_registry option when server is running
allow registries to be used in contruction in test mode
add a rollback test case for http tests
add a phantomjs helper
bzr revid: al@openerp.com-20140209004005-p5pwym4sqc23vw5b
Thibault Delavallée