Add profiling support to Melange. By assigning profile_main_as_logs or profile_main_as_html to main variable you can turn on profiling. profile_main_as_logs will log profile data to App Engine console logs, profile_main_as_html will show profile data as html at the bottom of the page. If you want to profile app on deployed app just set the profiling function and deploy it.
Patch by: Pawel Solyga
Reviewed by: to-be-reviewed
TEMPLATE NAMESPACES
Templates are placed in a "namespace" subdirectory in the templates directory,
since the templates directory will be added to the Django templates search
path. This allows other packages to extend existing templates without "hiding"
the original template. For example, a template in another Melange application
can extend a template in the SoC framework like this:
{% extends 'soc/some_existing_template.html' %}
without "hiding" the some_existing_template.html for other uses, even if the
derived template is also named some_existing_template.html.
So, please do not put any templates in this soc/templates directory, but only
place them in the soc/templates/soc "namespace" subdirectory.
Different Melange applications should also follow this pattern, to promote
sharing of templates between applications as well. For exmample, the GSoC
Melange application should place its templates in gsoc/templates/gsoc.
MODEL/VIEW TEMPLATE NAMING
View templates are usually named some_view.html for a corresponding someView()
function and SomeViewForm form class. Since SomeView is likely to be a common
View name for multiple Models, Model-specific templates should be placed in
soc/<model>/<view> sub-directories.