> "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. > What i failed to grasp of Brandon's branches is the reason for the > differentiation between onsite and offsite payment processors and why > there can be only one of the former active per site. If someone with > more experience of the two different solution can point out what's on > Brandon's code that is missing on Mikko's, i will volunteer on merging > the two.
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 wish (UI / engine / non-Plone abstraction). With Satchmo / LFS you just know where to enter your hooks and it works. > Asko> And after that there's a nice awaiting Sales Tax > Asko> implementation (for us Europeans) in Mikko's > Asko> "miohtama-taxes"-branches, but those again are based on > Asko> Brandon's branches... :) > > never looked at it, my shop will sell stuff with clients that that don't > need to know anything about vat and other taxes. I can help to backport it to (Plone 4 ?) branch. It was not too many files. The work was done on Brandon's branch as it was enjoying the most of the development by the time. I also took some shortcuts and did not taxes in so abstract way than they were in getpaid.core, but simply allowing you to enter one value which is VAT. I hoped to achieve something at least marginally useful instead of making "super duper handle every special case" code. > Asko> Finally, I'd be personally interested to enhance the current > Asko> Currency Options with "currency_formatting" option (should the > Asko> currency symbol be rendered before or after the currency > Asko> value) from hannesc's branch (see: > Asko> > http://groups.google.com/group/getpaid-dev/browse_thread/thread/1956c8017245532a). > Or > Asko> does someone oppose it? I think there are getpaid.core options for more rich formatting, we just lack the settings interface to enter then. Also, I wrote some custom code for taxes and getpaid.atshop so that there is not only "currency formatter" but also "tax aware formatter" which knowns when to enter taxes in the price. Then here are cases like "sale price formatter" etc. where one could consider colors. But having a currency symbol is a start. -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
