On 08.04.2010 23:23, Mikko Ohtamaa wrote:
"simplest" and more clean solution. The differences between the trunk
and multiplepaymentprocessors branches are some "insertion points" into
checkout and configuration and a registry of the payments methods.
I think GetPaid just needs more plug-in points. User Interface plug-in
points specifically. Getpaid core is little too abstract and sometimes
feels that technology drive has taken it too far, so that it is damn
difficult to make it work the way you wis.
Btw, is there some specific reasons, why installing and configuring
multiple payment processes must be totally different from installing and
configuring multiple shipping methods/services?
Of course, this is a bit theoretical questions, since there is not many
shipping plugins available. But since I spent my afternoon trying to
understand how getpaid.ups installs its using getpaid.core's
IPluginManager and makes its configuration available using
PloneGetPaid's ISettingsShipmentManager, I must ask, why the same
approach on payment processor configuration (ISettingsPaymentManager)
was abandoned?
:)
-Asko
--
GetPaid for Plone: http://www.plonegetpaid.com (overview info) |
http://code.google.com/p/getpaid (code and issue tracker)
You received this message because you are subscribed to the Google Groups
"getpaid-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/getpaid-dev?hl=en?hl=en
To unsubscribe, reply using "remove me" as the subject.
