Keeping this brief, expect one more update with RDP support and
cosmetic changes coming in the next month or so (I mean it this time!)
Following that, the next update will be around the release of the iPad
and should have iPad support. iSSH will be a dual iPhone/iPad
application so anyone who purchases an iPad will not need to purchase
iSSH in order to get the updated interface and better use of the
larger real estate on the iPad. The iPad has a lot of cool features
that I think will fit iSSH well.
I've received plenty of feedback and suggestions already for iSSH on
the iPad and I'm trying to take everything into consideration. Please
let me know if you have any ideas in particular or suggestions on UI
design. Thanks and I hope I can really impress with the updates here
in the near future!
Dean
On Wed, 2010-02-03 at 01:39 -0800, Dean wrote:
> iSSH will be a dual iPhone/iPad application
I'm curious how much of an effect this has on the size of applications.
> larger real estate on the iPad. The iPad has a lot of cool features
> that I think will fit iSSH well.
I'm sure I speak for everyone when I say, SDK terms willing, you should
tease us with a screenshot :D
Cheers,
--
Chris Jones
cm...@tenshu.net
www.tenshu.net
Me too. The chances of my buying an iPad are getting greater every
day. It's past "Certainty" now and is up to "GIVE ME ONE NOW".
Oh, is everyone running Screen as their connection string?
http://blog.23x.net/12/ssh-on-the-iphone-at-last.html
And yes, I'll revisit that when the iPad gets released.
--
Jared Earle :: There is no SPORK
jea...@gmail.com :: http://jearle.eu
Hosting :: http://cat5.org
Blog :: http://blog.23x.net
On Wed, 2010-02-03 at 11:03 +0000, Jared Earle wrote:
> Oh, is everyone running Screen as their connection string?
Absolutely! And using byobu since I almost exclusively log into Ubuntu
machines :)
On the UI suggestions, as I recall a revamp of the connection manager was on the list at one time. I'd vote for this above NX (well, and RDP, but that's because I have no windows boxes I manage:-) I realize others certainly DO!).
Right now, I am on different networks depending on where I am. Many of the machines are not visible from the outside, so there really is little point in pinging them. Also, I have accounts on about 2 dozen machines across those networks. Needless to say, having an ssh and vnc entry to each of them in iSSH makes that connection list just a tad long! :-)
Possible interface. I think what might make sense is to set up a hierarchical sort of list, sort of like Unix dirs/Mac Folders that on the top level allowing me to group the machines together for whatever reasons.
For example:
World
Network A
Network B
Now inside them, I would have the machines grouped according to network (one could use other grouping criteria of course, or even none at all).
World
--> machine1.com
--> machine2.com
--> machine3.com
Network A
--> mylocalmachineA1.com
--> mylocalmachineA2.com
--> mylocalmachineA3.com
Network B
--> mylocalmachineB1.com
--> mylocalmachineB2.com
--> mylocalmachineB3.com
Pinging would only take place if I opened the "folder" to which the machines belonged. This avoids having to ping some many at once. Heck my 3G is only 400MHz! :-)
Now for each machine, I'd like to see an SINGLE slot where I can and select Telnet (yes I still use it), SSH, VNC, etc. Also, perhaps on a settings link on that tab, I would be able to set all the options associated with those protocols (ports, passwords, options, etc.)
I think this would be much cleaner than the current long list.
==================================================================
Michael Martin
ArsAstr...@gmail.com
==================================================================