Re: osso-xterm w/ overlayed transparent keyboard
 

The longer I look at this solution the more it seems to me to be an ingenious idea.

Re: osso-xterm w/ overlayed transparent keyboard
 

Looks like this is independent reimplementation of same idea
http://jtra.cz/stuff/maemo/xterm.html

Re: osso-xterm w/ overlayed transparent keyboard
 

Damn, how did you find this ?!
I have searched high and low for such a thing before deciding to take the plunge and start implementing mine.

I've checked his sources:
- his changes have bigger amplitude, there is even some python code, I don't know if he has a python interpreter embeded or they are just for testing
- he implemented in a different spot: in the vte library, whereas I have in the terminal_widget.c file of osso-xterm
- there is one big difference in the idea though: I wanted mine to be thumb keyboard, it looks like his is still for use w/ the pen because it's way too small

Re: osso-xterm w/ overlayed transparent keyboard
 

I did not search :-) I've seen it mentioned few months ago on #maemo channel, see http://mg.pov.lt/maemo-irclog/latest.log.html, there is search too.


or it may be some helper to generate the keymap or something (haven't seen the sources)

Well both input methods have its users. Some people simply doesn't like the idea of touching the screen with fingers and prefer pen to keep the screen clean.

Re: osso-xterm w/ overlayed transparent keyboard
 

As a small suggestion (from the screenshot), maybe you could change the shift and control keys to be more remeniscent of a real keyboard (an up arrow for shift, maybe smaller text saying ctrl for control [though the size of the 'key' need not be smaller]).

I agree with others that some sort of outline of keys would be useful. It could even pick up the background colour of the screen and be offset ever so slightly from that so that it's not too intrusive.

Finally, would it be unrealistic to suggest offsetting the middle row of keys horizontally a little. I know these thumb keyboards are meant to use as much screen as possible, but my biggest gripe with the N800's is that the keys aren't quite were I expect them to be. When I want to press 'A', my hand expects it to be below and slightly to the right of 'Q', like a real keyboard.

Re: osso-xterm w/ overlayed transparent keyboard
 

No, no - this is not the "one (almost invisible) screen on top of the other"-idea...

Re: osso-xterm w/ overlayed transparent keyboard
 

I agree. I get frustrated with the stylus keyboard all the time and started using the out of the box thumb keyboard with it's obvious limitations. I haven't played with this version yet, but just from the screenshots, I think it's the coolest F-ing thing I've seen for the IT's so far.

What if the trans keyboard could be toggled on an off with a hard key combo press? Or a screen thumb-sense to activate with a gesture to deactivate? Just tossing out ideas...

Re: osso-xterm w/ overlayed transparent keyboard
 

See that I made another release which has the toggle of the tkbd. There is a button (right end, 2nd row: "X") that hides it.
It can be shown back/toggled from menu. I have chosen to put the menu item first in the "File" so that the tkbd can be toggled very quickly w/ two hardware button presses: menu + center joystick.

Re: osso-xterm w/ overlayed transparent keyboard
 

Hi,

your flying keyboard is really high-tech solution and application, meant highly intelligent one.
As a novice to python, please tell me is application of this kind as yours can be written in python . Is python , as a script language, in anyway fit to develop such solution or to modify one of this kind ?

Thanks.
Darius

Re: osso-xterm w/ overlayed transparent keyboard
 

I like that solution. I'm playing with the new xterm now. I think I get why there are just characters without borders so far, but what I'm finding is that my thumbs are too big and I'm either pressing the wrong character or I'm pressing harder than I think is necessary. Maybe I need to practice more. It just isn't as usable as the built-in thumb keyboard for me...yet.