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

documentation updates

Browse Source
This commit is contained in:
Philip Sargent
2021-04-09 13:50:23 +01:00
parent 55d8aeb423
commit f2d83f1926
8 changed files with 44 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
handbook/troggle/trogspeculate.html
View File

@@ -14,7 +14,7 @@
From: Philip Sargent (Gmail) [mailto:philip.sargent@gmail.com]
Sent: 19 April 2020 01:28 [original - since edited with extra refs.]
To: expo-tech@lists.wookware.org
Subject: vague thoughts about future troggle architecture
Subject: vague thoughts about future troggle architecture
</pre>
<p>
@@ -27,8 +27,9 @@ These front-end frameworks get out of date in couple of years or so. So they do
give us the decade-long stability we need to match available maintenance
effort. [ See <a href="https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks">
Wikipedia list of javascript frameworks</a>.] With our deep historical perspective ("cough"),
we can expect this menagerie to sort itself out into a stable, standardised foundation
within the next 10 years.
we can expect <a href="https://www.circleid.com/posts/20201031-the-javascript-ecosystem/">this
menagerie to sort itself</a> out into a stable, standardised foundation
within the next couple of decades but probably not within the next 10 years.
<p>
A web API to expose the troggle database (read-only) would allow some keen
person to write a special-purpose app on a phone, e.g. an entrance-locator