Who is the mastermind behind HTML term..
it seems to have just stopped..
I would love to see HTML implemented into syncterm, or at least have syterm pull up a stripped version of webkit or someting.
Only if a broweser would make a telnet connection.
Who is the mastermind behind HTML term..
it seems to have just stopped..
Rick Parrish.
https://www.ftelnet.ca
I thought development was still fairly active.. Perhaps he's taking a break and might get back to it eventually..
I'm not sure that really make sense.. SyncTerm is a text-mode client application, and HTMLTerm is a client for web browsers. They're two separate things. Since SyncTerm is already a text-mode client, why would you want something like HTMLTerm integrated into it?
That's possible with HTMLTerm. So I'm not sure what you mean by this..
Who is the mastermind behind HTML term..
it seems to have just stopped..
Sorry, was speaking of a terminal emulator that supports the html menues on 3.17
You are mixed up with the HTML terminal I was speaking of, not a HTTP based one, a TELNET based one that served HTML text and receives commands like telnet.. I think I misworded the "htmlterm" bit.
sbbs@kk4qbn:/sbbs/exec$ ls html*
html.bin html_noyes.js html_shell.js html.src html_who.js html_yesno.js
There should be a terminal progam in the works to support this.
Who is the mastermind behind HTML term..
it seems to have just stopped..
Do you mean the embedded HTML telnet client that is in ecweb?
Ah.. I'm still not sure what "HTML menus" refers to, but I have not heard about this or looked into this. I saw a comment in the code referring to an "HTML terminal" that Deuce was working on, but I'm not sure what that is..
Nightfox
Ah.. I'm still not sure what "HTML menus" refers to, but I have not
heard about this or looked into this. I saw a comment in the code
referring to an "HTML terminal" that Deuce was working on, but I'm
not sure what that is..
Thats more than likely it. the terminal is send HTML vial the JS scripts and then shown via telnet.. html over telnet, not web.
That's an interesting idea, although I'm wondering why not just use the web interface with a web browser? I'm not sure what the advantage would be of a telnet client able to parse/render HTML.
Nightfox wrote to KK4QBN <=-
That's an interesting idea, although I'm wondering why not just use the web interface with a web browser? I'm not sure what the advantage
would be of a telnet client able to parse/render HTML.
Yeah, I'm not sure of the advantages either, but what I would like is to be able to strip HTML from incoming messages in selected areas (specigically, a gated mailing list). Simply selecting the text/plain MIME part is apparently not the answer, I would like to be able to strip the HTML on messages that come from a specific mailing list. In this instance, the HTML probably adds no benefit, so simply stripping it is enough.
Thinking about this further, this could be part of an email pre-processor that strips HTML according to user or sysop preferences (i.e. by email address). Good for those who use BBS tools for their email on Synchronet. Having it optional would allow those of us who use POP clients to receive the HTML as it was intended.
Nightfox wrote to KK4QBN <=-
That's an interesting idea, although I'm wondering why not just use the web interface with a web browser? I'm not sure what the advantage would be of a telnet client able to parse/render HTML.
Yeah, I'm not sure of the advantages either, but what I would like is to be able to strip HTML from incoming messages in selected areas (specigically, a gated mailing list). Simply selecting the text/plain MIME part is apparently not the answer, I would like to be able to strip the HTML on messages that come from a specific mailing list. In this instance, the HTML probably adds no benefit, so simply stripping it is enough.
Thinking about this further, this could be part of an email pre-processor that strips HTML according to user or sysop preferences (i.e. by email address). Good for those who use BBS tools for their email on Synchronet. Having it optional would allow those of us who use POP clients to receive the HTML as it was intended.
Is there any such beast around in JS that will run on Synchronet already?
Nightfox wrote to Vk3jed <=-
I've actually thought about having something like that too.. I've received some emails like that, but not in a while, so I haven't
thought much about that lately.. But I agree it would be useful to
have.
Digital Man wrote to Vk3jed <=-
Is there any such beast around in JS that will run on Synchronet already?
Sort of. There's exec/typehtml.js (for example), which converts HTML
files into Ctrl-A format so that it can be displayed to a BBS terminal/client (usually ANSI).
Digital Man wrote to Vk3jed <=-
Is there any such beast around in JS that will run on Synchronet already?
Sort of. There's exec/typehtml.js (for example), which converts HTML files into Ctrl-A format so that it can be displayed to a BBS terminal/client (usually ANSI).
That sounds useful. Wouuld it be possible to inser that between ListGate and when the message is posted to the sub on the BBS?
I.e., the flow would be mailing list -> ListGate -> typehtml.js -> SBBS.
And hopefully it would pass plain text unaltered.
Digital Man wrote to Vk3jed <=-
Messages imported from lists (via SMTP), just use the alias.cfg feature
of the the Synchronet Mail Server. To modify messages received by the
mail server, you can use an "external mail processor" (see ctrl/mailproc.ini and exec/mailproc_example.js). You could have a mail processor that only acts on listserv messages and converts HTML->bare ASCII (or Ctrl-A or whatever you like). In this scenario, you wouldn't
use typehtml.js, but rather the load/html2asc.js library which is used
by typehtml.js.
That's an interesting idea, although I'm wondering why not just use the web interface with a web browser? I'm not sure what the advantage would be of a telnet client able to parse/render HTML.
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.
There's a lot of ways HTML can format text - I think much more so than text client can render.. A text client for BBSing (from what I've seen) typically doesn't do things like italics, underline, fonts and font sizes, frames, etc.. There's a lot of HTML formatting that would just have to be ignored to display it in a BBS text client. Text colors specified in HTML and CSS could probably be used to some extent, and breaking up paragraphs (with the HTML <P> tag), etc., but I think it would be fairly limited.
Sysop: | Clippy |
---|---|
Location: | Houston, TX |
Users: | 4 |
Nodes: | 4 (0 / 4) |
Uptime: | 72:21:25 |
Calls: | 1 |
Files: | 11 |
Messages: | 38,318 |