Hi Mat, I'm a bit of a newbie myself, but for once I actually think that I can answer some questions here myself - mostly because I've wondered some of the same things.
> 1. Firstly one of best things about symfony is the debug toolbar which lets > developers see whats going on, it really is an amazingly useful piece of > development kit. Just to give you an idea it shows, time to execute each > function call, what was from cache/generated, all SQL statements and all the > php setup etc. I couldn't spot anything like this in django (or any other > framework for that matter), but thought it would make an awesome addition, > any thoughts? Or have I just missed this in django, the 500/404 pages are > excellent though, but this allows you to see similar info for pages with > bugs which don't cause a fatal error. There's a lot of debug info available under certain preconditions fulfilled by settings. When these conditions are met (DEBUG = True, INTERAL_IPS is set etc, see the docs[1]) there is a built-in template tag that prints out basically the same stuff you get from the error pages. I've also come across a very useful snippet on djangosnippets.org[2] that also prints out all the SQL-queries run and the time it took in a template tag. > 2. I cant believe django doesn't include this, so I figured where best to > ask. Again I apologise to the reference to symfony, but I'm trying to figure > out if django has an equivalent to components in symfony. I'll give you an > example. If you have a nav menu on a website which is on most pages, but the > contents of the navmenu change depending on the url and/or the user status, > so essentially it has to be generated on each page load if required. In > symfony the solution is to design a component template, and include this as > though it was a normal templates on any pages where it is required. The code > to generate this template is then stored in the components class and is run > only whenever the component template is included. This gives you the > advantage of cleanly separating the code behind the scenes and stops you > having to include the code on every request. I guess this could be included > in middleware but that would require filtering the request on a per page > basis which would be ugly. Any thoughts or suggestions how to do this, I > think I must have just missed something. I think what you're looking for is a custom template tag[3], more specifically an inclusion tag, which work very much like the way you describe above. These can be written from scratch, or simplified by using the built-in helpers[4] (even I managed to pull off a few, and I'm a lousy programmer... :-)). These tags can easily be set up to take the current page context as an argument and spit back differently rendered templates based on that. > Thanks, > Mat Good luck, hope you find this helpful! Cheers, //emil [1] http://www.djangoproject.com/documentation/templates/#debug [2] http://www.djangosnippets.org/tags/debug/, http://www.djangosnippets.org/snippets/93/ [3] http://www.djangoproject.com/documentation/templates_python/#writing-custom-template-tags [4] http://www.djangoproject.com/documentation/templates_python/#inclusion-tags --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
