I'd rather go the other way - generate a class diagram from django model source!
If you generate model code from a diagram you'll probably still have to edit the source to add new methods or tweak verbose_names, or add Admin meta classes, so then if you change the model you will lose all those changes unless you either put the code into your class diagram editor or have a smart UML-Python generator that preserves code sections - this is the approach of ArchgenXML which produces Python code for Plone content types. But I find the models.py code is as easy to construct as drawing a diagram, but it would be nice to get a diagram of all the foreignkey relationships. This shouldn't be too hard. Just need to introspect your model class and follow the related fields... Hmmm.... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
