5-row keyboard

Posted by: padmavyuha

5-row keyboard - 12/04/10 09:57 AM

For those happy few who remember the fantastic iKeyEx substrate that meant that in (jailbroken) iOS 3.xx you could have, for example, 5-row keyboards on your iPhone with user-assignable layouts, all is not lost.

Well, all is not found either, because the latest 5-row keyboard for iOS 4.xx iPhones (not iPads) works as a Winterboard layout, and is therefore not flexible at all yet, but it's a start.

Jira Hiraku, the author, is very responsive - he's already fixed a bug I reported this morning, and has promised to add an alternate layout where shift is numbers, non-shift is punctuation - once he's finished his mid-terms!

Posted by: padmavyuha

Re: 5-row keyboard - 12/04/10 10:01 AM

And before anyone asks, no, I don't find myself hitting the wrong keys more often using this layout. The old iKeyEx layout was fantastic, as you could choose the punctuations you used most often and line them up along the top row, which sped up typing no end. It won't be possible using this because of Winterboard limitations, but I hope one day the author of iKeyEx can bring a version of that extension into the 4.x arena.
Posted by: Papa

Re: 5-row keyboard - 12/04/10 03:33 PM

That would take some getting used to but it does look like it would work once you got the hang of it.
Posted by: padmavyuha

Re: 5-row keyboard - 12/04/10 06:21 PM

I really miss the functionality of the 3.x-friendly system. Plus that didn't need winterboard, which is just one more thing to get loaded on a 3G's teensy memory. The iKeyEx substrate had a nice small footprint.

It takes surprisingly little time to get used to - it has taken me longer to get used to not having it any more!
Posted by: Sarah Hastings

Re: 5-row keyboard - 12/14/10 12:36 PM

It has been really simple for me. I am very brisk at iKeyEx substrate.
Posted by: padmavyuha

Re: 5-row keyboard - 04/05/11 09:03 AM

5-Row Keyboard temporarily broken in iOS 4.3.x - fix on the way.
Posted by: padmavyuha

Re: 5-row keyboard - 04/07/11 10:25 AM

Fixed now.