On 5/1/08, joasch ([EMAIL PROTECTED]) wrote: >this is what I have done. I checked out satchmo trunk and keep it >updated. After checkout I exported it to a new copy and check it in on >my own SVN, and there I make my changes. When ever there is a change >in satchmo trunk I merge these changes into my own copy. It's a bit of >extra work but that way I can take advantage of improvements and bug >fixes in main satchmo and also make patches if I do something of >benefit for satchmo.
After further investigation I came to the same conclusion - branch and 'cope'. I have been setting the groundwork to follow this path and am brushing up on merging, etc. As a solo developer, I don't normally have to worry about what others have been doing; I still have acres to learn. >It might be possible to do it some other way, but I like to develop in >line with newforms-admin branch and have done these changes to "my" >satchmo, as well as some other structural changes I hope to offer back >once they branch to start develop with newforms-admin as base. I was hoping there was some brilliant way to do what I need, but alas such is not the case. A benefit is that the Satchmo project has been done very well so far and I don't expect that to change (unless maybe they start foolishly accepting my code - LOL). >I read your post in satchmo group but don't really have any input for the >special things you trying to achive. In fact, I am pretty new to >django/python as well coming from php. My requirements regarding 'product' and to some degree 'customer' managment are so far away from a typical e-com site that it isn't a trivial task. >If you are interested in using newforms-admin there is a script here >http://www.djangosnippets.org/snippets/603/ which help you to do this >change quite easily. That's what I used and the script really works. I've been reading about newforms here <http://code.djangoproject.com/wiki/NewformsHOWTO> but have yet to put it into action. That will change any day now - I appreciate your pointing me to the script. Scott PS. I did check out the dispatcher and signals as suggested by Rajesh - woah! Python & Django just keep getting sweeter by the day. Photologue has an interesting implementation and when I first encoutered it there, it didn't make sense but these articles helped imensely: <http://www.mercurytide.co.uk/whitepapers/django-signals/> <http://feh.holsman.net/articles/2006/06/13/django-signals> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
