Not sure if this makes sense, but perhaps introducing the thought of creating a "Generic" product whose sole functionality is the ability to be added to a satchmo cart. Any views, urls, business logic etc would be dependent on the developer to create, assuming this his/her products all extend this "Generic" product.
Simply by extending GenericProduct, any model could be added to the cart. You could still keep the other models "as-is" and if they work for a given project, then great. (To me, the standard "Product" model in Satchmo seems to try to do so much). I think an addition like this would impact the existing model structure very little. My other idea was modify the cart so that any django model could theoretically be added to it, but I worry that it would create too much backwards incompatibility. I dunno, perhaps these are both bad ideas...just tossing it out there. On Tue, Nov 3, 2009 at 6:07 AM, bobhaugen <[email protected]> wrote: > > On Nov 2, 9:43 am, Chris Moffitt <[email protected]> wrote: > > I'm open to ideas on improving the product models. However, I'm not > > convinced we can do it in an easy way. > > Probably can't, but maybe if the product model gets split out and so > can be replaced by people who have better ideas, or experiments to > try, or different requirements, it would open the door without a major > disruption. > > (I assume that was what Bruce Kroeze meant by "pluggable product model > mapping".) > > > > -- http://www.sudovi.com/ http://www.twitter.com/lifewithryan http://www.thecommontongue.com http://www.lifewithryan.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
