On Tue, 2008-12-02 at 18:39 -0800, Tonne wrote: > I am interested to see if anyone could share their solutions for > ensuring pretty HTML output. > > I have found achieving it to be a very uncomfortable compromise in > that I seem to need to make my templates almost unreadable to do so, > which isn't really a practical solution. > > Perhaps nicely formatted HTML markup is simply not a worthy priority > in the greater scheme of things Django. Which is a bit of a pity, as > I've always appreciated well-manicured HTML, and it has been a point > of professional pride to make my own handwritten HTML as readable as > possible.
You're right: there's a trade-off. Almost every single piece of machine-generated HTML makes that trade-off. You trade off output formatting that hardly anybody will see for speed. Every professional worth their salt strives to write neat and tidy source. If we're writing HTML source, it will generally be neat and tidy. In Django, we're more regularly writing template source, so that's the bit that is edited over and over and is formatted for readability. There's been a bunch of discussion about this and the conclusion is this: if somebody came up with a way that wasn't eye-bleedingly ugly in the Python source to remove any blank lines that only contained template tags from the output, we would include it. However, it should not slow down template rendering. A few people tried to do this on a very old ticket and came up with 25 - 50% slow-downs, which is simply unacceptable. I had a shot once and got something that was close to comparable with the current speed, but it was really messy. Since then, it's been back-burnered as there are other things to be fixed in the template rendering space before worrying about stuff like this. The problem is much harder than it looks on the surface, so it's not out or orneriness that we have avoided including anything. By the time you factor in readable templates, nested templates, included HTMl from template tags, etc, the resulting generated HTML is only one aspect of a multi-faceted problem. However, if really regularly formatted HTML output is a requirement for you and you can pay the speed penalty, you could run the results through something like TidyLib (from the HTML tidy project) or similar before serving it. I could imagine it wouldn't be too hard to write a middleware that did this for all text/html (and similar) results. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
