Index: templates/main.html |
diff --git a/templates/main.html b/templates/main.html |
index 276d3db38862319c533498634d7a884df0378e84..f639017b96250836ec3b458ed22d77e9a668881f 100644 |
--- a/templates/main.html |
+++ b/templates/main.html |
@@ -1,11 +1,26 @@ |
{% extends "base.html" %} |
+{% block extra_head %} |
+ <script src="js/main/main.js"></script> |
+{% endblock %} |
+ |
{% block content %} |
- <script type="text/javascript"> |
- window.onload=function() { |
- document.add_new_message.message.focus(); |
- } |
- </script> |
+ <!-- Keep in sync with status.py:Status.general_state() logic --> |
+ <div id="help" class="help" hidden> |
+ The message is scanned for partial matches (in the order listed)<br> |
szager1
2013/12/05 20:47:48
"partial matches" sounds weird. How about "keywor
vapier
2013/12/05 21:02:45
"keywords" to me indicates word boundaries, and th
|
+ and will set the tree state accordingly. The scan order does <b>not</b><br> |
+ correspond to the severity of the tree state.<br> |
+ <br> |
+ (1) "<span class="maintenance">maint</span>": The tree is closed for |
+ maintenance<br> |
+ (also needs to have the text |
+ "close")<br> |
+ (2) "<span class="throttled">throt</span>": The tree is throttled; |
+ tread carefully<br> |
+ (3) "<span class="closed">close</span>": The tree is closed<br> |
+ (4) Otherwise, the tree is <span class="open">open</span> for business |
+ </div> |
+ |
<center> |
{% if write_access %} |
{% if error_message %} |
@@ -14,7 +29,8 @@ |
</div> |
{% endif %} |
<form action="/" name="add_new_message" method="post"> |
- <input type="text" size="80" name="message" value="{{ message }}"> |
+ <textarea cols="80" rows="2" name="message" |
+ style="vertical-align: middle;">{{ message }}</textarea> |
<input type="hidden" name="last_status_key" value="{{ last_status_key }}"> |
<input type="submit" name="change" value="Change"> |
<input type="button" name="refresh" value="Refresh" onclick="location.href='/';"> |