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

updated to reflect wallets recent code improvements - online edit of handbook/troggle/trogdesign.html

Browse Source
This commit is contained in:
Expo on server 2022-08-03 14:53:38 +01:00
parent 2d4f61169e
commit b2eb38d577
1 changed files with 12 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
handbook/troggle/trogdesign.html
View File

@ -5,7 +5,8 @@
<title>Handbook Troggle Design</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<body>
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>What Troggle Does Badly - Design Decisions</h1>
<p>Practical use of troggle quickly shows up serious shortcomings:
@ -16,7 +17,7 @@
<li><h4><a href="#change">New Things Troggle will need to Manage</a></h4>
<li><h4><a href="#specific">Specific, Immediate problems</a></h4>
</ul>
<p><em>Updated: 11 March 2022</em>
<p><em>Updated: 3 August 2022</em>
<h2 id="fail">Things Troggle Doesn't Do</h2>
<p>Mostly these are not just a problem just with troggle, but things where expo procedures have never been
@ -55,19 +56,7 @@ the illutrating photographs - which were very good. We have these archived on ex
Element, which we can archive ourseleves, and maybe we can use Kanboard (ditto) next year instead of Trello.
<h2 id="badly">Things Troggle Does Badly</h2>
<h3>Online Wallet Management</h3>
<p>The results are not too bad, but some poor caver has to edit a JSON file in each online wallet on the
<em>expo laptop</em>. It should be a straightforward job to move the code in
<a href="scriptscurrent.html#wallets"><var>wallets.py</var></a> into
troggle, create troggle reports to duplicate the 3 different types of pages produced by the script, and add
an online form to create the equivalent to the JSON file.
<p>The current script does only a single year at a time. When incorporated into troggle, we will be able to
do all outstanding years worth of work.
<p>We have all the wallets data for 1999 but it needs to be restructured into the modern file structure
before we can run the script on it. (We have scanned survey logbooks for 1989-1998 and a wallet structure
could be restrospectively created with a bit of data archeology. If we did that, we could then apply the same
data consistency tools. This is only likely to be worthwhile if we need to seriously return to 1623/161).
<h3>Writing Cave Descriptions</h3>
<p>In 2022 we have a working online form to create or edit the cave and entrance descriptions. But the URL
@ -88,6 +77,14 @@ up all the ARGE surveys, but we could filter those out).
in survex files.
<p>We could do with better reports on survex files which have neved been drawn up ("tunnelled").
<h3>Online Wallet Management</h3>
<p>[Much better now that an external script has been incorporated into troggle and a form has been created for editing wallet data in July 2022. See <a href="/wallets/year/2019">2019 Wallets</a>]
<p>We have all the wallets data for 1999 but it needs to be restructured into the modern file structure
before we troggle can make sense of it. (We have scanned survey logbooks for 1989-1998 and a wallet structure
could be restrospectively created with a bit of data archeology. If we did that, we could then apply the same
data consistency tools. This is only likely to be worthwhile if we need to seriously return to 1623/161).
<h3>API for Different Front Ends</h3>
<p>We have proof of concept for <a href="/api/expeditions_json">one</a> of these: a simple list of
@ -169,6 +166,5 @@ Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />
Troggle index:
<a href="trogindex.html">Index of all troggle documents</a><br />
<hr />
</body>
<hr /></body>
</html>