expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

trog notes updates

Browse Source
This commit is contained in:
Philip Sargent 2021-12-01 21:59:23 +00:00
parent c3d0db216a
commit 96372650c9
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/troggle/trog2030.html
View File

@ -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

2
handbook/troggle/trogdesign.html
View File

@ -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 />