<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Handbook Troggle NOTES</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> <h2 id="tophead">CUCC Expedition Handbook</h2> <h1>Troggle - the beginnings of a manual</h1> <p>Troggle runs much of the the cave survey data management, presents the data on the website and manages the Expo Handbook. <h3>Rewrite from here on...</h3> <img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a> <p>This troggle manual describes these: <ul> <li>Annual tasks: preparing for next year, finishing last year (troggle & scripts) <li>Architectural documentation of how it all fits together & list of active scripts <li>How to edit and maintain troggle itself. The code is public on repository <a href="../computing/repos.html">:troggle:</a> </ul> <p>This page is mostly an index to other records of what troggle is and what plans have been made - but never implemented - to improve it. Today troggle is used for only three things: <ol> <li>Reformatting all the visible webpages such that they have a coherent style and have a contents list at the top-left hand corner. This is particularly true of the handbook you are reading now and the historic records of past expeditions. <li>Publishing the "guidebook descriptions" of caves. The user who is creating a new guidebook description can do this by filling-in some online forms. (And managing all the cave suvey data to produce this.) <li>Providing a secondary way of editing individual pages of the handbook and historic records pages for very quick and urgent changes. This is the "Edit this page" capability; see <a href="../computing/onlinesystems.html#editthispage"> for how to use it</a> and <em>how to tidy up afterwards</em>. </ol> <p>[Note that /survey_scans/ is generated by troggle and is not the same thing as /expofiles/surveyscans/ at all.] <p>Only a small part of troggle's original plan was fully implemented and deployed. Many of the things it was intended to replace are still operating as a motley collection written by many different people in several languages (but mostly perl and python; we won't talk about the person who likes to use OCamL). Today troggle is used for only three things: <ol> <li>Reformatting all the visible webpages such that they have a coherent style and have a contents list at the top-left hand corner. This is particularly true of the handbook you are reading now and the historic records of past expeditions. <li>Publishing the "guidebook descriptions" of caves. The user who is creating a new guidebook description can do this by filling-in some online forms. </ol> <h3>Troggle Login</h3> <p>Yes you can log in to the troggle control panel: <a href="http://expo.survex.com/troggle">expo.survex.com/troggle</a>. </p> <hr /> <h3><a id="arch">Archived updates</a></h3> <p>Since 2008 we have been keeping detailed records of all data management system updates in the version control system. Before then we manually maintained <a href="../computing/update.html">a list of updates</a> which are now only of historical interest. <p>A history of the expo website and software was published in Cambridge Underground 1996. A copy of this article <a href="../c21bs.html">Taking Expo Bullshit into the 21st Century</a> is archived here. <hr /> 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> </html>