From 96372650c974afb7c75d6e2a44bca4d001efd825 Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@klebos.com>
Date: Wed, 1 Dec 2021 21:59:23 +0000
Subject: [PATCH] trog notes updates
---
handbook/troggle/trog2030.html | 2 +-
handbook/troggle/trogdesign.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index acc11768f..1948e4864 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -92,7 +92,7 @@ we are trying to make future maintenance easier, not harder. But it looks like R
<h3>Things that could be a bit sticky 2 - front-end code</h3>
<p>There is not yet a front-end (javascript) framework on the client, i.e. a phone app or webpage, which is stable enough for us to commit
-effort to. Bits of troggle use very old jQuery ("edit this page", and the svx file editor) , and Flask looks interesting
+effort to (we managed to remove all the jQuery by using recent HTML5 capabilities). Flask looks interesting
(but <a href="https://adamj.eu/tech/2019/04/03/django-versus-flask-with-single-file-applications/">maybe is only simpler when
starting a new project and doesn't scale to complexity</a> the way Django does, but maybe in 2025 we
could see a good way to move all the user interface (rewritten to be GIS-centric?) to the client
diff --git a/handbook/troggle/trogdesign.html b/handbook/troggle/trogdesign.html
index 731f2524b..75b935fa0 100644
--- a/handbook/troggle/trogdesign.html
+++ b/handbook/troggle/trogdesign.html
@@ -18,7 +18,7 @@
<ul>
<li>Critiqued proposal on <a href="trogsimpler.html">future architecture</a>
- <li>A possible <a href="trog2030.html">5 year plan</a>
+ <li>A possible <a href="trog2030.html">5 year plan</a> to 2030
<li>Speculations on <a href="trogspeculate.html">future architectures</a>
</ul>
<hr />