News for hackers. Stuff that matters.
Re:A better iPad keyboard by ctdonath on Sunday November 28, 2010 @02:09PM (#1947953)
Author seems to not realize that several keys show alternates when held.
Re:A better iPad keyboard by sfphotoarts on Sunday November 28, 2010 @02:40PM (#1948054)
I didn't realize that either! Although it just took me a while to find any that did, and even those that do are not very useful. For example round brackets, I cannot seem to hold down any key to get that character.

My biggest grips is 'n'. I keep conjoining words with n because it seems as though I hit that rather than space. Then autocorrect makes matters worse is that it figures it out and rather than breaking the words, it instead keeps the last word and drops the first. This is harder to spot when proofing than if it had just left the conjoined word alone.

I mainly use the blackberry for anything typing heavy.

Re:A better iPad keyboard by etfb on Sunday November 28, 2010 @05:47PM (#1948598)
Years ago, I experimented with a speech synthesiser for the Commodore 64. You used it the typical Commodore way: open a channel to the device, print command codes to the channel. Something like OPEN 3,12,1: PRINT#3, "H0E1L0O3 W0E4R1L0D0";: CLOSE 3 would be the obvious first step (I'm making up the details, but it gives you the idea). One funny thing was that, if you forgot the semi-colon at the end of the PRINT# command, you got an "nnnn" noise at the end of every statement. Why? Because all ASCII characters had associated sounds with the synthesiser, and the end of line character, which the semi-colon suppresses in a print statement, was mapped to the sound of the letter N.

Decades later, totally different technology, and you brought up that memory. Plus ça change and all that.

Re:A better iPad keyboard by pak on Monday November 29, 2010 @11:44AM (#1950851)
I wonder if that was related to "\n", or if the synthesizer intentionally mapped nonprinting characters to sounds (that would seem to make the command set more complicated than necessary, but bytes were precious then so what do I know.)
Re:A better iPad keyboard by etfb on Tuesday November 30, 2010 @12:20AM (#1953182)
Could have been that, but I think it was just a coincidence. In CBMSCII, pronounced "ka-BOOM-ski", which was the warped and bizarre version of ASCII used on the Commodore machines, the end-of-line character was 13, aka Ctrl+M, not the C/Unixy Ctrl+J.

From dim, distant memory, every one of the 255 characters had a sound mapped to it, though surely I'm misremembering since there are only about 40 distinct phonemes in English.

I just remembered that it was called SAM, and here's the Wikipedia link: http://en.wikipedia.org/wiki/Software_Automatic_Mouth Ah, memories...

Re:A better iPad keyboard by Xuzz on Sunday November 28, 2010 @06:02PM (#1948649)
I also hit 'n' as well, both on the iPhone and the iPad. I was worried this was just me, thanks for letting me know I'm not crazy.
Re:A better iPad keyboard by gojomo on Sunday November 28, 2010 @02:36PM (#1948033)
I don't think his flicks are incompatible with the hold-for-alternates option, and the flicks -- with display on the keys -- offer a lot more symbols at easily learnable locations.