Hi, With the latest developments, I started to write a lot of glue modules like:
- purchase_shipment_cost_percentage
- sale_shipment_cost_weight
and I start to need one more purchase_shipment_cost_anglo_saxon because
the accounting move when the unit price include shipment cost must be
splitted.
All this glue modules don't add new functionality but fix existing one
because 2 (or more) modules are activated on the same database.
I think it means there is something wrong with this design.
So, I would like to know what is your feeling about having some code in
some modules that tests if an other module is activated or not? It will
be a little bit like duck-typing.
By the way, we already have some code with such design like the template
in the module product or the grouping of shipment in sale and purchase.
The main issue, I see in this way, is that some feature should need to
wait a new release to be added. For example, the purchase_shipment_cost
can not be developed for 2.2 as it will require a modification of
account_stock_anglo_saxon.
A second is about testing, it will be harder to test such part of the
code because by default the extra-module will not be installed.
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/
pgp3TakaUq6xn.pgp
Description: PGP signature
