expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-03-31 06:06:07 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updating troggle docum. links in handbook

Browse Source
This commit is contained in:
Philip Sargent
2020-07-31 23:20:20 +01:00
parent c5dde279d8
commit e417d28272
12 changed files with 49 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
handbook/troggle/trogsimpler.html
View File

@@ -52,7 +52,7 @@ for displaying a table of members by expedition year, but what if you wanted to
logbook about a certain cave in a certain expedition year? Theoretically, all of the necessary information to produce that
list has been recorded in the logbook, but there is no way to access it because there is no connection between the
person's name in folk.csv and the entries he wrote in the logbook".
[<a href="/expofiles/documents/troggle/troggle_paper.pdf" download>Adrian Curtis</a>]<em>
[<a href="/expofiles/documents/troggle/troggle2020.pdf" download>Aaron Curtis</a>]<em>
<p>And for ensuring survey data does not get lost we need to coordinate people, trips, survex blocks,
survex files, drawing files (several formats), QMs, wallet-progress pages, rigging guides, entrance photos, GPS tracks, kataster boundaries, scans of sketches, scans of underground notes, and dates for all those - Philip Sargent]
</em>
@@ -119,10 +119,11 @@ exist
</ul>
<div style="margin-left: 2em; margin-right:2em; color: blue; font-family: sanserif"><em>
[This vastly underestimates the number of things that troggle does for us.
See "<a href="/expofiles/documents/troggle/troggle_paper.pdf" download>Troggle: a novel system for
cave exploration information management</a>". And a VM is not required to run and debug troggle.
See "<a href="/expofiles/documents/troggle/troggle2020.pdf" download>
Troggle: a revised system for cave data management</a>"</em>.] And a VM is not required to run and debug troggle.
Sam has produced a docker variant which he uses extensively.
<p>Troggle today has 8,200 lines of python (including comments and blank lines), plus 600 in imagekit and 200 in flatpages. 2,200 of those are in the parsers. Django itself has a lot more, including integration with TinyMCE in-browser HTML editor. </em>]
<p>Troggle today has 6,400 non-comment lines of python and 2,500 non-comment lines of django HTML template code. Plus there is the integration with the in-browser HTML editor in JavaScript. Half of the python is in the parsers which will not change whatever we do. Django itself is much, much bigger and includes all the security middleware necessary in the web today.
<p>But maintaining the code with the regular Django updates is <a href="trogdjango.html">a heavy job</a>.]
</div>
How much work would this actually take:
<ul>