On 5/1/07, Eugene Morozov <[EMAIL PROTECTED]> wrote: > Building such site on Zope platform is more or less straightforward. > As underlying storage is an object oriented database, every page is an > object.
...snip... > On the other hand, Django uses ORM and this means that each site > section must be separate application with corresponding database and > URL mappings. It seems to me that building large site with different > kinds of sections would be harder in Django. There would be code > duplication and too much manual work to maintain url mappings and > hardcoded hierarchy. As others have said, I don't think these assumptions hold true in practice; don't automatically equate "does things differently" with "makes things harder". On ljworld.com, for example, we've got several hundred different "types" of content interacting, and that's far from being the hardest thing we deal with :) Django helps you out with management and maintenance by encouraging you to write modular code, where related functionality is bundled into a pluggable "application" encapsulating all the relevant logic -- models, views, URLs, custom template extensions, feeds, etc. -- which can then be dropped into any "project" with relative ease. Think of it as encapsulation at a slightly higher level; instead of "all logic related to a weblog entry goes into an Entry class", it's "all logic related to having a blog goes into the 'weblog' application". Also keep in mind that, most of the time, you're primarily working with one type of object on a given "page"; to run with the weblog example, there would be pages which -- while they might display other types of incidental content -- are focused mainly on displaying entries, either individually or in organized lists (and Django's built-in generic views are designed to help you do this while writing as little application-specific code as possible). Incidental content of other types can be easily pulled in via custom template tags, for example, so each view is free to focus narrowly on its primary task. Writing index pages which handle many types of content, as in the case of a site's home page, usually requires a bit more work but still isn't terribly hard if you put a little forethought into the design of the code. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
