Mar 17 notes at end of sprint:

Checkout options: click on add to cart and get review viewlet. portlet gets options

• Interface: 

• incorporate "view cart" in personal pathbar (when have item in cart)

Viable content: not doing ContentFlavors, but using a marker interface to change default view. Use z3 form to override the edit template (call it and add to it). TAB to view. For "shippable" is "product", for "subscription" is "premium".

Subscriptions Case Ideas

• This is not interfering with the default registration process, but adding additional features for "premium" membership levels

• How to handle upgrade of membership (Premium1-->Premium2)? Could be done with discount code (ie existing Premium1 subscribers enter a discount code for the Premium2 when purchasing that membership to get a price that reflects the difference in value). 

• User view of content that is premium content gives the link/button option to buy membership/subscription

 
  default UI for purchasing subscription is to be made by integrator.
  select membership, review cart, go to payment area. on successful payment, add member to group, redirect them back to content bought
 
How to do?
- Nate's product with membrane/remember, but preferably a way that doesn't need those products...

signing up is registration, then cart/subscription process

- config payment processor: don't require pay processors to implement own UI (don't want to be zope2 specific). make pay processor configuration viewlet in PloneGetPaid that gets Ipaymentprocessor options and displays the edit screen for payment processor.
- plone UI: we plug into plone (not changing or overriding); might become an issue on premium subscription (re view changes that happen). ***look at how premium membership changes the membership process, how to sign up.
- checkout screen
- implement full payment processor that requires events (re status); callback service to notify when something is successful. Needed immediately for
- config processor: use viewlet system; each processor registers a viewlet. When select processor, saves it. another form in same page appears with options (and a "change" button). Means that all processors will depend on z2 for the UI (if they provide a view to their configuration); but if they provide an interface then can be z3. The configlet can switch over the interface to be a viewlet manager ()

Task: Set up viewlet manager for GetPaid management interface (then people can plug into it from outside the product). Plone3 interface is all viewlet space.
- Shopping Cart Views:
Portlet view: add what you are currently view to cart; buy now.
Edit cart: add/delete items, continue shopping, change quantity; use zc table; is default view after you add an item to cart.
Checkout: discount code
Viewlet manager for shopping cart review: (where you are redirected to after you add an item) to add in things like "other people also bought this..."