Subj : HTMLTERM
To   : Nightfox
From : KK4QBN
Date : Wed Jul 19 2017 11:22 am

  Re: HTMLTERM
  By: Nightfox to KK4QBN on Mon Jul 17 2017 17:27:18

 Ni> That's an interesting idea, although I'm wondering why not just use the
 Ni> web interface with a web browser? I'm not sure what the advantage would be
 Ni> of a telnet client able to parse/render HTML.


Maybe thats why the idea was killed off, or has'nt been updated? it's all in
CVS, unless I'm thinking wrong, these appear to be JS that send HTML code over
a TERMINAL connection.. eg HTML_yes_no.js, etc..

-rw-r--r-- 1 sbbs sbbs    37 May 15 17:59 html.bin
-rw-r--r-- 1 sbbs sbbs  1113 Jul 29  2007 html_noyes.js
-rw-r--r-- 1 sbbs sbbs 26749 Feb 20  2008 html_shell.js
-rw-r--r-- 1 sbbs sbbs   111 Jul 27  2007 html.src
-rw-r--r-- 1 sbbs sbbs  2223 Jul 28  2007 html_who.js
-rw-r--r-- 1 sbbs sbbs  1113 Jul 29  2007 html_yesno.js

yea.. 2007 was the last time they were fooled with... I guess this was before
html became more "interactive" beats me.. I thought it would have been cool..

maybe it was'nt even what I though it was going to be, but it appears to be a
dupilicate of the generic synchronet system that outputs html formatted text
instead of regular text. the html.bin detects whether they have the HTML
terminal, if does it sends to html_shell.js if not it sends them to default.js.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
 * Synchronet * KK4QBN - kk4qbn.synchro.net - 7064229538 - Chatsworth GA USA

.