expoweb/handbook/troggle/trogassumptions.html

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Handbook Troggle XXX</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>Pre-Troggle Assumptions</h1>
<h3><em>Assumptions</em> and starting points</h3>

<ol>
<li>Let's <var>not</var> try to design a generic catalogue for storing all kind of data about caves of the whole world, intended for every kind of user (sports, exploration, science). 
<ul>
<li>Let's just settle for a generic framework. 
<li>Let geeks in individual countries or individual communities write their tools operating within this framework.
</ul>
<li>Let's try make it available for the layman, but still well-playable for the geeks.
<li>Let's rely on already existing, popular technologies. 
<li>Let's keep it open source and multiplatform. 
<li>Let's try not to reinvent the wheel.
<li>Let's not assume everyone has an Internet connection while working with their data.
<li>Let's version-control as much as possible.
<li>Let's support i18n - let's use UTF-8 everywhere and cater for data in many languages(entrance names, cave descriptions, location descriptions etc.)
</ol>
<p>These are taken from a two page preliminary design document for <a href="../../documents/caca_arch2.pdf">'caca' (Cave Catalogue) rev.2 2013-07-26</a> by Wookey (copied from http://wookware.org/software/cavearchive/caca_arch2.pdf)
<p>Troggle diverges markedly from these ideals in both design and in actual use.
<hr />
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>
New index to all troggle pages 2020-07-27 01:42:09 +01:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
			`<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />`
			`<title>Handbook Troggle XXX</title>`
fix CSS link 2024-02-09 00:01:17 +00:00			`<link rel="stylesheet" type="text/css" href="/css/main2.css" />`
New index to all troggle pages 2020-07-27 01:42:09 +01:00			`</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>Pre-Troggle Assumptions</h1>`
			`<h3><em>Assumptions</em> and starting points</h3>`

			`<ol>`
			`<li>Let's <var>not</var> try to design a generic catalogue for storing all kind of data about caves of the whole world, intended for every kind of user (sports, exploration, science).`
			`<ul>`
			`<li>Let's just settle for a generic framework.`
			`<li>Let geeks in individual countries or individual communities write their tools operating within this framework.`
			`</ul>`
			`<li>Let's try make it available for the layman, but still well-playable for the geeks.`
			`<li>Let's rely on already existing, popular technologies.`
			`<li>Let's keep it open source and multiplatform.`
			`<li>Let's try not to reinvent the wheel.`
			`<li>Let's not assume everyone has an Internet connection while working with their data.`
			`<li>Let's version-control as much as possible.`
			`<li>Let's support i18n - let's use UTF-8 everywhere and cater for data in many languages(entrance names, cave descriptions, location descriptions etc.)`
			`</ol>`
			`<p>These are taken from a two page preliminary design document for <a href="../../documents/caca_arch2.pdf">'caca' (Cave Catalogue) rev.2 2013-07-26</a> by Wookey (copied from http://wookware.org/software/cavearchive/caca_arch2.pdf)`
			`<p>Troggle diverges markedly from these ideals in both design and in actual use.`
			`<hr />`
			`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>`