* (1, '=', 1) is a noop domain section
* list.append. A thing.
* converting an int to an int is not useful
* search_count avoids having to fetch all product.template ids from
the database just to call len() on the result when it's not
necessary
* when using a dict value 5 times in a row, it's simpler to get it
just once and refer a local variable thereafter
bzr revid: xmo@openerp.com-20131121141647-2w9z2a7b8p5sek22
[ADD] payment_acquirer module, holding :
- payment.acquirer model: models the acquirer with the various credentials (e.g. paypal, ogone). payment_acquirer only contains basic fields. Each acquirer can add fields through inheritance. See payment.acquirer model for more details.
- payment.transaction model: models the transaction itself. Inheritance is done by calling custom methods prefixed by the acquirer name. See payment.transaction model for more details.
[ADD] payment_acquirer_ogone, payment_acquirer_paypal and payment_acquirer_transfer modules. Those are specific implementations for ogone, paypal and basic money transfer. They contain dummy account data, to avoid committing real accounts. Will have to be cleaned before final merge. Those module contain tests but some tests will not work without real account creadentials. To be cleaned.
[ADD] website_payment: a test module for payment. Will have to be cleaned.
[IMP] website_sale: added support of payments in the checkout process. Improved checkout process. Confirmation is now basically a view on a sale.order, and a polling on a transaction to see its status. Context / Session are better managed, but still require some cleaning. Also fixed some links in the shop.
[TODO]
- some cleaning in paypal / ogone about form methods
- improve some tests
- clean checkout process after more tests
- cleaning in ogone server2server + tests
bzr revid: tde@openerp.com-20131121134140-3somglek7dk1o6t1
Indeed render accepts view ID, but the qweb engine does not handle
IDs, only xml_ids. Using the view xml_id field allows to avoid
having a hack in the server.
bzr revid: tde@openerp.com-20131121133309-qq2alstapq5sonkm
- confirmation is now a page displaying a sale order, which polls on the
related transaction to have its status
- when receiving an incoming notification thorugh the acquirer controller
the sale order is updated, then the confirmation page is displayed
- this allows to have a confirmation page that is independant from the
rest of the checkout process
- cleaned confirmation page, removed order details
bzr revid: tde@openerp.com-20131121120902-fm8b7u94gmepohgi
Button implementation turned out to be crap:
* Didn't work at all in Firefox (!)
* Unreliable in webkit, some types of image selection wouldn't
correctly activate the button
->
* changed RTEImageDialog to take an (optional) image element, used as
the "source element" if provided. This allows greater reliability
for events which may leave selection in debatable or variable
(across browsers) state
* setup and teardown button on hover, using selection triggered issues
with oe_overlay thing where e.g. the first click on the button would
work but the second one would not (it'd be intercepted by the
overlay as far as I can tell).
This also saves a click for user, they will see the [Edit] button
immediately when putting the cursor over the image.
bzr revid: xmo@openerp.com-20131121110748-s5e2ne3etpzwi2a6
Christophe Matthieu
Fabien Pinckaers
ddm
Xavier Morel
Fabien Meghazi
Thibault Delavallée