From 397c1a66264eac93cba516c5589da342e3b13962 Mon Sep 17 00:00:00 2001
From: "Philip Sargent  (muscogee)" <philip.sargent@gmail.com>
Date: Thu, 26 Mar 2020 23:20:16 +0000
Subject: [PATCH] added datestamps. But this whole approach fails as TinyMCE
 sunmisison trashes everthing not int he TEXTAREA

---
 handbook/computing/x-todo.html | 68 ++++++++++++++++++----------------
 1 file changed, 37 insertions(+), 31 deletions(-)

diff --git a/handbook/computing/x-todo.html b/handbook/computing/x-todo.html
index df2ed6c4b..35150050e 100644
--- a/handbook/computing/x-todo.html
+++ b/handbook/computing/x-todo.html
@@ -11,65 +11,65 @@
     <input type="checkbox" id="toggle-1">
 <h2>Documentation</h2>
 <ul>
-    <li>Wallets & new-cave
+    <li><!--2020-03-26 psargent-->Wallets & new-cave
         <ul>
-            <li>Explain (in the wallets process) how to view the surveys
+            <li><!--2020-03-26 psargent-->Explain (in the wallets process) how to view the surveys
                 online so that <br>(1) you can see an example of how to do your new one,
                 and <br>(2) so that you can check that you have done it properly when you
                 have finished.</li>
-            <li>Explain how to link a new cave into the other caves in
+            <li><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
                 troggle filesystem</li>
         </ul>
     </li>
-    <li>Troggle architecture
+    <li><!--2020-03-26 psargent-->Troggle architecture
         <ul>
-            <li>Handbook: explain how troggle works - much better and simpler. Fix
+            <li><!--2020-03-26 psargent-->Handbook: explain how troggle works - much better and simpler. Fix
                 mistakes I wrote. For future system maintainers</li>
-            <li>Copy the .wiki material into the documentation somewhere</li>
+            <li><!--2020-03-26 psargent-->Copy the .wiki material into the documentation somewhere</li>
         </ul>
     </li>
-    <li>Surveyscans
+    <li><!--2020-03-26 psargent-->Surveyscans
         <ul>
-            <li>explain where the image files are referenced from: svx, tunnel/therion, and why there are so many broken links</li>
+            <li><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and why there are so many broken links</li>
         </ul>
     </li>
 </ul>
 <h2>Photos</h2>
 <ul>
-    <li>Capitalisation in filenames problem
+    <li><!--2020-03-26 psargent-->Capitalisation in filenames problem
         <ul>
-            <li>run the duplicate filename script on the server in
+            <li><!--2020-03-26 psargent-->run the duplicate filename script on the server in
                 /photos/xml/ as there are files which differ only in
                 capitalisation of their names.</li>
-            <li>Fix such duplicates in the /photos/ folders where this
+            <li><!--2020-03-26 psargent-->Fix such duplicates in the /photos/ folders where this
                 problem originates</li>
-            <li>Document this issue of duplicate photo filenames produced by
+            <li><!--2020-03-26 psargent-->Document this issue of duplicate photo filenames produced by
         multiple cameras running similar software</li>
-            <li>somehow fix the photo filenames which use capital letters on
+            <li><!--2020-03-26 psargent-->somehow fix the photo filenames which use capital letters on
         import or upload, or by a cron job</li>
         </ul>
     </li>
 </ul>
 <h2>Surveys data entry</h2>
 <ul>
-    <li>2019 surveyscans
+    <li><!--2020-03-26 psargent-->2019 surveyscans
         <ul>
-            <li>edit all the content.json</li>
-            <li>try to autocomplete the content.json by parsing .svx files</li>
-            <li>Put personal names into canonical form</li>
+            <li><!--2020-03-26 psargent-->edit all the content.json</li>
+            <li><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files</li>
+            <li><!--2020-03-26 psargent-->Put personal names into canonical form</li>
         </ul>
     </li>
 </ul>
 <h2>Troggle</h2>
 <h2>Expo Server</h2>
 <ul>
-    <li> www-data:www-data permissions
+    <li><!--2020-03-26 psargent--> www-data:www-data permissions
         <ul>
-					<li>Fix permissions so that all files served by troggle have
+					<li><!--2020-03-26 psargent-->Fix permissions so that all files served by troggle have
         www-data:www-data ownership and group ownership, otherwise the
         "Edit this page" fails with a permissions error, or
 					</li>
-					<li>Or fix group
+					<li><!--2020-03-26 psargent-->Or fix group
         membership for the process running django so that it can write
         files owned by 'expo'
 					</li>
@@ -80,35 +80,41 @@
     <font color="darkviolet">This to-do-list gadget itself</font>
 </h2>
 <ul>
-     <li>Eventual aim
+     <li><!--2020-03-26 psargent-->Eventual aim
         <ul>
-					<li>to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
+					<li><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
 					CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</li>
-					<li>We need two of these: <br>1.for expo systems work (troggle & scripts) - the current priority as we have nowhere currently that Wookey is willing to use
+					<li><!--2020-03-26 psargent-->We need two of these: <br>1.for expo systems work (troggle & scripts) - the current priority as we have nowhere currently that Wookey is willing to use
 					<br>2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit) 
 					</ul>
 					</li>
    
-    <li>Try to automate simple functions in javascript
+    <li><!--2020-03-26 psargent-->Try to automate simple functions in javascript
         <ul>
-					<li>to control this document
+					<li><!--2020-03-26 psargent-->to control this document
 					in-place (tick, delete) instead of using the <a
 					href="https://www.tiny.cloud/docs/general-configuration-guide/use-tinymce-inline/">
 					tinymce</a> HTML editor in Django</li>
-					<li>Maybe restructure whole page as JSON and use
+					<li><!--2020-03-26 psargent-->Maybe restructure whole page as JSON and use
 					javascript editor to create (edit), re-order and demote items. So long
 					as the content is inserted into the DOM, it should work ?</li>
-					<li>Implement comments on an issue, mimicking GitHub issues wiki</li>
-					<li>Use javascript to skip over the _edit page and submit changes
+					<li><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki</li>
+					<li><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes
 					direct to server when updating</li>
-					<li>checkboxes so that items can be ticked
+					<li><!--2020-03-26 psargent-->checkboxes so that items can be ticked
 					(which also does strike-through)</li>
-					<li>bin icon to delete an item? Better to have an archive process.</li>
+					<li><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.</li><!--2020-03-26-->
         </ul>
     </li>
 
 </ul>
 <hr>
-
+<!--2020-03-26--> Testing area..
+<div id="demo">Demonstation as initially read from disc</div>
+<script>
+document.getElementById("demo").innerHTML = "Demonstation innerHTML change CONFIRMED";
+</script>
+<!--Bother. The DOM is not carried across to the _edit page. It looks like the _edit page just re-reads
+the original file from disc. So storing changes done by js will mean working directly with the POST action and a form. -->
 </body>
 </html>