On 3/2/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > My initial thought is that I'm -0 on the proposal, since I'm not sure it > makes that much of a difference. It is kind of logical, since a project > is a collection of applications and the configuration that ties them all > together. But, inuitively, I think of a "site" as something more > specific still, but I'm not really sure why it is that different. I am > also not convinced that somebody capable of developing in Django is > going to be able to understand "site" and not "project". Let's give our > users some credit.
Particularly if they are programmers. Most coders are going to understand the term project, keep in mind that several major IDEs (Visual Studio, among others) make use of the term Project. (In VS, for instance, in developing an ASP.NET website using a Solution of Projects.) Keep in mind, too, that not all Projects are Sites (and vice versa as mentioned in the Ellington example). I've got at least one Project that I feel qualifies more as a Library, whose applications are often much more useful in conjunction with more site-specific functionality built on top. -- --Max Battcher-- http://www.worldmaker.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
