Context Navigation

Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Version 5 and Version 6 of Ticket #7274, comment 1

Timestamp:: 05/28/12 11:41:31 (12 years ago)
Author:: atarkowska
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #7274, comment 1

-                      v5
+                      v6
 {{{
+{% static "3rdparty/jquery-1.7.2.js" %}
+<script type="text/javascript" src="{% static "3rdparty/jquery-1.7.2.js" %}"></script>
 }}}
 …
 '''WARNING''': In every inherited template any code outside blocks redefinitions is not executed. So in this case {% load webclient_tags %} has to be called inside each block.
 or use context processor for setting "global" variable.
+or use context processor for setting "global" variable.
+[[BR]]
+[[BR]]
+== Using STATICS in views methods: ==
+{{{
+from django.conf import settings
+'<script type="text/javascript" src="%s3rdparty/jquery-1.7.2.js"></script>' % settings.STATIC_URL
+}}}
 [[BR]]
 …
 The static files tools are mostly designed to help with getting static files successfully deployed into production. This usually means a separate, dedicated static file server, which is a lot of overhead to mess with when developing locally. Thus, the staticfiles app ships with a quick and dirty helper view that you can use to serve files locally in development. This will only work if DEBUG is True.
 {{{
 $ bin/omero config set omero.web.debug True
 }}}
 That's because this view is grossly inefficient and probably insecure. '''This is only intended for local development, and should never be used in production'''.
 …
 == Config changes: ==
+. STATICFILES_DIRS should be configurable from omero config command line by
+. STATICFILES_DIRS should be configurable from omero config command line by
 {{{
 $ bin/omero config set omero.web.staticfile_dirs '[["alias", "/home/example.com/static/"], ["/opt/webfiles/common"]'