expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-25 08:41:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

prettier to-do list

Browse Source
This commit is contained in:
expo on server 2020-03-29 03:50:39 +01:00
parent 314af7c4c9
commit fb3a4740f1
1 changed files with 22 additions and 149 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

171
handbook/computing/x-todo.html
View File

@ -5,164 +5,37 @@
<meta charset="utf-8">
</head>
<body>
<h1>Expo Systems Exptl. To-Do List</h1>
<link rel="stylesheet" type="text/css" href="x-todo-styles.css" />
<button onclick="window.location.href = 'x-todo.html';">Update this to-do list</button>
<!--
<button onclick="window.location.href = 'x-todo.html_edit';">Update this to-do list</button>
-->
<!--
<h1>Expo Systems Exptl. To-Do List</h1>
<p><button onclick="window.location.href = 'x-todo.html_edit';">Update this to-do list</button></p>
<!--
<label for="toggle-1">Toggle visibility of all sub-items</label>
<input type="checkbox" id="toggle-1">
-->
<h2>Experimental</h2>
<p>Click on a sub-heading to hide and reveal the individual to-do items. If a heading is in italics, then there are hidden items.
<p>Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before. But this is not working yet. Please do not try as that will currently delete all the Javascript that makes the hide/reveal functions work.
<h2>Taken from file on ::expoweb::/TODO </h2>
<dl>
<dt>Add missing images to logbooks</dt>
<dd>
2000, 2008, 2009, 2011</dd>
<dd>
fix corrupted image in 2001 log</dd>
<dt>2011 logbook:</dt>
<dd>type up via-ferrate & bolt-testing writeups (In paper book, not in scan or HTML)</dd>
<dt>200? logbook:</dt>
<dd>
Type up "list of GPS locations still to type"</dd>
<dt>2019 Logbook</dt>
<dd>
transcribe the rest of those blog entries into expoweb/years/2019/logbook.html</dd>
<dd>
copy the photos from the UKCaving blog into expofiles/photos/2019/<MyName>/ -- in fact many of those photos are already there</dd>
<dd>edit in the links to those photos in the right place in 2019/logbook.html</dd>
</dl>
<h2>Experimental</h2>
<p>Click on a sub-heading to hide and reveal the individual to-do items. If a heading is in italics, then there are hidden items.</p>
<p>Edit this page by clciking on the big blue button. It uses the same "Edit this page" function that you may have used before.</p>
<h2>Taken from file on ::expoweb::/TODO</h2>
<dl><dt>Add missing images to logbooks</dt><dd>2000, 2008, 2009, 2011</dd><dd>fix corrupted image in 2001 log</dd><dt>2011 logbook:</dt><dd>type up via-ferrate &amp; bolt-testing writeups (In paper book, not in scan or HTML)</dd><dt>200? logbook:</dt><dd>Type up "list of GPS locations still to type" - is this 2012??</dd><dt>2019 Logbook</dt><dd>transcribe the rest of those blog entries into expoweb/years/2019/logbook.html</dd><dd>copy the photos from the UKCaving blog into expofiles/photos/2019// -- in fact many of those photos are already there</dd><dd>edit in the links to those photos in the right place in 2019/logbook.html</dd></dl>
<h2>Documentation</h2>
<dl>
<dt><!--2020-03-29 psargent-->Document this to-do list thing</dt>
<dd><!--2020-03-29 psargent-->explain how clicking works</dd>
<dt><!--2020-03-26 psargent-->Wallets and new-cave</dt>
<dd><!--2020-03-26 psargent-->Explain (in the wallets process) how to view the surveys
online so that <br>&nbsp;&nbsp;(1) you can see an example of how to do your new one,
and <br>&nbsp;&nbsp;(2) so that you can check that you have done it properly when you
have finished.</dd>
<dd><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
troggle filesystem</dd>
<dt><!--2020-03-26 psargent-->Troggle architecture</dt>
<dd><!--2020-03-26 psargent-->Handbook: explain how troggle works - much better and simpler. Fix
mistakes I wrote. For future system maintainers</dd>
<dd><!--2020-03-26 psargent-->Copy the .wiki material into the documentation somewhere</dd>
<dt><!--2020-03-26 psargent-->Surveyscans</dt>
<dd><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and </dd>
<dd>why there are so many broken links</dd>
</dl>
<dl><dt><!--2020-03-29 psargent-->Document this to-do list thing</dt><dd><!--2020-03-29 psargent-->explain how clicking works</dd><dt><!--2020-03-26 psargent-->Wallets and new-cave</dt><dd><!--2020-03-26 psargent-->Explain (in the wallets process) how to view the surveys online so that <br />&nbsp;&nbsp;(1) you can see an example of how to do your new one, and <br />&nbsp;&nbsp;(2) so that you can check that you have done it properly when you have finished.</dd><dd><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in troggle filesystem</dd><dt><!--2020-03-26 psargent-->Troggle architecture</dt><dd><!--2020-03-26 psargent-->Handbook: explain how troggle works - much better and simpler. Fix mistakes I wrote. For future system maintainers</dd><dd><!--2020-03-26 psargent-->Copy the .wiki material into the documentation somewhere</dd><dt><!--2020-03-26 psargent-->Surveyscans</dt><dd><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and</dd><dd>why there are so many broken links</dd></dl>
<h2>Photos</h2>
<dl>
<dt><!--2020-03-26 psargent-->Capitalisation in filenames problem
<dd><!--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.</dd>
<dd><!--2020-03-26 psargent-->Fix such duplicates in the /photos/ folders where this
problem originates</dd>
<dd><!--2020-03-26 psargent-->Document this issue of duplicate photo filenames produced by
multiple cameras running similar software</dd>
<dd><!--2020-03-26 psargent-->somehow fix the photo filenames which use capital letters on
import or upload, or by a cron job</dd>
</dl>
<dl><dt><!--2020-03-26 psargent-->Capitalisation in filenames problem</dt><dd><!--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.</dd><dd><!--2020-03-26 psargent-->Fix such duplicates in the /photos/ folders where this problem originates</dd><dd><!--2020-03-26 psargent-->Document this issue of duplicate photo filenames produced by multiple cameras running similar software</dd><dd><!--2020-03-26 psargent-->somehow fix the photo filenames which use capital letters on import or upload, or by a cron job</dd></dl>
<h2>Surveys data entry</h2>
<dl>
<dt><!--2020-03-26 psargent-->2019 surveyscans
<dd><!--2020-03-26 psargent-->edit all the content.json</dd>
<dd><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files</dd>
<dd><!--2020-03-26 psargent-->Put personal names into canonical form</dd>
</dl>
<dl><dt><!--2020-03-26 psargent-->2019 surveyscans</dt><dd><!--2020-03-26 psargent-->edit all the content.json</dd><dd><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files</dd><dd><!--2020-03-26 psargent-->Put personal names into canonical form</dd></dl>
<h2>Troggle</h2>
<h2>Expo Server</h2>
<dl>
<dt><!--2020-03-26 psargent--> www-data:www-data permissions
<dd><!--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
</dd>
<dd><!--2020-03-26 psargent-->Or fix group
membership for the process running django so that it can write
files owned by 'expo'
</dd>
</dd>
</dl>
<h2>
<font color="darkviolet">This to-do-list gadget itself</font>
</h2>
<dl>
<dt><!--2020-03-26 psargent-->Eventual aim
<dd><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</dd>
<dd><!--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)
</dd>
<dt><!--2020-03-26 psargent-->Try to automate simple functions in javascript
<dd><!--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</dd>
<dd><!--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 ?</dd>
<dd><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki</dd>
<dd><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes
direct to server when updating</dd>
<dd><!--2020-03-26 psargent-->checkboxes so that items can be ticked
(which also does strike-through)</dd>
<dd><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.</dd><!--2020-03-26-->
</dl>
<hr>
<!-- ------------------- Do not touch anything below here ------------------------>
<!--2020-03-26--> Testing area..
<div id="demo">Demonstation as initially read from disc</div>
<script>
<dl><dt><!--2020-03-26 psargent--> www-data:www-data permissions</dt><dd><!--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</dd><dd><!--2020-03-26 psargent-->Or fix group membership for the process running django so that it can write files owned by 'expo'</dd></dl>
<h2><span style="color: darkviolet;">This to-do-list gadget itself</span></h2>
<dl><dt><!--2020-03-26 psargent-->Eventual aim</dt><dd><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues"> CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</dd><dd><!--2020-03-26 psargent-->We need two of these: <br />1.for expo systems work (troggle &amp; 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)</dd><dt><!--2020-03-26 psargent-->Try to automate simple functions in javascript</dt><dd><!--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</dd><dd><!--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 ?</dd><dd><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki</dd><dd><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes direct to server when updating</dd><dd><!--2020-03-26 psargent-->checkboxes so that items can be ticked (which also does strike-through)</dd><dd><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.</dd><dt><!--2020-03-26--></dt></dl><hr />
<p><!-- ------------------- Do not touch anything below here ------------------------> <!--2020-03-26--> Testing area..</p>
<div id="demo">Demonstation as initially read from disc</div>
<p>
<script type="mce-text/javascript">// <![CDATA[
document.getElementById("demo").innerHTML = "Demonstation innerHTML change CONFIRMED";
</script>
// ]]></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. -->
<script>
// TO DO - make the <dt> italic when any of the <dd> following it are hidden.
<script type="mce-text/javascript">// <![CDATA[
var itemlist = document.getElementsByTagName('dd');
for (i = 0; i < itemlist.length; i++) {
itemlist[i].onclick = hideable;
@ -200,7 +73,7 @@ function hideable () {
x.style.display = "none";
}
}
</script>
// ]]></script>
</p>
<hr /></body>
</html>