expoweb/handbook/troggle/trogdocm.html

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Handbook Troggle Maintenance</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Troggle - Fixing things that break</h1>
<p>The guide to the parser-model-view architecture is in the architecture document.
<p><em>This page will describe the usual things that go wrong: the parsers that break when
faced with user-generated data and how to fix them. Common error messages. How to set up troggle on a new machine. Copies of the older material where that is illuminating.</em>
<p>It concentrates on showing how to find and fix import errors so that the troggle-generated webpages are complete and not full of gaps.
<p>Intended audience: Ideally someone who is not a python programmer will be able to use this page to help them fix import errors.
<p>Also here we will explain the useful diagnostic pages such as <br>
<a href="expo.survex.com/experimental">experimental</a><br>
<a href="expo.survex.com/pathsreport">pathsreport</a><br>
<a href="expo.survex.com/survey_scans">survey_scans</a><br>
<a href="expo.survex.com//admin/core/dataissue/l">/admin/core/dataissue/</a><br>
<a href="expo.survex.com/tunneldata">tunneldata</a><br>
<a href="expo.survex.com/statistics">statistics</a><br>
<a href="expo.survex.com/people">people</a><br>

<hr />
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Go on to: <a href="trognotes.html">Troggle notes to be restructured</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />
<hr />
</body>
</html>
more troggle pages dismemberment 2020-04-02 21:40:30 +01:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
			`<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />`
Generating more outline troggle documentation 2020-04-03 01:06:35 +01:00			`<title>Handbook Troggle Maintenance</title>`
more troggle pages dismemberment 2020-04-02 21:40:30 +01:00			`<link rel="stylesheet" type="text/css" href="../../css/main2.css" />`
			`</head>`
			`<body>`
			`<h2 id="tophead">CUCC Expedition Handbook</h2>`
Generating more outline troggle documentation 2020-04-03 01:06:35 +01:00			`<h1>Troggle - Fixing things that break</h1>`
			`<p>The guide to the parser-model-view architecture is in the architecture document.`
			`<p><em>This page will describe the usual things that go wrong: the parsers that break when`
			`faced with user-generated data and how to fix them. Common error messages. How to set up troggle on a new machine. Copies of the older material where that is illuminating.</em>`
			`<p>It concentrates on showing how to find and fix import errors so that the troggle-generated webpages are complete and not full of gaps.`
			`<p>Intended audience: Ideally someone who is not a python programmer will be able to use this page to help them fix import errors.`
			`<p>Also here we will explain the useful diagnostic pages such as <br>`
			`<a href="expo.survex.com/experimental">experimental</a><br>`
			`<a href="expo.survex.com/pathsreport">pathsreport</a><br>`
			`<a href="expo.survex.com/survey_scans">survey_scans</a><br>`
			`<a href="expo.survex.com//admin/core/dataissue/l">/admin/core/dataissue/</a><br>`
			`<a href="expo.survex.com/tunneldata">tunneldata</a><br>`
			`<a href="expo.survex.com/statistics">statistics</a><br>`
			`<a href="expo.survex.com/people">people</a><br>`
more troggle pages dismemberment 2020-04-02 21:40:30 +01:00
			`<hr />`
			`Go on to: <a href="trogarch.html">Troggle architecture</a><br />`
Generating more outline troggle documentation 2020-04-03 01:06:35 +01:00			`Go on to: <a href="trognotes.html">Troggle notes to be restructured</a><br />`
more troggle pages dismemberment 2020-04-02 21:40:30 +01:00			`Return to: <a href="trogintro.html">Troggle intro</a><br />`
			`<hr />`
			`</body>`
			`</html>`