Hi Chris,
"And it's rather not extending the ipc module to add a certain parameter in the catalog context, but the catalog module. I would recommend to define your custom version of IPCPriceCalculatorCRM in backendobject-config and override"
Question of approach.. Tomorrow we have another module that uses IPC (not just the Catalog) and what do you do? - Either you duplicate code or you inject some crazy BO/BE coming from the Catalog.. what's the logic behind this approach? - IPC it's a component of the equation itself, and unless there are some 'Catalog Specific' settings that needs to be passed to IPC, the Catalog is always the wrong place to place the logic.
IPC is disconnected from Catalog and have no 'dependency' whatsoever, so extensions *should* reside in the IPC module (an extended module) - and the Catalog may fetch the BO from there if needed adding extra functionality that really relates to the Catalog module. (now in the Catalog module)
I understand that WCEM was *designed* to work the way you said, but IMO it's just wrong and I would never adhere such approach (nor recommend others).
Image may be NSFW.
Clik here to view.
Cheers,
D.
