fTelnet

I've just released a new version with a bugfix for WBA and a bunch of changes to fTelnet. Most of the changes to fTelnet are rather unimportant feature wise, but helped reduce the size of the .swf greatly! I'm a little concerned I may have broke something in the process, so if you notice anything not working right, please drop me a line.

OK, the updated HtmlTerm and WBA have just been uploaded. If you are using either of these products, then I would definitely recommend upgrading (or users of the latest versions of Firefox and Chrome won't be able to connect). If you only use fTelnet, then it's not such a big deal to upgrade since that wasn't updated at all.

Looks like there has been some progress on the HTML5 WebSocket front, and this has caused some problems with HtmlTerm. Basically some of the major browsers have upgraded to a newer version of the WebSocket protocol, and this means that the WebSocket servers (like WBA and Synchronet's websocketservice.js) need to be upgraded too.I now have the websocketservice.js upgrade complete and am testing it out...if all goes well then I'll upload it to the CVS for everyone else to download, and then I'll use the new logic to upgrade WBA next so I can make a new release of it as well.

Additionally, as of Firefox 6 the WebSocket API has been "temporarily namespaced in prevision of upcoming changes to the specification", which means I'll also need to update HtmlTerm to support it and future versions. I'll make this release at the same time as the new WBA release, so it'll all be made available at once.

The good news is that with these changes, all the major browsers should be supported in one form or another:

• Chrome as of version 4
• Firefox as of version 4
• Internet Explorer as of version 10 developer preview
• Safari as of version 5
• Opera as of version 10.70

Some users have been reporting that ANSI screens haven't been displaying correctly in the latest releases of fTelnet, and it looks like it's because I broke something when adding VT100 support! BBSs expect that the cursor will wrap to the beginning of the next line when something is written to the 80th column of the screen, but that wasn't happening in the newer versions, so some screens displayed poorly as a result.

So that's now fixed, and so screens should be displaying correctly again. If you notice any other issues, please let me know!

fTelnet was hanging when attempting to upload a file under certain circumstances, so I've updated the telnet option negotiation code (which seemed to be the culprit).

A new javascript function ClientSetLocalEcho() has been added, allowing you to enable or disable local echo at the push of a button. Probably could have added a configuration option for this as well, but I guess that'll have to wait for the next release now!

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.