On 5 Aug 2006, at 3:40, Jeremy Dunck wrote: > On 8/4/06, Antonio Cavedoni <[EMAIL PROTECTED]> wrote: >> I have an initial, rather crude implementation of the Django model -> >> DOT (the Graphviz file format) converter. > > Related: > http://groups.google.com/group/django-users/browse_frm/thread/ > bde9e0928973f14a/08d286888aa781f5?tvc=1&hl=en#08d286888aa781f5
Thanks for the pointer, Jeremy, I totally missed this one when it was posted. I merged some of Andrew Barilla’s ideas in my code (like not having to call modelviz for every model, but rather on a per-app basis), but I think his own is more complete. For example, mine doesn’t yet generate arrows that start from a model property and get to the related model box. I’m just connecting the two boxes blindly. Still, the way I see it, this should be more of a job for a batch script (maybe manage.py?) than for a Django app. That way the only thing that Django has to take care of is to generate the .dot files, then it’s somebody else’s job to take them and render them by importing in a desktop app like OmniGraffle o Graphviz itself and Django itself doesn’t have the dependency of the graphviz codebase just for this nifty trick. > ...And I'm very close to having a graph generator for template > inheritance and load source. Cool, would be very nice to see it! Cheers. -- Antonio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
