Notices

Originally Posted by bow

I can't even figure out how to execute this thing. A pity, because it looks like a great thing to have for when mudding from the N800. Can anyone provide some really simple instructions? "Installing the thing for Dummies" style

Originally Posted by revwillie

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.

Originally Posted by cvmiller

I like the new xterm as well. I know others have asked for key outlines, but frankly I find things hard enough to read without having more. So less is better for me.

Have you thought about different colors for the overlay keys? For some reason, I am thinking yellow might be good (I'd have to see it).

Another thing. Is it possible to make overlapping keys? Don't know if you have seen the iPod touch, but it's onscreen keyboard looks way too small, but it works really well. It appears that the keys overlap, and there is some method to determine if your finger is covering more one key than the next. Not sure if you have that level of control. But I think it would make it easier to use, if you do.

Thanks again for the really cool and useful xterm!

Craig...

Originally Posted by dnastase

It's my opinion too that less is better in this case, that's why the transparent keyboard is so bare. The problem is that the keyboard is not transparent though.
It just prints over.
I'm working on a version now that will be truly transparent. In this case we may outline the buttons without losing from the terminal content.

Colors, in general, are "de gustibus" (depend on one's taste). The optimal color is also highly dependent on the background color. So this one should be configurable.

I'm not very sure, but I think I know what you're talking about.
From programming point of view (GTK) you're just getting a mouse button press. It's only in a single pixel.
But I think Nokia's lower level touch screen routines are implementing what you're saying. I mean, for sure when you're thumb typing you're pressing many more pixels than just one.
And in my experience the OS2006 on N770 does a better job at approximating what you wanted to press then the OS2007 (on N770). That was one of the main reasons I switched back to OS2006.

Like I said before, I'm having very little misses when I type. My rule is to aim for the symbol. That's printed in the middle of the area where the button is, so it has the highest probability of success.
One way to increase the success rate would be to have bigger buttons, therefore less buttons. I'm also working in this direction, but there is so much I can do if we want to have most of the symbols on the keyboard.

Daniel

Originally Posted by Darius2006

Hi Daniel,

good job, great success.
My congratulations.
Pls tell me if python is a right solution to write a plugin or something else to add some flying buttons to maemo navigation solutions like maemo mapper or pymapper.
Does python has any connectivity to touch screen libraries, functions, methods ?

Thanks.
Darius

Originally Posted by dnastase

It's my opinion too that less is better in this case, that's why the transparent keyboard is so bare. The problem is that the keyboard is not transparent though.
It just prints over.
I'm working on a version now that will be truly transparent. In this case we may outline the buttons without losing from the terminal content.

Colors, in general, are "de gustibus" (depend on one's taste). The optimal color is also highly dependent on the background color. So this one should be configurable.

Daniel