Thanks for your thoughful reply. I've succeeded in installing Satchmo into my project now and I see what you mean. I like the design you have chosen - the idea is not to "extend" the core functionality but embed it as a service and then use the funcationality provided.
I can see the real way to add new and custom functionality would be via the "signals" mechanism rather than overriding some class or hacking the underlying code. That's a good decoupled design, I'm encouraged to continue evaluating satchmo as I think it could be a nice fit for what I want to do. My main concern is disabling features I do not need. Three concrete examples: 1. Subscription stuff. 2. Discount codes. 3. Multisite - I will never need multisite. Is the core stuff sufficiently abstracted from these "non core feature bundles" I can just yank them out? And still be able to update to a newer version of Satchmo with minimal work? Or do I need to just accept the underlying models will alway reflect them and comment them out in templates and by manipulating the admin screen? If it is the latter is there a plan to refactor some of this stuff out into optional modules? Many thanks, Jim. On Dec 22, 2:49 pm, Chris Moffitt <[email protected]> wrote: > I don't think I'd call Satchmo a "monolothic knot of code" and I definitely > don't want people drinking Kool-aid :) but I'm not sure that Satchmo allows > you to just pick and choose just the parts you need. > > There are some places where you can simply disable an app and not use it and > there's no problem. There are also places where you can easily customize > your own pieces - like shipping and payment modules. We also try to make it > easy to override parts of the template, hook into signals or replace views > with your custom views. However, there are other places where the > integration may be a bit tighter than you would like - especially when it > comes to the product models. We try to loosely couple but it's not that easy > for you to plug your custom product model in instead of Satchmo's. > > If you can give some more details about what you'd like to pick and choose, > we might be able to help you figure out how easy or hard it might be. > > -Chris > > > > On Tue, Dec 22, 2009 at 12:16 AM, Leonig Mig <[email protected]> wrote: > > I want an ecommerce framework I can pick and choose from- is this > > approach possible with Satchmo. > > > Or am I required to instantiate some monolithic knot of code and drink > > the kool aid? > > > I am evaluating satchmo atm so would value any viewpoints. > > > -- > > > 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]<satchmo-users%2bunsubscr...@goog > > legroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/satchmo-users?hl=en. -- 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.
