[google-appengine] Re: Django+Appengine vs Appengine

2008-12-21 Thread Waldemar Kornewald
Hi, On 20 Dez., 23:15, Bobby bobbysoa...@gmail.com wrote: The MVC, self-contained, DRY approach offered by Django is what really sells it for me at this point (even with the reduced feature set on the AppEngine). I saw this great video from DjangoCon that really outlines this strength of

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-20 Thread luismgz
On Dec 15, 4:58 am, Bobby bobbysoa...@gmail.com wrote: In addition to this i'm seeing that the Django admin site has been replaced by the AppEngine data viewer which isn't as powerful or customizable right now, so i'm not seeing alot of reasons to use the Django framework (other than

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-20 Thread Bobby
The MVC, self-contained, DRY approach offered by Django is what really sells it for me at this point (even with the reduced feature set on the AppEngine). I saw this great video from DjangoCon that really outlines this strength of Django:

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-19 Thread Waldemar Kornewald
Hi, On Dec 19, 3:13 am, boson dan.kam...@gmail.com wrote: Now considering the facts that a) lots of the good bits from Django are either included in GAE (templates) or don't work with GAE (some of the admin stuff), b) the version of Django that works out of the box is old (.96), and c) the

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-19 Thread boson
On Dec 19, 4:26 am, Waldemar Kornewald wkornew...@gmail.com wrote: There's nothing magic about the workarounds. In app-engine-patch there's a sample project which gets you started immediately with the latest stable release. Everything that's need is placed in a folder called common and in

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-19 Thread fede
What about internationalization?. I didn't find anything in webapp (and there is in django). That was one of the most important reasons I'd go with django... On Dec 19, 5:00 pm, boson dan.kam...@gmail.com wrote: On Dec 19, 4:26 am, Waldemar Kornewald wkornew...@gmail.com wrote: There's

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-19 Thread Alexander Kojevnikov
Like I said, it's been hard enough getting up and going with just GAE.  Every additional piece is more configurations, more documentation, more forums, more possible bugs, more possible constraints, etc.  It looks like the app-engine-patch developers (you?) did a good job bringing newer

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-19 Thread johnP
Another +1 compliment for the Patch. It is a wonderful gift to the community. Waldemar Kornewald deserves big Kudos. Thanks - it rocks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-18 Thread boson
Personally: I haven't used Python in a few years, and I've never used Django, though it looks good. Most of my recent web work has been LAMPish (including large structured OO projects in PHP 5). I've found the learning curve with GAE to be pretty immense but presumably worthwhile. I'm very

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-15 Thread Jesaja Everling
Well, Django doesn't really extend App Engine with more functionality, because you probably could do everything you could do in Django in webapp and vice versa. What are the main advantages of using Django on the AppEngine? Well, if you ask me that would be support from the Django community

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-15 Thread Bobby
Ah, good point about being able to make use of existing Django apps. Thanks. Bobby On Dec 15, 2:46 pm, Jesaja Everling jeverl...@gmail.com wrote: Well, Django doesn't really extend App Engine with more functionality, because you probably could do everything you could do in Django in webapp

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-15 Thread Bobby
One note on portability, for example for retrieving all objects in the datastore, sorted, in Django one could do: Poll.objects.all().order_by(...) Whereas in AppEngine it complains that order_by isn't defined, and i have to use the AppEngine's version: Poll.objects.all().order(...) Also, when

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-15 Thread Alexander Kojevnikov
The problem with built-in djangoforms and templates is that they are from Django 0.96. Django 1.0 has a lot of new useful functionality, it really worth the trouble installing it with your app. Another advantage of Django is that it allows to implement custom user authentication, this is

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-15 Thread Alexander Kojevnikov
This is using the AppEngine helper (not the patch you linked to). I thought the AppEngine helper would make sure that the Django model methods would delegate to the AppEngine's version transparently but some seem to be missing - why is this? app-engine-patch does not try to replace appengine

[google-appengine] Re: Django+Appengine vs Appengine

2008-12-15 Thread Bobby
I like the Appengine Patch's approach the best so far, i think it's quite good. I'll stick with Django in hopes that eventually most of the missing Django features and apps will be ported over (either by the Django AppEngine-Helper or the AppEngine-Patch). Right now i've got nothing to lose.