Notices

i have 2 queries/suggestions:
1. i posted this already but can the keyboard colour be changed to grey or white, because currently it's almost invisible in sunlight
2. why is the portrait kb so small? the landscape goes almost to the top of the screen while the portrait goes halfway. i think it's best not going all the way to the top, but it should be higher so the keys aren't so squashed.

also, will it ever load faster? it's not terrible right now but it is sluggish, and 'portrait keyboard' in devels, although never finished, was pretty fast to open up

Can you make it look like the keyboard in opera mobile? looks really great!!

*Sigh* This keyboard uses your system's theme. If you don't like the darkness of the buttons, get a lighter theme. And no I hope for my own sake that this doesn't look like the Opera keyboard. Don't get me wrong, it's not a bad keyboard - it is pretty nice - but it's not the greatest thing in the world like some people seem to irrationally worship it for being.

Because that's just what hildon-input-method does when the window under it is forced into portrait mode by the rotation of the vkb, but wouldn't be able to rotate normally. Enable rotation in an app you're using the vkb in, then open up the vkb and use it in portrait. It should go all the way up to the almost top when you do that. This has nothing to do with his vkb - if you use the CSSU and force auto-rotation everywhere, you'll see the stock vkb does the same thing in portrait. Scrunches at the bottom.

That's because 'portrait keyboard' was JUST a vkb - this launches the entire FastSMS app. Now, I would think the best solution is slowly splitting the FastSMS package set into three distinct packages - the keyboard-needed files, the settings/configuration package, and FastSMS itself. When FastSMS would be installed it would pull the other two (and use them as widgets within itself), when FastSMSEvo is installed, it would pull in just the settings ui package.

Beyond that you can also make it preload itself on boot, which means slower initial boot time, but most people wouldn't mind. The next difficulty is the swapping i/o one, where if the vkb is swapped, and you're trying to open in when it's in swap, there's i/o collisions and it slows down, so you'd see speed ups with, say, the various kernel/vm tweaks available, swap relocation to microSD, and the like. But those are entirely outside the realm of the keyboard. Alternatively this plugin would have to force the kernel to not swap it out, which is of questionable okay-ness for every user, not to mention probably difficult to do from within Qt.

ok, my main problem with this app is that it overrides the dial pad in the phone application. Or rather, you can't see the number dialled unless you click in the box and wait for the keyboard textbox to appear

Slight bug but its one i dontmindliving with. Tbh I dont find myself consistently touching the text box whenim typing in a number so it isnt really a problem for me.

Neither do i, the problem really is you can't tell if you dial a number wrong. So you have to dial it, tap the box, wait for it to open, check it's correct, tap outside, wait for it to rotate twice which it always does when closing the portrait kb, and then press call. Very cumbersome

So this thing cannot be implemented system wide?

it is system wide

what I mean is for it to show up even in web browsing mode. Heck even come in horizontal mode when it is needed. Simply put, to get away with the generic virtual keyboard.

Errrm mate. This is a system wide keyboard :P

It works everywhere minus a few places where there might be a couple of bugs.