Hi,
The "webdesign" django.contrib add-on [1] currently implements only 1
templatetag, supposed to help web designers. I think Django could
benefit from built-in elements that could be useful to web developpers
too, out of the box.
Some disorganized ideas that lead me to write this message:
* When developping, I always include code in my base template to
display the list of queries executed during the request ('sql_queries'
populated by the Debug context processor [2]). I'd love to simply have
a middleware appending that list (as a table) automatically to my HTML
response during development phase.
* Profiling. I have never done any yet, for the reason I do not know
how to hook profiling in Django (Google might help I confess). Again,
would it be feasible to have profiling available from a Django-contrib
app? Well, maybe profiling is not that important for regular
development, I do not know.
* A recurrent question that comes to mind when developing complex
pages: what are the objects available to me in a template (and what
are their attributes)? Some PHP frameworks have simple methods to
display all the variables passed to their templates ('views' in their
true MVC terminology) [3]. At some point during my development
process, I'd love to have a simple templatetag exposing the list of
variables available in my template, and their attributes (in the way
of the debug page that is fired up when something goes wrong and which
provides valuable debug/traceback data).
* Knowing the time it takes to render a page requested (e.g 'Page
loaded in 0.053s'). I remember someone suggesting a middleware for
that on the mailing list. Probably not the best measurement, I agree.
What do you think?
Do you have repetitive template code blocks that you add at the start
of a project to help you during development phase? Would it be useful
(and in line with the framework's philosophy) to ship them with core
Django (as contrib) and advocate them in the documentation?
Note: I link my thought to the webdesign contrib app, but it could as
well be shipped (and documented) as a separate "webdev" contrib app.
[1]
http://docs.djangoproject.com/en/dev/ref/contrib/webdesign/#ref-contrib-webdesign
[2]
http://docs.djangoproject.com/en/dev/ref/templates/api/?#django-core-context-processors-debug
[3] http://book.cakephp.org/view/458/Basic-Debugging
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
