Launchpad automatic translations update.
Launchpad automatic translations update.
[FIX] ir.translation: backport of trunk fix to allow editing master english source terms

Original trunk commits rev-ids:
 - 4855 qdp-launchpad@openerp.com-20130416091501-sgm3gdm80oxajahz
 - 4856 qdp-launchpad@openerp.com-20130417121718-jfwi2f3gn0tum9xa
 - 4857 qdp-launchpad@openerp.com-20130418114627-unmfdu6010hyc8xx
[FIX] ir.translation: backport of trunk fix to allow editing master english source terms

Original trunk commits rev-ids:
 - 4855 qdp-launchpad@openerp.com-20130416091501-sgm3gdm80oxajahz
 - 4856 qdp-launchpad@openerp.com-20130417121718-jfwi2f3gn0tum9xa
 - 4857 qdp-launchpad@openerp.com-20130418114627-unmfdu6010hyc8xx
[FIX] ir.ui.view: properly validate newly created inheriting views
  
  When a new inheriting view is imported during a module
  installation, it is validated thanks to the _constraints
  on the ir.ui.view model. However the validation uses
  a rather convoluted system for validating the whole
  view tree at once (root view + all inherited changes)
  while only taking into account the views that belong
  to modules that are currently loaded.
  
  This complicated system is necessary to be able to
  operate on-the-fly at any point during the registry
  loading/initialization.
  
  Now because _constraints are checked during create()
  this particular validation happens *before* the
  external ID (ir.model.data entry) of that new view
  can be created (it obviously needs to wait until
  the view record is inserted). As a consequence the
  view validation cannot determine the module to
  which that new view belongs, and was erroneously
  ignoring it.
  Changing the view filtering to also include views
  from unknown modules fixes this transient problem,
  and also means that manually created inherited
  views will be validated during module init too.
Launchpad automatic translations update.
Launchpad automatic translations update.
[FIX] ir.ui.view: properly validate newly created inheriting views
  
  When a new inheriting view is imported during a module
  installation, it is validated thanks to the _constraints
  on the ir.ui.view model. However the validation uses
  a rather convoluted system for validating the whole
  view tree at once (root view + all inherited changes)
  while only taking into account the views that belong
  to modules that are currently loaded.
  
  This complicated system is necessary to be able to
  operate on-the-fly at any point during the registry
  loading/initialization.
  
  Now because _constraints are checked during create()
  this particular validation happens *before* the
  external ID (ir.model.data entry) of that new view
  can be created (it obviously needs to wait until
  the view record is inserted). As a consequence the
  view validation cannot determine the module to
  which that new view belongs, and was erroneously
  ignoring it.
  Changing the view filtering to also include views
  from unknown modules fixes this transient problem,
  and also means that manually created inherited
  views will be validated during module init too.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.