<!DOCTYPE html>
<html>
<head>
<title>Expo Systems - To-Do List</title>
<meta charset="utf-8">

</head>
<body>
<style>
body { 
    background: #fff url(/images/style/bg-system.png) repeat-x 0 0
}
/* Use grey for system/programming/nerd pages as a visual reminder */
</style>

<style>
li.todo {
	font: 18px Calibri, sanserif;
	font-weight: normal;
	color: 6083BF;
	list-style-type: None;
	line-height: 1.0;
	margin-left: 1.0em;
}
li.todo:before {
	content: "ยป ";
	font-weight: normal;
	color: 6083BF;
}
</style>
    <h1>Expo Systems To-Do List</h1>

<h2>How this works</h2>

<p><b>Click on the solid triangle in a sub-heading to reveal</b> the individual to-do items. Click again to hide.<br />
<div  class="onright">
<figure>
<a href='/handbook/computing/l/troggle-todo.html'><img alt="troggle coding lists" src='/handbook/computing/t/troggle-todo.jpg' /></a>
<figcaption style="text-align: center">
<em>Troggle Coding lists<br></em>
</figcaption>
</figure>
</div>  
<p>Printing this page uses a much smaller font. Complain to <a href="mailto:expo-tech@lists.wookware.org">the nerd list</a> if you don't like this behaviour.

<p>Edit this page by using the same "Edit this page" function that you may have used before. 

<p>To see the "data maintenance" and "survey data-entry" to-do lists, go to <a href="todo-data.html">the other TO-DO list</a>
  




<h3>Module to-do texts</h3>
<p>These are extracted directly from the <var>todo = &apos;&apos;&apos;Thing to do &apos;&apos;&apos;</var> string at the top of each file of troggle code:</p>
<hr>

<div>
<figure>
<a href="/todo/anything">
<img  border="1" src="todo-snapshot.jpg" width=45%>
<figcaption>Click here for live list.
</figure></div></a> 
This to-do list is generated directly from the troggle python code files and is the most up to date
to-do list for programming you are likely to find anywhere. Every serious maintainer also maintains their own personal handwritten notes and/or Google Keep lists too.
<hr>

<h3>Other coding To Do things</h3>
<p>See also these long-running issues which have their own 'to do' implications:
<ol>
<li class="todo"><a href="/handbook/troggle/trogdesign.html">What Troggle Does Badly - Design Decisions</a>
<li class="todo"><a href="/handbook/troggle/menudesign.html">New Menu System</a>
<li class="todo"><a href="/handbook/troggle/trog2030.html">Troggle in 2025-2030</a>
</ol>
<h3>Process Documentation</h3>
    <details><summary><!--2020-03-26 psargent-->New-cave</summary>
        <li class="todo"><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
        troggle filesystem
        <li class="todo"><!--2020-03-26 psargent-->Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves
       
    </details>
   

    <details><summary><!--2020-04-13 psargent-->svx check on import/upload/edit</summary>
        <li class="todo">explain command line to run on newly typed survex file to check for format errors '$cavern xxxx.svx' AS WELL AS doing it online
       
    </details>
<h3>Wallets extras</h3>
    <details><summary><!--2023-01-29 psargent-->Things wallets stuff might do in future </summary>
        <li class="todo">- being more intelligent about .topo files and thus the lack of scan files,
       
    </details>
    
<h3>Handbook</h3>
<details><summary><!--2020-04-11 psargent-->Layout and format</summary>  
   
       
        <li class="todo"><!--2020-04-11 psargent-->Chase Airoa to help fix <a href="../troggle/menudesign.html">the menus for phones</a>
        <li class="todo"><!--2020-04-11 psargent-->Look at <a href="https://www.gov.uk/guidance/government-design-principles">gov.uk guidelines</a> for inspiration</details>

<h3>Areas </h3>
<details><summary>SubAreas </summary> 
        <li class="todo"><!--2020-05-01 psargent-->Downgrade the "sub areas" aspect of the documentation as we don't use these now
         <li class="todo"><!--2023-07-14 psargent-->Remove or rename sub areas (called "areas") in the troggle code
        </details>


<h3>Photos</h3>

    <details><!--2023-07-14 psargent--><summary>Shared Google Photos</summary>
        <li class="todo">Devise procedures and code assist to import the shared Expo google photo library into our photo storage area
</details>
<details><summary><!--2020-04-03 psargent-->Fix the BINS package (Wookey is looking for replacement)</summary>
        <li class="todo"><!--2020-04-03 psargent-->set up git on the BINS software? Fix base url sautret.org
        <li class="todo"><!--2020-04-03 psargent-->set up a cron / Makefile job to run BINS
        <li class="todo"><!--2020-04-03 psargent-->why is 'updatephotos' script in expofiles? 
        <li class="todo">Document the ~expo/webphotos/ directory and how it works
        <li class="todo">Why does expofiles/photos/xml/ get created containing all the generated xml files? Fix this.
</details>
    <details><summary>galley thumbs etc.</summary>
        <li class="todo">:expoweb:/galley/0.htm thumbnails not loading
</details>


    
   
<h3>Troggle Refactoring</h3>

<details><summary><!--2022-02-15 psargent-->MIME types and filename extensions</summary>
<li class="todo">We should use standard <a href="https://docs.python.org/3/library/mimetypes.html">https://docs.python.org/3/library/mimetypes.html</a> 
to convert between mimetypes and filenames, not our own hacks
<li class="todo">We should not be relying on filenames to accurately describe the format of the files. This is not robust and may also be a bit insecure. 
We should use <a href="https://github.com/ahupp/python-magic">python-magic</a> or some other wrapper around Linux  libmagic1 C library. 
But note that there are TWO packages called python-magic, see https://stackoverflow.com/questions/436220/how-to-determine-the-encoding-of-text/16203777#16203777
    </details>


<details><summary><!--2020-07-24 psargent-->Python documentation: Django's use of modern unobvious idioms</summary>
        <li class="todo"><!--2020-07-24 psargent-->[DECORATOR] pattern used for login-required pages
        <li class="todo"><!--2020-07-24 psargent-->Get all trogglistas to read https://ebookscart.com/effective-python-by-brett-slatkin-pdf-download/ - downloded to /expofiles/
        <li class="todo"><!--2020-07-24 psargent-->Get all trogglistas to read https://martinfowler.com/tags/refactoring.html
    </details>

        
<h3>Expo Server</h3>
<details><summary><!--2020-07-24 psargent--> document cgit installation and config</summary>
        <li class="todo"><!--2020-07-24 psargent-->as per Wookey on  Debian 10. Finish merging Wookey's instructions into handbook
    </details>


<details><summary>MySQL configuration </summary>
        <li class="todo"><!--2022-02-18 psargent-->robots.txt completely missing from /home/expo/static or troggle:/media
  
       
      
</details>
<details><summary>anacron and cron </summary>
 <li class="todo"><!--2020-05-14 psargent-->Document "anacron" / cron system on server
</details>

<h3>The To Do pages</h3>
<p>We were working on a more capable and easier-to-use to-do system which would mimic 
how <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">GitHub Issues</a> do this sort of thing, 
but now we are just using standard HTML5 tags. OK, using RST could be explored: <a href="todo.rst">todo.rst</a> but we don't have a renderer/editor for it yet. 
But <a href="/handbook/computing/todo.html_edit">you can edit this page</a> very easily.

<hr>
See also <a href="todo-data.html">Data maintenance to-do list</a><br />
Back to <a href="onlinesystems.html">Online Systems manual</a>

<hr /></body>
</html>