Hi guys, thank you for your appreciation. We are working to "fix" the rotor issue, maybe using different buttons as Rob said.
Kimber, i don't think that TypeInBraille could be considered as a labor-intensive way of inputting text. After few days of practice you can easily type much faster than using the traditional keyboard or any other app. On our website there is an audio/video that shows how fast, a blind user, can type the same text using both the traditional keyboard and the TypeInBraille keyboard. The blind user was asked to type: "Ok, see you at 5" --> 18 sec with TypeInBraille (after 3 weeks of training), 42 sec with the traditional keyboard (after 3 months of training). It's just a matter of practice. On Tue, May 29, 2012 at 10:57 AM, Rob Harris <[email protected]> wrote: > Love it! This is an old 3GS, but it does what is necessary. I'd like all > editors to have that 3 mode system and they'd all be good, but they > haven't. suggest buttons for changing mode as my device gets confused > between which rotor it is responding to. Ok, you could put it in the menu > even.... and I'm just off to check that you didn't already and I missed > it! > > Ok, it's not in there, and I also note that the bak button, though in the > normal place at the top, doesn't respond to the scrub gesture for going > back > directly and swiping back to the top... gets irritating, but just > remembered the 4 finger thing to go directly to the top or bottom, so we > can > skip that issue. But the scrub would help. > > So it's only the rotor that bugs me or my device a bit, and I'm sure that > can be fixed with specific gestures or arranging an alternative means of > changing mode. > > But still love it for the efficiency, and it is you know; and gets > things > done with much less groping about. > > Bet you could use some of the stray unused hcaracters too even. > > Many thanks, and it is appreciated. > > RobH. > ----- Original Message ----- > From: "EWTEch Accessibility" <[email protected]> > To: <[email protected]> > Sent: Tuesday, May 29, 2012 9:37 AM > Subject: Re: typing on the phone > > > Hi everybody, > > we are the Accessibility Team of EveryWare Technologies, the developers of > TypeInBraille app. > We'd like to know what do you think about our app and if you consider it as > a good solution to type on your mobile device. > > For those who want to get more information about TypeInBraille: > http://www.everywaretechnologies.com/apps/typeinbraille > > Thank you > > > On Mon, May 21, 2012 at 10:03 PM, Jeremiah Rogers < > [email protected] > > wrote: > > > Hi CJ. The initial appeal to me of touch typing was just as you > > described - I liked not having to hunt for te next letter. I did well > > at immediately finding the next letter I wanted. Unfortunately though, > > I seem to be missing the letter on the first try more often now than I > > used to. I'm also intrigued by the thumb thing. Will try that when > > I've more time. > > > > Jeremiah > > > > > > On 5/21/12, Rob Harris <[email protected]> wrote: > > > Depends if the tapper is likely to hit the edge of the screen, then we > > have > > > to swap or change angle dramatically, and have to do a certain amount > > even > > > when touch typing as control type keys need it regardless. - shift, > > return, > > > More numbers/letter/other, etc. > > > > > > But a recent theme about double thumb typing offered an interesting > > > deviation in which case covering half the kb each, the appropriate > thumb > > > hunts and the other taps, and vicerVersa. > > > ----- Original Message ----- > > > From: "Jeremiah Rogers" <[email protected]> > > > To: <[email protected]> > > > Sent: Monday, May 21, 2012 5:35 PM > > > Subject: Re: typing on the phone > > > > > > > > > One question for you split tappers, any tips for when to switch the > > > duties of fingers? Do you have certain letter combos, certain words, > > > etc where you just know you're tapper will become the hunter? Just > > > having sent a couple texts with the split tap method, that's the only > > > thing that seemed odd. > > > > > > I've learned much from this typing discussion. Initially, I loved the > > > touch typing method, but it seems to me that iOS has gotten less > > > responsive, even across hardware, than I remember it being when I got > > > my first iOS device most of two years ago. It may just be my > > > expectations, but I remember touch typing faster, and more accurately, > > > when I got that device than I can now. Prompted by this thread, I'm > > > trying out the split tap method and am quite intrigued. > > > > > > Jeremiah Z. Rogers > > > Mobile: 704-996-5334 > > > Email: [email protected] > > > > > > > > > On 5/19/12, Jane <[email protected]> wrote: > > >> I've found that typingwith both index fingers in portrait work using > > touch > > >> typing works reallly well. I'm not a whiz at it, but it's working. > > >> > > >> Jane > > >> > > >> > > >> On May 19, 2012, at 5:29 AM, Rob Harris wrote: > > >> > > >>> Ok, just trying this thumbs thing, so got the phone sideways, so > > >>> hand > > >>> over > > >>> the one main speaker outlet; so couldn't hear it. Moved hands a > > >>> bit, > > >>> now > > >>> doesn't hold very comfortably; but got a text donein the end. Once > > you > > >>> learn a thing one way, there needs to be a darned good motivation to > > undo > > >>> it > > >>> and learn it another. > > >>> > > >>> RobH. > > >>> ----- Original Message ----- > > >>> From: "Holly" <[email protected]> > > >>> To: "VIPhone" <[email protected]> > > >>> Sent: Saturday, May 19, 2012 2:09 AM > > >>> Subject: Re: typing on the phone > > >>> > > >>> > > >>> I usually type with my thumbs, but sometimes with my right index > > >>> finger. I became accustomed to typing with my thumbs while using a > > >>> querty keyboard on an android. I have used a home row on a computer > > >>> since age nine, so learning to locate keys with my thumbs was not too > > >>> hard. I am not very fast, but it works. I have a bluetooth keyboard > > >>> for longer typing needs. > > >>> > > >>> Holly and Ajax > > >>> > > >>> -- > > >>> You received this message because you are subscribed to the "VIPhone" > > >>> Google > > >>> Group. > > >>> To search the VIPhone public archive, visit > > >>> http://www.mail-archive.com/[email protected]/. > > >>> To post to this group, send email to [email protected]. > > >>> To unsubscribe from this group, send email to > > >>> [email protected]. > > >>> For more options, visit this group at > > >>> http://groups.google.com/group/viphone?hl=en. > > >>> > > >>> -- > > >>> You received this message because you are subscribed to the "VIPhone" > > >>> Google Group. > > >>> To search the VIPhone public archive, visit > > >>> http://www.mail-archive.com/[email protected]/. > > >>> To post to this group, send email to [email protected]. > > >>> To unsubscribe from this group, send email to > > >>> [email protected]. > > >>> For more options, visit this group at > > >>> http://groups.google.com/group/viphone?hl=en. > > >> > > >> -- > > >> You received this message because you are subscribed to the "VIPhone" > > >> Google > > >> Group. > > >> To search the VIPhone public archive, visit > > >> http://www.mail-archive.com/[email protected]/. > > >> To post to this group, send email to [email protected]. > > >> To unsubscribe from this group, send email to > > >> [email protected]. > > >> For more options, visit this group at > > >> http://groups.google.com/group/viphone?hl=en. > > >> > > > > > > -- > > > You received this message because you are subscribed to the "VIPhone" > > Google > > > Group. > > > To search the VIPhone public archive, visit > > > http://www.mail-archive.com/[email protected]/. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group at > > > http://groups.google.com/group/viphone?hl=en. > > > > > > -- > > > You received this message because you are subscribed to the "VIPhone" > > Google > > > Group. > > > To search the VIPhone public archive, visit > > > http://www.mail-archive.com/[email protected]/. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group at > > > http://groups.google.com/group/viphone?hl=en. > > > > > > > -- > > You received this message because you are subscribed to the "VIPhone" > > Google Group. > > To search the VIPhone public archive, visit > > http://www.mail-archive.com/[email protected]/. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/viphone?hl=en. > > > > -- > You received this message because you are subscribed to the "VIPhone" > Google > Group. > To search the VIPhone public archive, visit > http://www.mail-archive.com/[email protected]/. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/viphone?hl=en. > > -- > You received this message because you are subscribed to the "VIPhone" > Google Group. > To search the VIPhone public archive, visit > http://www.mail-archive.com/[email protected]/. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/viphone?hl=en. > -- You received this message because you are subscribed to the "VIPhone" Google Group. To search the VIPhone public archive, visit http://www.mail-archive.com/[email protected]/. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/viphone?hl=en.
