I recommend to get a good overview about concepts. Yesterday I discovered Bruce's lecture on signals at DjangoCon 2009. Bruce Kroeze: Custom Signals for Uncoupled Design, (video 26 min) It's about Satchmo signals, but the word Satchmo there fits never http://blip.tv/djangocon/custom-signals-for-uncoupled-design-3088044 slides from this - but more efficient is to look at the video first. http://www.slideshare.net/ecomsmith/custom-signals-for-uncoupled-design
This is the biggest difference between Django concepts and Satchmo. People ask: why Satchmo does not accept some Django conventions and we not understand it? After the lecture I understand well. Other good resource is lecture about Satchmo at DjangoCon 2008 http://www.youtube.com/watch?v=d42a4g650Ws&list=PLD415FAF806EC47A1&index=17&feature=plpp_video&noredirect=1. Some concepts were not initially implemented in Django and now they are. I think that during lifetime of Django 1.4 we should do some decisions about. I trying to comply with Django and Python coding recommendations. For short parts of code is better to preserve the continuity with the existing. Lenght of line is better under 120 chars due to Bitbucket code browser, but conventions in Satchmo are very different. Chris do you have some older resources? Some missed, e.g. all four links at http://gosatchmo.com/apps/ On 10 pro, 14:15, Puneet <[email protected]> wrote: > Hi Chris, Hyneck, > > Do we you have any design or implementation specific document ? > > I want to understand more about satmacho and contribute in the longer run. > > Thanks, > Puneet -- 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.
