[IMP] web: allow fields in list view to use the attrs readonly to dynamically show and hide the fields

Production : Use the source location of the MO instead of the one of the BOM

When adding an item to the editable list, the focused field was no longer the first visible field
This is related to revision 4a508885
visible_columns list is not ordered

Use the source location defined on the current MO's routing not directly on the BOM

[FIX] fixes searchbar navigation (web client)

the code handling the keydown events was moved, but the variable this
was not adjusted accordingly, resulting in a broken navigation.

It is now possible to press LEFT and RIGHT again to move the focus
between facets.

Removed widge=selection from account_id field in line in Purchase Receipt, as it only displays limited records(100) from the limit set in the name_search

[FIX] l10n_be_invoice_bba: random generation do not use sequence, so should be 10 char long during padding

When `base_crypt` was updated for v7, the auto-encryption
at installation was dropped, with user passwords only
encrypted on-demand whenever the user would connect.

It is important to encrypt all passwords immediately to
prevent password compromission for user who do not
login often or even for deactivated users who are not
allowed to login anymore.

Fixes https://bugs.launchpad.net/openobject-addons/+bug/1280152

Based on LP merge proposal by Nicolas Bessi (Camptocamp):
https://code.launchpad.net/~camptocamp/openobject-addons/improve_auth_crypt_3_please_launchpad_work-nbi/+merge/206476

[FIX] l10n_be_invoice_bba: Fixed the length of random generated code to ensure it generates 10 digit code so that it allows validation of invoice. (Maintenance Case: 608485)

In editable list, on keypress enter, the _next method is called, saving the current line and starting the edition of the next one
The _next is triggered before the date(time) field change event, and, therefore, the saved value of the date(time) field is the old one

Prior to this fix, the domain was set in the onchange methods onchange_company_id. Therefore, if the onchange was not triggered, the domain wasnt apply (e.g. while editing an existing invoice).

[FIX] event: change the field nbevent to make sense

The field nbevent was representing the number of registration with value of 1 for events without registrations (which makes no business sense). Fix to actually represent the number of registrations and display a better field name.

[FIX] account_report_company: display_name field is not computed for non-active partners

[MERGE] mail: Speed improvement, backport of rev ed116d6b

[FIX] hr_holidays: date_from, date_to required in form view only for leave requests, not for allocation requests

Before, the focus was set on the first row, and, thererefore, if the list was enough long, it jumped out and the actual new row was hidden

[MERGE] orm: avoids error when reading twice a field

_read_flat: remove duplicated fields in read call
get many2one: as False is instance of int, check the value of x first to avoid calling a name_get with a list of False

When we were reading twice a m2o field where at least one result is null, the first call to name_get would set the value to False instead of None and then accepted by the filter 'isinstance(x, (int,long))'

Wwhen parsing a integer field, do not accept float values. '1' or '1.0' is ok but not '1.1'. (opw 608544)

sale_order module override state field of sale.oder (sale.sale.py) and forgot to reset the track_visibility, therefore sale orders state changes are no longer tracked once this module installed.

This will make sure already processed rules are persisted
in case a timeout occurs while processing the next ones,
ensuring that *some* progress can be made in most cases.

A safety guard already in place prevents the recursive
trigger of rules while another rule is being executed,
as a simple measure to prevent endless loops.
This guard was missing when processing time-based rules.

A programming error introduced at rco@openerp.com-20121220142445-emzzvhlw400q37c9
fails to properly check when a rule has already been executed in the past.
Time-based rules should only be executed if the trigger date is in the past and:
 - either they never executed before
 - or the last execution date is older than the trigger date

Executing a rule always updates the `last_run` value, which would
always force a useless registry reload to occur. Only signal the
change if the rule applies to a model that was not previoulsy
monitored for base action rules.

[IMP] account.move.line: extra index on (date, id) corresponding to the default _order, courtesy of @gurneyalex.

 Fixes https://bugs.launchpad.net/openobject-addons/+bug/1311004

[FIX] delivery: add missing information in chained pickings

[FIX] hr_timesheet_sheet: correctly set the employee on the attendance

The field note on account.fiscal.position and account.fiscal.position.template should not be translatable in classic modules.
The l10n_multilang module is intendend to make chart of accounts multilang and is the place to set translate=True

[FIX] delivery: do not remove the delivery method on the sale.order when adding it as an order line (useful information)

If the writeoff_amount is above 0, the fields writeoff_acc_id can be displayed and is required depending of the payment option. If the writeoff_amount is reset to 0, this field should no longer be required.

[FIX] report_webkit: avoid sharing parser instance globally and make it thread safe