Roadmap for the next couple of months

[Dean]

Several things have been brought to my attention so I'm going to
revise the roadmap a little more:

I'm resubmitting 4.2.3 today to deal with the following: (Complete by
this weekend)

* The iphone bug at the at the smallest zoom level
* A customized pager on the key widget for VNC to make it more clear
there are additional keys
* Fix for the advanced settings propagating to all other settings
* Increase stability with temporary ssh connections created via SSH
URLs

Then I plan to focus on 4.0 multitasking, this includes: (Complete by
3rd week in May)

* A configuration setting for setting up any number of port forwards
* The ability to request more time to run in the background
* Notification of the user if the background time is about to run out
so they can request a larger timeslice
* A direct option to use "screen" to automatically connect to sessions
once iSSH has become suspended

Finally I expect to return to RDP and ssh-agent support: (Complete by
early June)

All the while I plan on revising documentation to bring it up to the
current iPad/iPhone version.

Have I missed anything particularly important?

Dean

--
You received this message because you are subscribed to the Google Groups "iSSH/iX11" group.
To post to this group, send email to is...@googlegroups.com.
To unsubscribe from this group, send email to issh+uns...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/issh?hl=en.

[Brendan Erwin]

Support for the arrow and ctrl keys on a physical keyboard. Pretty
important I think.

Sent from my iPhone

[Dean]

Presently there is no way (or in the foreseeable future in iPhone 4.0)
given the public API calls to capture meta keys and arrow keys from an
external keyboard. Apple provided text components simply do not make
this information available outside their boxed components.

If something comes to light that demonstrates otherwise, the road map
will change. Until then, there's nothing I can do.

Dean

On May 7, 12:51 pm, Brendan Erwin <brendanjer...@gmail.com> wrote:
> Support for the arrow and ctrl keys on a physical keyboard. Pretty  
> important I think.
>
> Sent from my iPhone
>

> > For more options, visit this group athttp://groups.google.com/group/issh?hl=en

[Brendan Erwin]

Those bastards! :)


Sent from my iPad

[Garibaldi]

Hi Dean,

Thanks, the roadmap looks good! In regards to arrows, alt, ctrl, and
meta keys, since right now we don't have a solution for supporting
external keyboards, would it be possible for you to write a different
virtual keyboard (which users could optionally use instead of the
built-in iPad keyboard) for iSSH to use which would include these
keys? That would at least bypass the issue of trying to listen for key
events which never appear...

Thanks,

Andrew

[Ezra]

One thing I noticed when experimenting with the bluetooth keyboard --
ALT works! I get funny characters (high bit set) if I use it. I used
this
to hack my keymappings on the host to support things like the command
mode escape in vim.

So, I was wondering, maybe, in lieu of actually control and arrow key
support, if
there was a way to just capture the alt characters and map them to
special keys
(configurable, of course). So, at least one could do alt-(hjkl) for
arrows and alt-c
for control-c, alt-q for esc or whatever.

Ezra

On May 7, 12:51 pm, Brendan Erwin <brendanjer...@gmail.com> wrote:

> Support for the arrow and ctrl keys on a physical keyboard. Pretty  
> important I think.
>
> Sent from my iPhone
>

> > For more options, visit this group athttp://groups.google.com/group/issh?hl=en

[thebasa]

As of OpenSSH 5.4, passphrase-protected rsa private keys are encrypted
with AES-128 instead of the previous 3DES. I already verified that
copy and paste in iSSH can't handle these keys. You get the error
"ciphers other than DES-EDE3-CBC not supported.

[E]

Hey Ezra,

I started down this path but never got it to work. Mind sharing the
details?

Terminal type used?
Specific keymappings setting you have tried/used?

Thanks,
Erik (hoping find some glimmer at the end of this dark, ctrl-less
tunnel!)

On May 8, 1:10 pm, Ezra <ezra.st...@gmail.com> wrote:
> One thing I noticed when experimenting with the bluetooth keyboard --
> ALT works!  I get funny characters (high bit set) if I use it.  I used
> this
> to hack my keymappings on the host to support things like the command
> mode escape in vim.
>
> So, I was wondering, maybe, in lieu of actually control and arrow key
> support, if
> there was a way to just capture the alt characters and map them to
> special keys
> (configurable, of course).  So, at least one could do alt-(hjkl) for
> arrows and alt-c
> for control-c, alt-q for esc or whatever.
>
> Ezra
>

...

[Jeff Clithero]

Hi Erik34 and anyone interested in 'screen key substition,

You have to use the user .screenrc file in your login's home folder, ie:

/home/erik/.screenrc

If you don't have one, copy the general one from your system, often
located here: /etc/screenrc

cp /etc/screenrc ~/.screenrc

I modified my /home/jeff/.screenrc file based on the keys I need for
my main terminal based application "Appgen Business Software".

I need F1 through F10, actually use PF1 through PF4 instead of F1 to
F4, like an old vt100 or vt220 terminal.

I need the up, down, left and right arrows, page-up, page-down,
control-d, control-c, control-A (for screen), Below you'll see my
setup, comments start with #. One key, TAB already works if you hold
Alt + TAB.

Below you'll find a cut from my working "~/.screenrc" and may be a
starting point others. For some reason some keys didn't work until I
moved them to the top of the list, hence the random-ish order of the
key definitions. My comment lines starting with '#' show this:
#desired key === (actual-keys-pressed)
The bindkey syntax is: bindkey X stuff newkey
Replace X above by pressing the key-pair you wish to use for 'newkey',
ie ALT-1

Note: \033 == octal value of ESC,

################### cut from ~/.screenrc ###################
#F10===(alt-0)
bindkey º stuff \033[21~

#F5===(alt-5)
bindkey ∞ stuff \033[15~

#F7===(alt-7)
bindkey ¶ stuff \033[18~

#PageUp===(alt-O)
bindkey ø stuff \033[5~

#Up Arrow===(alt-K)
bindkey ˚ stuff \033[A

#Right Arrow===(alt-L)
bindkey ˙ stuff \033[D

#Down Arrow===(alt-J)
bindkey ∆ stuff \033[B

#Left Arrow===(alt-H)
bindkey ¬ stuff \033[C

#Control-D===(alt-D)
bindkey ∂ stuff \004

#Control-C===(alt-C)
bindkey ç stuff \003

#Control-W===(alt-W)
bindkey ∑ stuff \027

#Control-R===(alt-R)
bindkey ® stuff \022

#PF1===(alt-1)
bindkey ¡ stuff \033OP

#PF2===(alt-2)
bindkey ™ stuff \033OQ

#PF3===(alt-3)
bindkey £ stuff \033OR

#PF4===(alt-4)
bindkey ¢ stuff \033OS

#F6===(alt-6)
bindkey § stuff \033[17~

#F8===(alt-8)
bindkey • stuff \033[19~

#F9===(alt-9)
bindkey ª stuff \033[20~

#PD===(alt-M)
bindkey µ stuff \033[6~

#################### end of cut from ~/.screenrc ################

Have fun!

Jeff

[Dean]

Quick update everyone. Multitasking (both for port forwarding and
keeping connections live) is done and I'm really excited about it.
Now I just have to wait for the 4.0 release.

In the meantime I've been getting tons of feature requests, bug
reports and general feedback. I think I'm going to change the roadmap
again and do a quick release that involves a virtual keyboard of sorts
for those and see if I can't work something in for the option-shortcut
stuff (which will have to be disabled by default for international
distribution reasons). I'm not sure how much value there will be in
having RDP or internal browser support once multitasking is
available. Thoughts anyone?

Dean

[Andrew Plotkin]

On May 14, 1:56 pm, Dean <canada...@gmail.com> wrote:
>  I think I'm going to change the roadmap
> again and do a quick release that involves a virtual keyboard of sorts
> for those and see if I can't work something in for the option-shortcut
> stuff

I've been following this. My personal use case can be rudely summed up
as "die-hard Emacs user, refuses to change" -- so I would ideally want
control *and* option keys available. But I admit ctrl is more
important. :)

A non-standard on-screen keyboard would probably work, but so would a
simple line of buttons directly above the regular iPad keyboard. (I
could squinch my hands into using a control key in the "top row" of
the on-screen keyboard. Up in the toolbar is too high -- besides the
fact that it doesn't act like a modifier key.)

(I *do* have a bluetooth keyboard, and I've bookmarked the option-
screen hack. But I don't generally carry the keyboard around, so ipad-
only is what I'm primarily looking for.)

I am looking forward to the multitasking release, need I say...

[Doug DeJulio]

RDP is still valuable, I think -- I have avoided buying any other RDP
clients because you had announced that it was coming at some point.
Internal browser I don't care about at all, and clearly we all already
have a browser.

On May 14, 1:56 pm, Dean <canada...@gmail.com> wrote:

[Doug DeJulio]

Oh, another thing to recall is that anyone with an iPhone 2G, or 1st
or 2nd gen iPod Touch, will *never* be getting OS 4.0. They're stuck
at 3.1.3 forever. You're not the only developer who will have some
hard decisions about what to do in support of customers with those
devices.