Guillermo Fernandez Castellanos wrote: > I've been following the discussion with interest. I've seen that many > of you have concentrated on the actual code. But something I would > find also helpful/interesting is a "standard" model of blog. Or, to > push the idea further, a djangoforge of models. > > Often, the model is one of the parts that must be right from the > beginning. And a common model would be ideal for interoperability > between applications, in this case blog applications, allowing easy > migrations.
I second that. Actual code may vary, but domain model (and its representation as Django data model) would remain constant, as long as software will be performing similar tasks. Cheers Jarek Zgoda --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
