Well, the way I imagined it, if you ever added 'swype-like' input, you could make it a 'third' key layout. Meaning, now you have qwerty, and through that one button, you can toggle it to Alphanumeric. Now imagine you have a third entry in there called Swype, that keeps unchangeable button positions. (That said, I'm sure with enough thought, swype-like input can be written that checks what button is in what position when the vkb is loaded. But that would be a major, major PITA to code.) So you have QWERTY, AlphaNum, "Swype-like", and "Circular/Swirl" - in theory. Again, I honestly think your keyboard is good as is. I don't expect anything so radically new Swype or the circular input methods - I intend on eventually getting good enough to contribute such code myself, but that is a slow process indeed.

If you get around to doing it I'll be happy to share my ideas on making it happen. I can't write the code itself, but I'm decent enough at logic, and can understand programming without necessarily being able to word it in the coding-language-appropriate terminology.

Yeah, I definitely agree with that. (You could probably also just split the next/previous buttons into two each, couldn't you? They seem wide enough to still be usable if split into two buttons, even in portrait mode. That way everyone who likes prev/next gets to keep those buttons, but you also get an extra button, and one for the shift key.) Either way though I do like that idea. It certainly gives you even more room for symbols, although I suggest waiting to see if other people are okay with losing the Next/Prev buttons - I don't use them so far, but I'm sure there are people who like them.

I really need to get off my *** and learn how to recode Hildon, then. (It's in C, I believe?) And yes, I realize how it could he hard. You have to make sure each 'instance' is properly targeting the right application, that it can store the text correctly, etc. But on the other hand, I mean, web browsers do it all the time - they manage to store a bunch of text boxes on different web pages and don't run into collisions. So I am pretty confident it's doable. I just need to learn how to code in that language and get good at it to the point where it would be even feasible for me to try.

I agree. It's doable, but it does not belong in the vkb code. It can be released in a separate package if need be, but it shouldn't be a part of the keyboard. When you meld projects like that, things get messy and inconvenient.