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.

Analytic scructures can now use different ordering values for the same dimension. Models that use analytic code fields should now use conditions on nd_id.ns{n}_id.model_name in the domain for those fields.

Added a parent-child hierarchy on analytic codes. Fixed a bug where analytic codes without a description couldn't be selected.

ields that are marked as invisible in the view are no longer displayed.

This method should be used in order to retrieve the analytic field ordering numbers and/or names from outside the analytic_structure module.

the view.

When updating the invisible and tree_invisible modifiers, the analytic_fields_view_get method used to override the entire "modifiers" attribute. This isn't the case anymore.

These methods should be called by models that implement analytic fields, respectively in their fields_get and fields_view_get methods.

new group group_ans_manager, people of this group can create analytic structure

This view is editable in tree view