mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 07:11:55 +00:00
Making page much more easily editable by using <dl><dt> and <dd> tags
This commit is contained in:
parent
5d207e675c
commit
effadc446a
16
TODO
16
TODO
@ -1,14 +1,2 @@
|
|||||||
Add missing images to logbooks from
|
everything here moved to handbook/computing/x-todo.html
|
||||||
2000, 2008, 2009, 2011
|
Philip Sargent 2020/03/28
|
||||||
fix corrupted image in 2001 log
|
|
||||||
|
|
||||||
2011 logbook:
|
|
||||||
type up via-ferrate & bolt-testing writeups (In paper book, not in scan or HTML)
|
|
||||||
|
|
||||||
200 logbook:
|
|
||||||
Type up "list of GPS locations still to type"
|
|
||||||
|
|
||||||
2019
|
|
||||||
transcribe the rest of those blog entries into expoweb/years/2019/logbook.html
|
|
||||||
copy the photos from the UKCaving blog into expofiles/photos/2019/<MyName>/ -- in fact many of those photos are already there
|
|
||||||
edit in the links to those photos in the right place in 2019/logbook.html
|
|
@ -55,30 +55,36 @@ h2, h3, h4 {
|
|||||||
margin-bottom: 0;
|
margin-bottom: 0;
|
||||||
}
|
}
|
||||||
|
|
||||||
ul:not(#links) li ul, ul:not(#links) ul {
|
dd {
|
||||||
font: 18px Calibri, sanserif;
|
font: 18px Calibri, sanserif;
|
||||||
font-weight: normal;
|
font-weight: normal;
|
||||||
list-style-type: disc;
|
color: 6083BF;
|
||||||
|
#list-style-type: disc;
|
||||||
line-height: 1.3;
|
line-height: 1.3;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
dd:before {
|
||||||
|
content: "- ";
|
||||||
|
}
|
||||||
|
|
||||||
/* Default State */
|
/* Default State */
|
||||||
ul:not(#links) {
|
dt {
|
||||||
font: 20px Calibri, sanserif;
|
font: 20px Calibri, sanserif;
|
||||||
font-weight: bold;
|
font-weight: bold;
|
||||||
color: 6083BF;
|
color: 6083BF;
|
||||||
margin-top: 0.4em;
|
margin-top: 0.4em;
|
||||||
margin-left: -1.2em;
|
#margin-left: -1.2em;
|
||||||
|
margin-left: 0;
|
||||||
margin-right: 5em;
|
margin-right: 5em;
|
||||||
list-style-type: none;
|
#list-style-type: none;
|
||||||
line-height: 1.4;
|
line-height: 1.4;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
/* Toggled State */
|
/* Toggled State */
|
||||||
input[type=checkbox] ~ ul:not(#links) li ul {
|
input[type=checkbox] ~ dl dd {
|
||||||
display: none;
|
display: none;
|
||||||
}
|
}
|
||||||
input[type=checkbox]:checked ~ ul:not(#links) li ul {
|
input[type=checkbox]:checked ~ dl dd {
|
||||||
display: block;
|
display: block;
|
||||||
}
|
}
|
||||||
|
@ -1,3 +1,4 @@
|
|||||||
|
<!DOCTYPE html>
|
||||||
<html>
|
<html>
|
||||||
<head>
|
<head>
|
||||||
<title>Expo Systems Exptl. To-Do List</title>
|
<title>Expo Systems Exptl. To-Do List</title>
|
||||||
@ -5,76 +6,144 @@
|
|||||||
</head>
|
</head>
|
||||||
<body>
|
<body>
|
||||||
<h1>Expo Systems Exptl. To-Do List</h1>
|
<h1>Expo Systems Exptl. To-Do List</h1>
|
||||||
<p><button onclick="window.location.href = 'x-todo.html_edit';">Update this to-do list</button> <label for="toggle-1">Toggle sub-items</label> <input id="toggle-1" type="checkbox" /></p>
|
<link rel="stylesheet" type="text/css" href="x-todo-styles.css" />
|
||||||
|
<button onclick="window.location.href = 'x-todo.html_edit';">Update this to-do list</button>
|
||||||
|
|
||||||
|
<label for="toggle-1">Toggle sub-items</label>
|
||||||
|
<input type="checkbox" id="toggle-1">
|
||||||
|
|
||||||
|
<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>Documentation</h2>
|
<h2>Documentation</h2>
|
||||||
<ul>
|
<dl>
|
||||||
<li>Wallets & new-cave
|
<dt><!--2020-03-26 psargent-->Wallets and new-cave</dt>
|
||||||
<ul>
|
|
||||||
<li>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>
|
<dd><!--2020-03-26 psargent-->Explain (in the wallets process) how to view the surveys
|
||||||
<li>Explain how to link a new cave into the other caves in troggle filesystem</li>
|
online so that <br> (1) you can see an example of how to do your new one,
|
||||||
</ul>
|
and <br> (2) so that you can check that you have done it properly when you
|
||||||
</li>
|
have finished.</dd>
|
||||||
<li>Troggle architecture
|
<dd><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
|
||||||
<ul>
|
troggle filesystem</dd>
|
||||||
<li>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>
|
|
||||||
</ul>
|
<dt><!--2020-03-26 psargent-->Troggle architecture</dt>
|
||||||
</li>
|
|
||||||
<li>Surveyscans
|
<dd><!--2020-03-26 psargent-->Handbook: explain how troggle works - much better and simpler. Fix
|
||||||
<ul>
|
mistakes I wrote. For future system maintainers</dd>
|
||||||
<li>explain where the image files are referenced from: svx, tunnel/therion, and why there are so many broken links</li>
|
<dd><!--2020-03-26 psargent-->Copy the .wiki material into the documentation somewhere</dd>
|
||||||
</ul>
|
|
||||||
</li>
|
|
||||||
</ul>
|
<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>
|
<h2>Photos</h2>
|
||||||
<ul>
|
<dl>
|
||||||
<li>Capitalisation in filenames problem
|
<dt><!--2020-03-26 psargent-->Capitalisation in filenames problem
|
||||||
<ul>
|
|
||||||
<li>run the duplicate filename script on the server in /photos/xml/ as there are files which differ only in capitalisation of their names.</li>
|
<dd><!--2020-03-26 psargent-->run the duplicate filename script on the server in
|
||||||
<li>Fix such duplicates in the /photos/ folders where this problem originates</li>
|
/photos/xml/ as there are files which differ only in
|
||||||
<li>Document this issue of duplicate photo filenames produced by multiple cameras running similar software</li>
|
capitalisation of their names.</dd>
|
||||||
<li>somehow fix the photo filenames which use capital letters on import or upload, or by a cron job</li>
|
<dd><!--2020-03-26 psargent-->Fix such duplicates in the /photos/ folders where this
|
||||||
</ul>
|
problem originates</dd>
|
||||||
</li>
|
<dd><!--2020-03-26 psargent-->Document this issue of duplicate photo filenames produced by
|
||||||
</ul>
|
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>
|
<h2>Surveys data entry</h2>
|
||||||
<ul>
|
<dl>
|
||||||
<li>2019 surveyscans
|
<dt><!--2020-03-26 psargent-->2019 surveyscans
|
||||||
<ul>
|
|
||||||
<li>edit all the content.json</li>
|
<dd><!--2020-03-26 psargent-->edit all the content.json</dd>
|
||||||
<li>try to autocomplete the content.json by parsing .svx files</li>
|
<dd><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files</dd>
|
||||||
<li>Put personal names into canonical form</li>
|
<dd><!--2020-03-26 psargent-->Put personal names into canonical form</dd>
|
||||||
</ul>
|
|
||||||
</li>
|
|
||||||
</ul>
|
</dl>
|
||||||
<h2>Troggle</h2>
|
<h2>Troggle</h2>
|
||||||
<h2>Expo Server</h2>
|
<h2>Expo Server</h2>
|
||||||
<ul>
|
<dl>
|
||||||
<li>www-data:www-data permissions
|
<dt><!--2020-03-26 psargent--> www-data:www-data permissions
|
||||||
<ul>
|
|
||||||
<li>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>
|
<dd><!--2020-03-26 psargent-->Fix permissions so that all files served by troggle have
|
||||||
<li>Or fix group membership for the process running django so that it can write files owned by 'expo'</li>
|
www-data:www-data ownership and group ownership, otherwise the
|
||||||
</ul>
|
"Edit this page" fails with a permissions error, or
|
||||||
</li>
|
</dd>
|
||||||
</ul>
|
<dd><!--2020-03-26 psargent-->Or fix group
|
||||||
<h2><span style="color: darkviolet;">This to-do-list gadget itself</span></h2>
|
membership for the process running django so that it can write
|
||||||
<ul>
|
files owned by 'expo'
|
||||||
<li>Eventual aim
|
</dd>
|
||||||
<ul>
|
|
||||||
<li>to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues"> CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</li>
|
</dd>
|
||||||
<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 <br />2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit)</li>
|
</dl>
|
||||||
</ul>
|
<h2>
|
||||||
</li>
|
<font color="darkviolet">This to-do-list gadget itself</font>
|
||||||
<li>Try to automate simple functions in javascript</li>
|
</h2>
|
||||||
<ul>
|
<dl>
|
||||||
<li>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>
|
<dt><!--2020-03-26 psargent-->Eventual aim
|
||||||
<li>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>
|
<dd><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
|
||||||
<li>Use javascript to skip over the _edit page and submit changes direct to server when updating</li>
|
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</dd>
|
||||||
<li>checkboxes so that items can be ticked (which also does strike-through)</li>
|
<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
|
||||||
<li>bin icon to delete an item? Better to have an archive process.</li>
|
<br>2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit)
|
||||||
</ul>
|
|
||||||
<li>TEST</li>
|
</dd>
|
||||||
</ul>
|
|
||||||
|
<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>
|
||||||
|
<!--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. -->
|
||||||
|
|
||||||
<hr /></body>
|
<hr /></body>
|
||||||
</html>
|
</html>
|
||||||
|
Loading…
Reference in New Issue
Block a user