fTelnet

News

The new WBA was complaining about a missing AutoUpdateURL parameter, so I've removed the auto-update code. It wasn't ever used anyway, since I don't have WBA available as a stand-alone release.

So if you use WBA then this should fix the error, and if you don't run WBA, then I wouldn't bother upgrading because there were no changes to fTelnet since yesterday.

Left a bit of debug code in the last release, which caused the close button to prompt you to open a local file rather than to disconnect you.

Maybe this local file loading will interest somebody, so I've left that functionality in there, but it only works in the disconnected state (so when you're connected the button will act as a disconnect button again)

A new release with experimental RIP and VTxxx terminal emulation support has just been uploaded! As usual, the changelog will have a somewhat complete list of changes (I'm bad at keeping a list, so may have forgotten some changes).

I developed a test suite that I'll now use for future versions, which will hopefully catch any obvious bugs in the major features, but if something got through feel free to let me know.

Also, the RIP and VTxxx support is incomplete. For RIP most things work, but there's still a few things left on my TODO list. For VTxxx I've been testing with vttest and most of the displays are correct, but I think the input isn't quite there yet.

Just wanted to post an update about the next release...I was really close to uploading a new version but I had a request for VT100 support come in, and in looking into that I discovered some of the escape sequences were being handled incorrectly, so I'm now in the process of implementing a much more complete, yet simpler, parser. So I apologize to those who I told I would be "uploading a new version later tonight", since that obviously never happened! But hopefully in the next couple days I'll have time to work on and complete the new parser.

Just uploaded a beta version of fTelnet that supports RIPScrip! Support is still in the early stages, so only a small portion of the protocol has been implemented, but it's somewhat usable so I thought I'd upload it for people to have a look at.

With the recent release of Firefox 4, I've had a few people email me letting me know that HtmlTerm isn't working. The issue here is that early beta versions of Firefox 4 did support WebSockets (which is why the message in HtmlTerm mentions Firefox 4 beta suports HtmlTerm), but then support was removed after it was shown to be vulnerable to attacks.

Unfortunately there's nothing that I as the programmer of HtmlTerm, or you as the administrator of your website, can do to fix this -- it's up to each user to individually enable WebSockets support in their browser if they want. I'm working on updating the error message in HtmlTerm to give instructions on how to enable WebSocket support in both Firefox and Opera (since it suffers from the same "disabled by default" problem). Hopefully I'll have a chance to upload this new version this weekend.

I've just uploaded fTelnet and HtmlTerm (and Web BBS Assistant, though it wasn't updated) v11.03.14! It's a fairly minor update from the last beta, so if you've been running that then there's not much new in this, but if you're still using the last non-beta version from last September, then there's been a lot of changes to digest.

Probably the biggest change is that HtmlTerm is now quite functional, so you have a decent alternative to fTelnet for users who don't run an OS supported by Adobe Flash! Although it comes with its own compatibility issues, since not all browsers support all the required HTML5 features yet.

This is kind of old news, but it slipped under my radar until just now...apparently Apple finally enabled WebSocket support in Safari on the iPhone/iPad as of the 4.2 update. So this means that HtmlTerm will now work on those devices!

The screen is REALLY tiny on my iPod Touch, so I'm not sure how useful HtmlTerm will be on that device, but it might look alright on the much larger iPad. Unfortunately the closest thing I have to an iPad is the iOS Simulator that ships with XCode (which I run on the closest thing I have to a MacBook, my Toshiba Tecra running OSX in VMWare), so it's pretty hard to tell exactly how well it works on that device.

So if you have an iPad, please check it out and let me know how it works. You'll have to click in the textbox to bring up the on-screen keyboard, but after that things should work pretty good. Well except for the fact that the on-screen keyboard doesn't have arrow keys, so if your BBS needs them (lightbar navigation or something), then you're going to have problems. But maybe I'll see about adding arrow key buttons to the webpage so you can use those as necessary.

< 1 2 3 4 5 6 7 8 9 >
Get it on Google Play Download on the App Store
Donations for Rick Parrish of R&M Software

Like something you see here? Consider donating to keep development alive!

(Please note that donations are not tax-deductible for income tax purposes.)

Thank you!