to-do lists updates

handbook/computing/todo.html

@@ -43,8 +43,15 @@ li.todo:before {
 <h3>Module to-do texts</h3>
 <p>These are extracted directly from the <var>todo = &apos;&apos;&apos;Thing to do &apos;&apos;&apos;</var> string at the top of each file of troggle code:</p>
 <hr>
+
 <div>
-<a href="/todo/anything">Click here to see the programmers' to do within the code.</div></a> This list is generated directly from the troggle python code files.
+<figure>
+<a href="/todo/anything">
+<img  border="1" src="todo-snapshot.jpg" width=45%>
+<figcaption>Click here for live list.
+</figure></div></a> 
+This to-do list is generated directly from the troggle python code files and is the most up to date
+to-do list for programming you are likely to find anywhere. Every serious maintainer also maintains their own personal handwritten notes and/or Google Keep lists too.
 <hr>
 
 <h3>Other coding To Do things</h3>

handbook/logbooks.html

@@ -50,7 +50,7 @@ and then the
 <p>Writing up this and the final rigging guide is an important part of the Expo cave exploration process and is documented in <a href="survey/newrig.html">a specific "rigging" section</a>  the survey handbook.
 
 
-<h3>The online logbook file</h3>
+<h3 id="type">The online logbook file</h3>
 
 <p>If you are at basecamp, then it is an excellent idea to 
 <b>type the text of your logbook trip report</b> instead of writing it by hand - see <a href="#type">below</a>. But still do lots of drawings in the paper logbook.
@@ -139,10 +139,10 @@ idea to type up <i>just your trip(s)</i> in a separate file, e.g. "logbook-mynew
 &lt;div class="tripdate" id="t2007-07-12B"&gt;2007-07-12&lt;/div&gt;
 &lt;div class="trippeople"&gt;&lt;u&gt;Jenny Black&lt;/u&gt;, Olly Betts&lt;/div&gt;
 &lt;div class="triptitle"&gt;Top Camp - Setting up 76 bivi&lt;/div&gt;
-&lt;div class="timeug"&gt;T/U 10 mins&lt;/div&gt;</pre></code>
+&lt;div class="timeug"&gt;T/U 0.2 hrs&lt;/div&gt;</pre></code>
 <p>Note:  the ID's must be unique, so are generated from 't' plus the trip date plus a,b,c etc. 
 when there is more than one trip on a day.</p>
-<p>Note: <var><span style="color:red">T/U</span></var> stands for "Time Underground" in minutes and/or hours. (We do not parse or collate this information so the format and units don't matter.)
+<p>Note: <var><span style="color:red">T/U</span></var> stands for "Time Underground" in decimal hours, e.g. "0.2" for 12 minutes (approx.) . We do not parse or collate this information currently.
 <p>Note: the <var><span style="color:red">&lt;hr /&gt;</span></var> is significant and used in parsing, it is not just prettiness.
 <p>Note: follow this format exactly. No HTML comments or  tabs or newlines.
 
@@ -155,9 +155,17 @@ for this are "Plateau", "Base camp", "264", "Balkon", "Tunnocks", "Travel" etc.
 <code><pre>&lt;div class="trippeople"&gt;<span style="color:red">&lt;u&gt;Jenny Black&lt;/u&gt;</span>, Olly Betts&lt;/div&gt;
 </pre></code>
 It is necessary that one (and only one) of the people on the trip is set in <span style="color:red">&lt;u&gt;&lt;/u&gt;</span> underline format. This is interpreted to mean that this is the author of the logbook entry. If there is no author set, then this is an error and the entry is ignored.
+
+<p>If you like, you can put non-expo people in the trip-people line: <var>"<span style="color:red">*Ol's Mum</span>"</var> with a <span style="color:red">*</span> prefix and they will be totally ignored by troggle:
+<code><pre>&lt;div class="trippeople"&gt;&lt;u&gt;Jenny Black&lt;/u&gt;, Olly Betts, <span style="color:red">*Ol's Mum</span>&lt;/div&gt;
+</pre></code>
+or
+<code><pre>&lt;div class="trippeople"&gt;&lt;u&gt;Jenny Black&lt;/u&gt;, Olly Betts, <span style="color:red">*4 Hungarian Cavers</span>&lt;/div&gt;
+</pre></code>
+
+<hr />
+Go on to <a href="computing/logbooks-parsing.html">Importing logbooks into troggle</a>.
 <hr />
-
-
 </body>
 </html>