2020-03-28 22:06:47 +00:00
<!DOCTYPE html>
2020-03-26 20:50:08 +00:00
< html >
< head >
2020-04-03 21:55:58 +01:00
< title > Expo Systems - Experimental To-Do List< / title >
2020-03-26 20:50:08 +00:00
< meta charset = "utf-8" >
< / head >
2020-03-28 17:55:47 +00:00
< body >
2020-04-03 21:55:58 +01:00
< h1 > Experimental expo To-Do List< / h1 >
2020-03-29 03:54:18 +01:00
< 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 >
-->
<!--
2020-03-29 03:32:27 +01:00
< label for = "toggle-1" > Toggle visibility of all sub-items< / label >
2020-03-28 22:06:47 +00:00
< input type = "checkbox" id = "toggle-1" >
2020-03-29 03:32:27 +01:00
-->
2020-03-29 03:54:18 +01:00
< h2 > Experimental< / h2 >
2020-04-03 21:55:58 +01:00
2020-03-29 03:54:18 +01:00
< 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.
2020-04-03 21:55:58 +01:00
< p > Printing this page uses a much smaller font. Complain to a nerd if you don't like this behaviour.
< p > < span style = "text-decoration: line-through;" > Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before.< / span > < em > But that is not working yet. Please do not try as that will currently delete all the Javascript that makes the hide/reveal functions work.< / em >
< p > Edit this page using the pull/edit/commit/push version control mechanism.
< h3 > Taken from file on ::expoweb::/TODO < / h3 >
< dl > <!-- 2020 - 03 - 29 psargent -->
< 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 >
2020-03-29 03:54:18 +01:00
< / dl >
2020-04-03 21:55:58 +01:00
< h3 > Documentation< / h3 >
2020-03-29 03:54:18 +01:00
< dl >
< dt > <!-- 2020 - 03 - 29 psargent --> Document this to-do list thing< / dt >
2020-04-03 21:55:58 +01:00
< dd > <!-- 2020 - 03 - 29 psargent --> explain how clicking works< / dd >
2020-03-29 03:54:18 +01:00
< dt > <!-- 2020 - 03 - 26 psargent --> Wallets and new-cave< / dt >
2020-04-03 21:55:58 +01:00
< dd > <!-- 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.< / dd >
< dd > <!-- 2020 - 03 - 26 psargent --> Explain how to link a new cave into the other caves in
troggle filesystem< / dd >
< dd > <!-- 2020 - 03 - 26 psargent --> Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves< / dd >
2020-03-29 03:54:18 +01:00
< dt > <!-- 2020 - 03 - 26 psargent --> Troggle architecture< / dt >
2020-04-03 21:55:58 +01:00
< dd > <!-- 2020 - 03 - 26 psargent --> Handbook: complete the new troggle architecture documentaiton. For future system maintainers< / dd >
< dd > <!-- 2020 - 03 - 26 psargent --> Copy the .wiki material into the documentation somewhere< / dd >
2020-03-29 03:54:18 +01:00
< dt > <!-- 2020 - 03 - 26 psargent --> Surveyscans< / dt >
2020-04-03 21:55:58 +01:00
< 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 >
< dt > Apache & MySQL configuration
< dd > <!-- 2020 - 04 - 03 psargent --> DOCUMENT How to set up a server
< dt > non-troggle scripts
< dd > <!-- 2020 - 04 - 03 psargent --> DOCUMENT them all - have we got < a href = "../troggle/otherscripts.html" > a full list< / a > ?
2020-03-29 03:54:18 +01:00
< / dl >
2020-04-03 21:55:58 +01:00
< h3 > Photos< / h3 >
2020-03-29 03:54:18 +01:00
< dl >
2020-04-03 21:55:58 +01:00
< dt > <!-- 2020 - 04 - 03 psargent --> Fix the BINS package
< dd > <!-- 2020 - 04 - 03 psargent --> set up git on the BINS software< / dd >
< dd > <!-- 2020 - 04 - 03 psargent --> set up a cron job to run BINS< / dd >
2020-03-29 03:54:18 +01:00
< / dl >
2020-04-03 21:55:58 +01:00
< h3 > Surveys data entry< / h3 >
< dl >
< dt > Write code to extract info about wallets form svx files
< dd > <!-- 2020 - 04 - 03 psargent --> use to VALIDATE exitsing contents.json files - produce DISCREPANCY report & fix
2020-03-29 03:54:18 +01:00
< 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 >
2020-04-03 21:55:58 +01:00
< dt > 2014 contents.json
< dd > <!-- 2020 - 04 - 03 psargent --> parse all the svx files to extract people, dates & svx references
2020-03-29 03:54:18 +01:00
< / dl >
2020-04-03 21:55:58 +01:00
< h3 > Troggle< / h3 >
< dl >
< dt > Better import error messages
< dd > <!-- 2020 - 04 - 03 psargent --> REPORT if import surveyscan file failure
< dd > <!-- 2020 - 04 - 03 psargent --> Why are so many surveyscan foolder missing after import?
< dd > <!-- 2020 - 04 - 03 psargent --> WHY are total lengths of surveyed cave different between expo server and WSL server for 2019 and a few other years only ?
< / dl >
< h3 > Logbooks< / h3 >
< dl >
< dt > 2019 - blog photos
< dd > <!-- 2020 - 04 - 03 psargent --> copy & plumb-in the blog photos for the already-copied blog text
< dt > Past logbooks - missing images?
< dd > <!-- 2020 - 04 - 03 psargent --> Which previous years HTML logbooks are missing images extracted from scanned PDF copies of the logbooks?
< dt > data model: unfilled fields?
< dd > <!-- 2020 - 04 - 03 psargent --> 'cave' of location field missing on nearly all logbook entroies. Missing from logbook templates. Where is this used and how can we fill it it in? Is it useful?
< dt > imagemagick convert
< dd > <!-- 2020 - 04 - 03 psargent --> Not working for PDFs on current version of xubuntu ! Fix & document. Also not working on WSL ubuntu.
< / dl >
< h3 > Expo Server< / h3 >
2020-03-29 03:54:18 +01:00
< dl >
2020-04-03 21:55:58 +01:00
< dt > <!-- 2020 - 03 - 26 psargent --> document directory structure
< dd > <!-- 2020 - 04 - 03 psargent --> as per Julian's GitHub list - then close that issue< / dd >
< dt > permissions
< dd > <!-- 2020 - 04 - 03 psargent --> do we need a cron job or has the group membership fix fixed it ? either way, document it.
< / dd >
2020-03-29 03:54:18 +01:00
< / dl >
2020-04-03 21:55:58 +01:00
< h3 >
< font color = "fuchsia" > This to-do-list gadget itself< / font >
< / h3 >
2020-03-29 03:54:18 +01:00
< dl >
2020-04-03 21:55:58 +01:00
< dt > <!-- 2020 - 03 - 26 psargent --> Eventual aim
2020-03-29 03:54:18 +01:00
2020-04-03 21:55:58 +01:00
< 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)
2020-03-29 03:54:18 +01:00
2020-04-03 21:55:58 +01:00
< / dd >
2020-03-29 03:54:18 +01:00
2020-04-03 21:55:58 +01:00
< dt > <!-- 2020 - 03 - 26 psargent --> Try to automate simple functions in javascript
2020-03-29 03:54:18 +01:00
2020-04-03 21:55:58 +01:00
< 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. < / dd >
< dd > <!-- 2020 - 03 - 26 psargent --> if using tinymcs, use the INLINE mode. < / 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. Needs direct POST and include the javascript in the posted content.< / dd >
< dd > <!-- 2020 - 03 - 26 psargent --> checkboxes so that items can be ticked (which also does strike-through)< / dd >
< dd > <!-- 2020 - 04 - 03 psargent --> promotion/demotion options?< / dd >
< dd > <!-- 2020 - 03 - 26 psargent --> bin icon to delete an item? Better to have an archive process.< / dd >
< dt > Local WSL server
< dd > <!-- 2020 - 04 - 03 psargent --> Why is it using recuced-capability tinymce, a paths problem ?
< dt > Italics management
< dd > <!-- 2020 - 04 - 03 psargent --> Hide ALL DD if any Heading clicked.
< dd > <!-- 2020 - 04 - 03 psargent --> Put DL into italics when *any* DD is hidden
< / dl >
< h3 > < font color = "fuchsia" > Tackle Store Records< / font > < / h3 >
< dl >
< dt > No authoritative list of where the expo paper records are!
< dd > <!-- 2020 - 04 - 03 psargent --> FIND where all the wallet binders are, and the logbooks.
< < dd > <!-- 2020 - 04 - 03 psargent --> Buy A4 plastic boxes for filing cabinet for logbooks getting damp there.
2020-03-29 03:54:18 +01:00
< / dl >
< hr >
<!-- - - - - - - - - - - - - - - - - - - - Do not touch anything below here - - - - - - - - - - - - - - - - - - - - - - -->
<!-- 2020 - 03 - 26 --> Testing area..
< div id = "demo" > Demonstation as initially read from disc< / div >
< script >
2020-03-28 22:06:47 +00:00
document.getElementById("demo").innerHTML = "Demonstation innerHTML change CONFIRMED";
2020-03-29 03:54:18 +01:00
< / script >
2020-03-28 22:06:47 +00:00
<!-- 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. -->
2020-03-29 03:54:18 +01:00
< script >
// TO DO - make the < dt > italic when any of the < dd > following it are hidden.
2020-03-29 03:32:27 +01:00
var itemlist = document.getElementsByTagName('dd');
for (i = 0; i < itemlist.length ; i + + ) {
itemlist[i].onclick = hideable;
}
var itemlist = document.getElementsByTagName('dt');
for (i = 0; i < itemlist.length ; i + + ) {
itemlist[i].onclick = showable;
}
function showable () {
// When clicking on a < dt > item, show or not all the following < dd > elements
if (this.style.fontStyle !== "italic") {
this.style.fontStyle = "italic";
} else {
this.style.fontStyle = "normal";
}
var ddO = this.nextElementSibling;
while((ddO !== null) & & (ddO.nodeName.toLowerCase() == 'dd')){
if (this.style.fontStyle === "italic") {
ddO.style.display = 'none';
} else {
ddO.style.display = 'block';
}
ddO = ddO.nextElementSibling;
}
}
function hideable () {
var x = this;
if (x.style.display === "none") {
x.style.display = "block";
} else {
x.style.display = "none";
}
}
2020-03-29 03:54:18 +01:00
< / script >
2020-03-28 17:55:47 +00:00
< hr / > < / body >
2020-03-26 20:50:08 +00:00
< / html >
