<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
<ahref="https://en.wikipedia.org/wiki/Gitorious">git@gitorious.org:stroggle/stroggle.git</a> (but gitorious has been deleted).</p>
<p>A copy of this project is archived by Wookey on <ahref="http://wookware.org/software/cavearchive/stroggle/">wookware.org/software/cavearchive/stroggle/</a>.
<p>There is also a copy of stroggle on the backed-up, read-only copy of gitorious on "<ahref="https://gitorious.org/">gitorious valhalla</a>"<br/>
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
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>]
</div>
How much work would this actually take:
<ul>
<li> most likely one script per page type, so far page types that are
obviously needed:
<ul>
<li>cave index
<li>individual cave descriptions
<li>logbooks
</ul>
<li> more than half of the parsers are already rewriten by me and can be
changed to do this instead of modifying SQL database with minimal effort
<li> html/css side of things already exists, but it would be nice to go for a
[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
