openerp-expert-accounting team mailing list archive

[Alexis de Lattre <alexis@xxxxxxxxxx>]

Thanks to all of you for your answers. I understand that the INSTAT XML
file standard hasn't been adopted accross EU countries.

So my conclusion is that it will be quite difficult to have a lot of
common code, because we will obviously have many differences between
countries.

We could try to split the code between generic modules and
country-specific modules. But, if you look at it, what would the generic
(i.e. non-country-specific) module contain ? It would contain :
- the intrastat field on res_country
- the object report_intrastat_code
- the country_id and intrastat_id fields on product_template
and that's all. And only the first one would be needed for service-only
companies ; the product-companies would need them all.
So that would mean having 2 generic modules :
- report_intrastat_base, with only the intrastat field on res_country,
- report_intrastat_product_base with the object report_intrastat_code
and country_id + intrastat_id on product_template.
These 2 generic modules would be very small with just a few lines of
code in each. I don't think it makes much sense.

So, instead of doing that, I propose that we develop country-specific
modules and we try to keep, in each of them, the same name for the basic
fields and object, i.e. the names that are used in the current
report_intrastat module of the addons. That way, a user which first
tried to use the "report_intrastat" module from the addons would just
need to uninstall it and install the country-specific module(s), and he
would keep the data that he already entered.

Do you agree with my proposal ?

If yes, then I will rename my work on put it somewhere in the
extra-addons. I think I will have 3 modules :
- report_intrastat_base_fr (which would conflict with report_intrastat)
- report_intrastat_product_fr (depends on report_intrastat_base_fr)
- report_intrastat_service_fr (depends on report_intrastat_base_fr)

Regards,

-- 
Alexis