- Few small easy mistake fix (typo)
- Define _bound_dimension_id in _setup_complete method instead of __init__

The method calls get_object_reference or _update try to look up information
in the _columns of the object. But at '__init__' time, the object is not properly
finish and _columns is None.
By moving last initialisation in _setup_complete we are sure that object is initialized.

We need to keep the old api to be sure that 'self' is really the object.
If v8 api 'self' is a records set and we can't set _bound_dimension_id.

Main changes are :
- Change fields declaration
- Update metaclass to add field to nmspc instead of _columns
- Add v8's version of compute/reverse/search function of
    disable_per_company field

The field analytic dimensions is now a function and not a char to avoid the creation of a database column

Bound dimensions: if an analytic code ID is passed to create or write, it will be ignored unless the key "force_code_id" is set to True in the context.

Add some help

Para-analytic are created and named according to the structure but do not take analytic codes as values. Instead, they can be any kind of field.

The analytic_structure method analytic_fields_subview_get allow any model (not necessarily one that implements MetaAnalytic) to display the analytic fields of models that have subviews defined inside its views. It is still strongly recommended to use ir.ui.view records and the [type]_view_ref context key instead.

Structures can now be restricted to one company. Bound dimensions: added the code_ref_ids (and code_ref_module) options to generate external IDs for all analytic codes of the dimension.

Bound dimensions: fixed an issue with the initialisation of related fields. Can now define the analytic code field in data (XML or CSV) files. Fixed a bug with the name methods.

Added 'usable' field in analytic.code. Analytic fields now filter out the codes with usable=False rather than those with children. Added the rel_name and rel_usable options for bound dimensions.

Can now import data for a module bound to a dimension through the default method (many2one field w/o inherits), without having to create or reference the analytic codes. Default value for ref_module is now '' (empty string).

The MetaAnalytic metaclass can now be used to bind a dimension to a model, generating a new code for each new record.

The README has been updated with more instructions.

Fields generated by MetaAnalytic now exclude codes with children. Fixed some issues when selecting the parent and dimension of a new analytic code. Added a new 'translate' option.

When creating a code, the parent cannot be selected (readonly) if the code's dimension is not selected (code view) or not a record in the database (dimension view, while creating a new dimension).

Added descriptions to models. Added a 'translate' option to enable/disable translation of analytic code and dimension names (default: False). Fields generated by the metaclasses now have a common placeholder string value. Cleaned up the translation file.

Can now use <div class="oe_analytic" prefix="prefix" /> in order to place every remaining field associated with a structure in the view. Added a README.

Also added a config check on module load.

The number of analytic fields can be defined in the OpenERP configuration file, category [analytic], key analytic_size (default: 5).

The default behavior is unchanged.