> > 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?
Because when I asked fellow Plone developers how settings should be done they told me to stick with portal_properties until plone.registry is complete. I really didn't understand ISettingsPaymentManager by the time and thus I steered away with it, trying to stick something more understandable. Storing settings as annotations in the site root is bad because the settings are "invisible" - i.e. the user has no way to access, except magically guess Python code in Zope debug shell, if things go borked. I believe Alberto rewrote this bit for Plone 4 branch so it should not be an issue anymore. In long term, i think that GetPaid can start utilizing plone.registry and try to decrease the amount of GetPaid specific code. This concerns at least form wizards also. -Mikko -- Mikko Ohtamaa mFabrik - Freedom Delivered. Web site - http://mfabrik.com Mobile site - http://mfabrik.mobi Blog - http://blog.mfabrik.com -- 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 getpaid-dev@googlegroups.com To unsubscribe from this group, send email to getpaid-dev+unsubscr...@googlegroups.com 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.
