Sorry, the page you requested was not found.

Please check the URL for mistakes. You can also try using the site navigation or search tool to find your content.

Geek Pro

Finally, an Apple interface for remote server updating

From the Editors of The Geek Weekly

Opening secure connections to remote servers is a breeze -- from a desktop terminal. But say you're at lunch, and all you've got is your iPhone. That's when you will wish you had TouchTerm Pro for the iPhone.

The TouchTerm Pro is the latest remote-access app from JBrink, maker of the free TouchTerm SSH client, which is a better-than-nothing way to update server files from a remote location. But the free version just provides a bare text command line, and requires you to tap out long directory names. The TouchTermPro leverages some of the iPhone's key features, such as text-completion, text-magnifying zoom, a customizable gesture-engine and copy-and-paste. Best of all, it uses a GUI directory, instead of having to “cd” through deep directory trees.

Naturally, all this raw power occasionally comes at the price of clarity (emacs, anyone?). Remembering when to tap, swipe-and-tap, or scratch your head to call up a particular function can be about as easy as remembering you car's VIN number. Fortunately, a series of tutorial screencasts on TouchTerm's site will get you up to speed. The app follows suit with a strong online manual and context-sensitive help.

If the shoe still doesn't fit, customize. Nearly every part of TouchTerm Pro can be modified through its (perhaps too) extensive settings panel. Although its $12 price tag won't win any budget app awards, TouchTerm Pro is a great value, backed by an active developer, and a good buy.

--Michael Fitzhugh, tech writer

Back To Top

The Geek Weekly Channel Sponsor

This independent editorial program is brought to you by

Blog

Fring + iPhone = free calls

Turn your iPhone into a VoIP device and make free calls over Wi-Fi. Fring for iPhone lets you do just that. Available for free at Apple's App Store

More>>

Sorry, the page you requested was not found.

Please check the URL for mistakes. You can also try using the site navigation or search tool to find your content.