More issues: One cannot present paymeny processor options as a schema reference (options_interface). They payment processor must be able to customize its own form view as zope.schema cannot be used to express all form use cases (custom widgets and so on...).
-Mikko > I just went through Brandon's work. Looks nice to me, though there are > some show stopping issues. > > The offsite payment processor interface was empty. It is very > difficult for third parties to implement payment processor unless > interfaces are documented with the required precision. > > If I read the core correctly there can be just one on-site payment > processor. Also, the wizard step to choose payment processor is > missing. > > As is, this work is useless for many use cases, like > > * Having a wire payment processor > > * Choose between credit card and wire payment > > * Choose between different on-sites processors (imagine different > processor for different credit cards) > > What's the status of the future of Brandon's work? In > multiplepaymentprocessor support for these use cases exist. > > I am willing to help to merge multiplepaymentprocessor branch with > brandon and brandon branch with trunk if > > 1) Community "decision making process" sees this as a necessary > requirement for the future > > 2) There is someone else willing to put hours on the issue > > -Mikko -- 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
