OK, I will go on the big Django Community http://www.djangoproject.com/community/
Bye bye :-D On Aug 31, 12:36 am, Michael Schreifels <[EMAIL PROTECTED]> wrote: > On Aug 30, 4:25 pm, Davide Rognoni <[EMAIL PROTECTED]> wrote: > > > Not Google but: > > > “Guido just pronounced: Django is the [Python] web > > frameworkhttp://www.cmlenz.net/archives/2006/08/the-python-web-framework > > So what? Guido likes > Django...http://www.djangoproject.com/weblog/2006/aug/07/guidointerview/ > > FYI if you listened to Guido's talk on building Django apps on AE at > Google I/O this year, he said that "Django is just one of many > frameworks you can use." The talk is available online. > > On Aug 30, 4:40 pm, Davide Rognoni <[EMAIL PROTECTED]> wrote: > > > fromhttp://www.cmlenz.net/archives/2007/06/logic-in-templates > > > """How could a custom, sparingly documented, somewhat inconsistent, > > and mostly unproven (compared to Python) mini expression language be > > any better for template authors?""" > > I wasn't using Django over a year ago when that was published (just > think: that was when oldforms was still in, eeek), but I will say one > thing: out of all of the frameworks and libraries I have used, Django > is THE best documented web framework I have ever come across. Also, > that quote is comparing how proven an entire language is to a mere > collection of template tags and constructs... > > > """In my humble opinion, this kind of “dumbed-down” templating results > > in only one thing: more lines of code in the application modules, > > lines of code that are really only about presentation, and should be > > in the templates. And frustration every single time you need to add > > those lines.""" > > So Django templates aren't for everyone. Django was designed to be > loosely coupled so you can stick in your own preferences where > desired. > > On Aug 30, 4:05 pm, "Noah Gift" <[EMAIL PROTECTED]> wrote: > > > I think for new comers to Python, it IS presented as the only choice > > as many people would have difficulty "monkey-patching" another > > template engine, as there have been issues in getting, to my knowledge > > at least, Mako and Genshi to fully work on appengine. It seems like > > this new cookbook area would be a good spot to for developers of those > > other templates to put their integration recipes: > > If I wanted to work with PHP and didn't like the fact that it allowed > my designers to access PHP, I could certainly choose to use a template > language. But of course, it is going to involve overcoming a barrier > to implementation. Django templates works great for most people. For > those who it doesn't work for, they should be prepared to have to do > some extra work. Besides, for beginner's needs, what exactly is it > that Django templates doesn't work for? > > Django templates is incredibly newbie-friendly. As mentioned, the > documentation is (IMO) second-to-none, and there are other great > resources, like the free talks available online covering Django, and > djangobook, which is mostly up-to-date. > > But still, I don't think this conversation is the appropriate place > for this discussion. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
