<p>At one time Martin Green attempted to reimplement troggle as "stroggle" using <ahref="https://www.fullstackpython.com/flask.html">flask</a> instead of Django at
<p>A copy of this project is archived by Wookey on <ahref="http://wookware.org/software/cavearchive/stroggle/">wookware.org/software/cavearchive/stroggle/</a>.
but note that this domain has an expired certificate so https:// complains.
<p>The schema for stroggle is <ahref="http://wookware.org/software/cavearchive/stroggle/git/exampledata/expo/schema.json">a schema.json file</a>. See the comparable <ahref="datamodel.html">troggle schema file</a> which is indeed horrendously bigger.
<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>
</div>
<p>Similarly I see little gain from doing the html - python himera
template pages. These contain mainly nested for loops which could just as
<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 <ahref="trogdjango.html">a heavy job</a>.
<p><em>"the horrifying url rewrites that correspond to no files"</em> were bugs introduced by people who edited troggle without knowing what they were doing. We now have a test suite and these have all been fixed.
<p>Troggle is now packaged such that it can run entirely on a standalone laptop and re-loads from scratch in 2 minutes, not 5 hours. So if one has a microSD card with 40GB of historical scanned images and photos, it will run on any Windows or Linux laptop. Even at top camp.
[The effort estimate is similarly a gross underestimate because (a) he assumes one script per page of output, forgetting all the core work to create a central consistent dataset, and (b) he is missing out most
of the functionality we use without realizing it because it is built into
django's SQL system, such as multi-user operations.
fail to keep up with the rest of the world. Right now we need to get ourselves onto python3
so that we can use an LTS release which has current security updates. This is
<ahref="https://docs.djangoproject.com/en/3.0/internals/release-process/#supported-versions-policy">more urgent for django</a> than for Linux. In Ubuntu terms we are on 18.04 LTS (Debian 10) which has no free maintenance updates from 2023. <spanstyle="color:red">We should plan to migrate troggle from django to another framework in about 2025. See stroggle below.</span>]
</em>
</div>
Things this [Rad's] solution doesn't solve:
<ul>
<li> no webpage-based 'wizzard' for creating caves and such (did people use it
much? do we care?) -> maybe 'send an email to this address' is the ultimate
solution to this
<li> uploading photos is still difficult (in the sense that they don't get
