By users I meant users of the Django framework, not end-users. Since my last post I came across a few models (the ones you suggested) that do have a great deal more logic than I expected. I still believe that many 'developers' could benefit from defining simple to moderately complex models on the web. If code needs to get more complex, developers can just switch back to using models.py.
As far as I can tell, part of Django's motivation is that the repetitive parts of the development cycle should be made easy and quick. I have written many applications which were nothing more than taking data form a database and putting it on the web...nothing complex. Something like what I propose would make web apps trivial. As far as developers getting bad habits because of the ease of creating and changing models...doesn't that make Django itself Bad(TM)? I wasn't able to find an outline of the most important classes and how they relate to each other, from the perspective of a django framework developer. I may like to experiment myself. James Bennett wrote: > On 5/3/06, falcon <[EMAIL PROTECTED]> wrote: > > I wonder if you could say a few more words about why you think such a > > system will be abused? As far as I can tell, the models.py interface > > is simple enough to be ported completely to the web (it doesn't look > > like models.py is where you put complicated logic). If anything, users > > could receive immediate feedback rather than having typos or syntax > > errors show up when only when they try to load the page (as I'm going > > through right now). > > Well, the first thing that occurs to me is to comment on your use of > the word "users"; "users" should *not* be creating new models. This > isn't developer arrogance coming through, just a recognition that most > places are going to have people who can think in terms of object > relationships (and, more importantly, in terms of fields and relations > in an RDBMS) and come to the most efficient solution more quickly; > these people are called "developers" and, if anything, they're more > comfortable in a text editor than in a web interface. > > Also, developers are more likely than anyone else to know what sorts > of fields and object types are available across the base of installed > applications and, thus, what to take advantage of in designing new > models; for example, on a news site a user might not realize that a > "video clip" model exists already, and so might create a new type of > story which takes the URL to a video clip instead of a foreign key to > a video-clip model, while the developer would (one hopes) know this > and be able to leverage the relational model more effectively. > > Going further, it seems to me that, rather than encouraging the design > of good, well-thought-out models, building models through a web > interface would encourage a slapdash "if we get it wrong we'll just go > into the web interface and change it" mentality, which would be a > certifiable Bad Thing(TM). > > > -- > "May the forces of evil become confused on the way to your house." > -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
