[google-appengine] Re: Should I use app-engine-patch or App Engine Helper for Django
Hi Khai, On 13 Mai, 07:53, Khai khaitd...@gmail.com wrote: I've tried to read the articles on using django with appengine, but I am confused. Should I go with App Engine Helper for Django or should I go with app-engine-patch? Use app-engine-patch. It is much more complete and feature-rich and in more active development. I might be biased, though... :) Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use App Engine Patch
thanks for the advice all. On Jan 4, 12:30 pm, Bobby bobbysoa...@gmail.com wrote: I was also undecided on whether to go with Django on top of the GAE but ended up going for it using the AppEngine Patch and i'm glad i did. Yesterday i needed to setup feeds and Django took care of everything in literally a couple of lines - it just keeps on giving. Also, the beauty of self-contained apps (so easy to do in Django) is something you won't be able to go without after having done a few. There are some types of sites where i wouldn't use Django but these are mostly specialized apps (more of web-based applications than content-driven sites). I highly recommend you look into both the AppEngine Django Helper and the AppEngine Patch (create some simple Django apps, go through the documentation for the AppEngine and Django side-by-side), above all it's important you get a feel for what's out there so you can make the best decisions, you'll learn alot about best practices - also see the video Waldemar linked to. Bobby On Jan 4, 8:20 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Jan 3, 6:43 pm, gops patelgo...@gmail.com wrote: think this way :: if there was a need of app engine patch than google would have released it. Actually, Google did release django-helper, but we (app-engine-patch) disagreed about unnecessarily introducing a new model class for Django users. More interestingly, I discussed that with Matt Brown (maintains django-helper) and he agreed with our decision. It would've just been difficult to remove the custom model class, again. and i personally think , webapp is sufficient for pretty large project , afterall * no matter how much django do for you , * atlast for sufficiently large project we endup with our own library-or-framework. Translation: No matter how much time you can save, code reuse is for sissies! ;) Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use App Engine Patch
Hi Ray, On Jan 2, 6:42 pm, Ray Malone rayish...@gmail.com wrote: I'm not sure of the benefits of using the Patch. I have been able to build two good sized apps (1000+ lines of code each) using the App Engine defaults. I know my code is not best practice yet, so I'm looking to learn more and make my next app better. While I like how the models are setup, the process of creating and maintaining an app seems complicated. Can you tell me what I would gain from using the Patch. Thanks Please watch this video, no matter if you choose webapp or Django: http://www.youtube.com/watch?v=A-S0tqpPga4feature=channel_page We put our own Django best-practice into app-engine-patch and we share our experience, so other open-source projects can create better code: http://code.google.com/p/app-engine-patch/wiki/SelfContainedApps Of course, you can implement everything for webapp yourself. But you'll do it alone and you'll reinvent the wheel; and we all started with a square wheel before we got a round one. ;) Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use App Engine Patch
I was also undecided on whether to go with Django on top of the GAE but ended up going for it using the AppEngine Patch and i'm glad i did. Yesterday i needed to setup feeds and Django took care of everything in literally a couple of lines - it just keeps on giving. Also, the beauty of self-contained apps (so easy to do in Django) is something you won't be able to go without after having done a few. There are some types of sites where i wouldn't use Django but these are mostly specialized apps (more of web-based applications than content-driven sites). I highly recommend you look into both the AppEngine Django Helper and the AppEngine Patch (create some simple Django apps, go through the documentation for the AppEngine and Django side-by-side), above all it's important you get a feel for what's out there so you can make the best decisions, you'll learn alot about best practices - also see the video Waldemar linked to. Bobby On Jan 4, 8:20 am, Waldemar Kornewald wkornew...@gmail.com wrote: On Jan 3, 6:43 pm, gops patelgo...@gmail.com wrote: think this way :: if there was a need of app engine patch than google would have released it. Actually, Google did release django-helper, but we (app-engine-patch) disagreed about unnecessarily introducing a new model class for Django users. More interestingly, I discussed that with Matt Brown (maintains django-helper) and he agreed with our decision. It would've just been difficult to remove the custom model class, again. and i personally think , webapp is sufficient for pretty large project , afterall * no matter how much django do for you , * atlast for sufficiently large project we endup with our own library-or-framework. Translation: No matter how much time you can save, code reuse is for sissies! ;) Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use App Engine Patch
On Jan 3, 6:43 pm, gops patelgo...@gmail.com wrote: think this way :: if there was a need of app engine patch than google would have released it. Actually, Google did release django-helper, but we (app-engine-patch) disagreed about unnecessarily introducing a new model class for Django users. More interestingly, I discussed that with Matt Brown (maintains django-helper) and he agreed with our decision. It would've just been difficult to remove the custom model class, again. and i personally think , webapp is sufficient for pretty large project , afterall * no matter how much django do for you , * atlast for sufficiently large project we endup with our own library-or-framework. Translation: No matter how much time you can save, code reuse is for sissies! ;) Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use App Engine Patch
dont use it if you are in learning phase , or not in hurry. think this way :: if there was a need of app engine patch than google would have released it. and i personally think , webapp is sufficient for pretty large project , afterall no matter how much django do for you , atlast for sufficiently large project we endup with our own library-or-framework. On Jan 2, 10:42 pm, Ray Malone rayish...@gmail.com wrote: I'm not sure of the benefits of using the Patch. I have been able to build two good sized apps (1000+ lines of code each) using the App Engine defaults. I know my code is not best practice yet, so I'm looking to learn more and make my next app better. While I like how the models are setup, the process of creating and maintaining an app seems complicated. Can you tell me what I would gain from using the Patch. Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use App Engine Patch
if you need features of django 0.96 then it makes sense to use this patch (or writing your own ...) if not, I agree with gops regards On Jan 3, 2:43 pm, gops patelgo...@gmail.com wrote: dont use it if you are in learning phase , or not in hurry. think this way :: if there was a need of app engine patch than google would have released it. and i personally think , webapp is sufficient for pretty large project , afterall no matter how much django do for you , atlast for sufficiently large project we endup with our own library-or-framework. On Jan 2, 10:42 pm, Ray Malone rayish...@gmail.com wrote: I'm not sure of the benefits of using the Patch. I have been able to build two good sized apps (1000+ lines of code each) using the App Engine defaults. I know my code is not best practice yet, so I'm looking to learn more and make my next app better. While I like how the models are setup, the process of creating and maintaining an app seems complicated. Can you tell me what I would gain from using the Patch. Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
