> 1. the view class imports Oscar classes relevant to the checkout process and create instances to simulate the add to cart to payment process.
Actually sounds reasonable - you're re-using most of the checkout code, and can plug in any necessary custom logic in between the steps. > Option 2, the view class inherits from classes involved in the checkout flow, but it will be a subclass of more than five classes [...] Incredibly ugly, smells, and almost certainly won't work without even more hacking. My advice is to just go ahead and build a prototype. If it works, you're 90% there - just clean it up, document it, and ship it ;) <3,K. -- https://github.com/tangentlabs/django-oscar http://django-oscar.readthedocs.org/en/latest/ https://twitter.com/django_oscar --- You received this message because you are subscribed to the Google Groups "django-oscar" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-oscar+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/django-oscar. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-oscar/721fdd6b-a387-430c-9e40-b2d8526bc943%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
