|
Wishlist
David Nason
Hi all,
Some people have been mentioning what they would like to see in terms of development. So I thought I'd send out my own wishlist. Larger dictionary. All too often I tap out relatively common words but find they are not in the dictionary, or not offered to me, so have to type it out manually. More variations / derivitives of words. For example the plural of many common nouns are not in the dictionary. And different tenses of verbs. For example, I try to type "subscribed". FlickType offers me "subscriber" as the first option, showing that I got the pattern right, but neither "subscribed" or "subscribes" appear in the suggestions list at all. Learn what I type. For example, I type my name, "Dave" regularly, signing emails etc. However it almost never offers me "Dave" as the first suggestion, usually offering "face" first, with "Dave" appearing somewhere in the list requiring me to swipe down. No matter how many times I have made this change, it still never offers me "Dave" first. Better accuracy of manual typing. It still sometimes selects the letter beside the one I wanted. Insert a space before the first emoji that comes after words or punctuation. I say this because I would want a space in that case, but I do not want a space between two emoji characters. Fix for issue with FlickType inserting spaces before or after quotation marks. Currently I have to go back through my text with the iOS keyboard to fix these. I'm not sure about this one because sometimes I get unwanted spaces and sometimes I don't, so maybe there is a trick to it, or maybe it behaves differently depending on whether the word inside the quotes was tapped or manually touch typed? Support for text expansion shortcuts. Preferably accessing the ones I've already created in iOS settings. Option to switch off the announcements when you open the keyboard. Related to this, the keyboard is sometimes slow to become responsive when opened. The half screen keyboard would be nice to see too, if full functionality could be added and we could fully interact with the elements of the app in the top half of the screen, but for me the above list would take priority. What do other people think? Dave
|
|
|
|
Re: Build 133
High all,
I tried out build 133, and I see no reason to use this version.
I would like to see build 132 expanded and the features included in future versions.
133 is just like an ios keyboard, and I dont see the point in using it.
Kind Regards,
George Cham
‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of David Nason <dnason@...>
Sent: Sunday, July 8, 2018 10:39:25 AM To: alpha@flicktype.groups.io Subject: Re: [FlickType-alpha] Build 133 Hi all, I am very much with chuck and Ed on this. If the half screen keyboard only does the manual typing method, then I really see absolutely no advantage to this over just switching to the standard iOS keyboard. I am of course happy to hear why people might like this, but I just don't get it. Benny, while you may be right in saying that people who don't have enough usable vision may struggle to use the tap typing and gestures on the half screen keyboard, the fact is that this would still also include the manual typing, as the full screen version does, so you would not be losing anything if full functionality was added to the half screen version. That's how I see it currently anyway☺️ Dave > On 8 Jul 2018, at 00:15, Ed Worrell via Groups.Io <ed.worrell@...> wrote: > > Hey Benny, > > Yes this is correct. I feel that this would give everyone the option to have the keyboard they want, or at least close... The unfortunate thing about this is a lot of work to do for kosta with this idea. > > I simply would like to have the ability to change the keyboard size on the fly. Bigger keyboard for emails, and smaller keyboard for texting and searching as there is stuff under the keyboard that I would like to interact with. Incoming messages, search results, etc. >> On Jul 7, 2018, at 3:51 PM, Benny Barber <rebelben@...> wrote: >> >> Hello Ed, >> >> Am I understanding you correctly? You prefer to have a full screen and a standard screen that are exactly the same in function? Thanks. >> >> Benny >> >> -----Original Message----- >> From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Ed Worrell via Groups.Io >> Sent: Saturday, July 07, 2018 4:32 PM >> To: alpha@flicktype.groups.io >> Subject: Re: [FlickType-alpha] Build 133 >> >> Hello all, >> >> I too like chuck use Fleksy and flicktype. I and really wanting to have a smaller version of flicktype. That's why I suggest a mode option... >> This could be implemented in the setting portion of the app. It would allow you to select which mode you would like FlickType presented in when you start editing a text feild. When someone installs and runs the keyboard for the first time the keyboard will be in full screen mode. In settings you could have the option to have flicktype present itself in standard mode, this would be the same size as the default ios keyboard... You could leave the flick gesture to increase or decrease the size of the keyboard. >> >> For example here's how I would run the keyboard with this option. >> I would make the keyboard side standard. This would be great for answering text messages, searching the app store. Basicly for little everyday things that don't take up much time. This would be the default method of text entry for me. >> >> Now lets say I need to peck out a lengthy email such as this one. I would perform the three finger flick up and have the full screen keyboard at my finger tips. The full screen keyboard would allow me to more comfortably bake a longer string of text without the need to be as precise. >> >> This would be the dream keyboard for me in my everyday use. >> >> Ed >>> On Jul 7, 2018, at 3:10 PM, Chuck Dean <cadean329@...> wrote: >>> >>> >>> Hi Benny, >>> Yes, my vision, and probably most people's vision of a half screen keyboard is a smaller keyboard that can be used like FlickType's tap typing and still have the ability to interact with the text fields and iPhone functions above. >>> Perhaps this is not possible with the way FlickType operates. I also use fleksy, which works exactly like the iOS keyboard, in minimal mode, except it allows tap typing. If you happen to stray above the keyboard, nothing really happens and you can continue typing. Personally, I would continue using Fleksy's minimal keyboard if they fixed its two main flaws, the predictive engine is not as good as FlickType, and if it had a much easier way to toggle to the iOS keyboard. Fleksy also has a stuttering problem, but so did I when I was a kid, so I can live with it.😎 >>> >>> I answered 23 emails this morning using FlickType. The first four I was changing between the half screen and full screen until it locked up. Then I restarted my iPhone and finished the other emails by switching between the iOS keyboard and the full screen FlickType keyboard, which I found much easier to and much more stable. >>> >>> I mention this to Kosta because I think this is taking a wrong direction, has very little, if any benefit over changing to the iOS keyboard, and, in my opinion will not be well received by the general public. I'd rather see Kosta use his extreme talents on a better solution. >>> >>> Chuck >>> >>>> On Jul 7, 2018, at 12:51 PM, Benny Barber <rebelben@...> wrote: >>>> >>>> Chuck, >>>> >>>> I understand what you are saying and I assume you would prefer a smaller >>>> full featured tap typing keyboard. I just don't know if smaller is a good >>>> idea for those of us with unusable or no vision,. If Kosta can make the >>>> current version work a little more crisper and consistent, I can use this >>>> version just fine. Just my opinion. Thanks. >>>> >>>> Benny >>>> >>>> -----Original Message----- >>>> From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf >>>> Of Chuck Dean >>>> Sent: Saturday, July 07, 2018 2:01 PM >>>> To: Alpha >>>> Subject: [FlickType-alpha] Build 133 >>>> >>>> >>>> Hi kosta, >>>> >>>> I have played with Build 133 for a while, I really do not see an advantage >>>> with this keyboard over just switching between the FlickType and iOS >>>> keyboards. >>>> When I leave this email, I will switch to the iOS keyboard, which will open >>>> the next email I send, ready to input my contact. I realize you put a lot of >>>> work into this, >>>> >>>> But I don't get it. >>>> Chuck >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > > >
|
|
|
|
Re: Build 133
David Nason
Hi all,
toggle quoted messageShow quoted text
I am very much with chuck and Ed on this. If the half screen keyboard only does the manual typing method, then I really see absolutely no advantage to this over just switching to the standard iOS keyboard. I am of course happy to hear why people might like this, but I just don't get it. Benny, while you may be right in saying that people who don't have enough usable vision may struggle to use the tap typing and gestures on the half screen keyboard, the fact is that this would still also include the manual typing, as the full screen version does, so you would not be losing anything if full functionality was added to the half screen version. That's how I see it currently anyway☺️ Dave
On 8 Jul 2018, at 00:15, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:
|
|
|
|
Re: Build 133
Ed Worrell
Hey Benny,
toggle quoted messageShow quoted text
Yes this is correct. I feel that this would give everyone the option to have the keyboard they want, or at least close... The unfortunate thing about this is a lot of work to do for kosta with this idea. I simply would like to have the ability to change the keyboard size on the fly. Bigger keyboard for emails, and smaller keyboard for texting and searching as there is stuff under the keyboard that I would like to interact with. Incoming messages, search results, etc.
On Jul 7, 2018, at 3:51 PM, Benny Barber <rebelben@bellsouth.net> wrote:
|
|
|
|
Re: Build 133
Ed Worrell
Hey chuck,
toggle quoted messageShow quoted text
As soon as you move to the application part of the window or change focus it could place the text. All though I would be happy with a half screen option that would function just like the current builds. This would allow me to check messages sent from friends and family as they come in. It would not have to place the text until it's dismissed. That would be ok with me. Ed
On Jul 7, 2018, at 4:59 PM, Chuck Dean <cadean329@...> wrote:
|
|
|
|
Re: Build 133
Chuck Dean
Hi Ed, I too would. like a smaller version of FlickType that could use tap typing. But as I understand it, this is not possible with the current configuration. Here is how Kosta explained it: FlickType does not immediately send keyboard events to the textfield, in order to prevent problematic VoiceOver feedback which includes delay, stutter, and perhaps most importantly a lot of erroneous feedback such as "End of document" which would happen with almost every word typed or changed. Instead, FlickType will hold on to all the new text you have typed, and only commit the changes upon dismissal or switching to the next keyboard. But with the half-screen mode, FlickType will also commit all changes as soon as the VoiceOver cursor moves away from FlickType.
On Sat, Jul 7, 2018 at 2:31 PM, Ed Worrell via Groups.Io <ed.worrell@...> wrote: Hello all,
|
|
|
|
Re: Build 133
Benny Barber
Hello Ed,
toggle quoted messageShow quoted text
Am I understanding you correctly? You prefer to have a full screen and a standard screen that are exactly the same in function? Thanks. Benny
-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Ed Worrell via Groups.Io Sent: Saturday, July 07, 2018 4:32 PM To: alpha@flicktype.groups.io Subject: Re: [FlickType-alpha] Build 133 Hello all, I too like chuck use Fleksy and flicktype. I and really wanting to have a smaller version of flicktype. That's why I suggest a mode option... This could be implemented in the setting portion of the app. It would allow you to select which mode you would like FlickType presented in when you start editing a text feild. When someone installs and runs the keyboard for the first time the keyboard will be in full screen mode. In settings you could have the option to have flicktype present itself in standard mode, this would be the same size as the default ios keyboard... You could leave the flick gesture to increase or decrease the size of the keyboard. For example here's how I would run the keyboard with this option. I would make the keyboard side standard. This would be great for answering text messages, searching the app store. Basicly for little everyday things that don't take up much time. This would be the default method of text entry for me. Now lets say I need to peck out a lengthy email such as this one. I would perform the three finger flick up and have the full screen keyboard at my finger tips. The full screen keyboard would allow me to more comfortably bake a longer string of text without the need to be as precise. This would be the dream keyboard for me in my everyday use. Ed On Jul 7, 2018, at 3:10 PM, Chuck Dean <cadean329@gmail.com> wrote:
|
|
|
|
Re: Build 133
Ed Worrell
Hello all,
toggle quoted messageShow quoted text
I too like chuck use Fleksy and flicktype. I and really wanting to have a smaller version of flicktype. That's why I suggest a mode option... This could be implemented in the setting portion of the app. It would allow you to select which mode you would like FlickType presented in when you start editing a text feild. When someone installs and runs the keyboard for the first time the keyboard will be in full screen mode. In settings you could have the option to have flicktype present itself in standard mode, this would be the same size as the default ios keyboard... You could leave the flick gesture to increase or decrease the size of the keyboard. For example here's how I would run the keyboard with this option. I would make the keyboard side standard. This would be great for answering text messages, searching the app store. Basicly for little everyday things that don't take up much time. This would be the default method of text entry for me. Now lets say I need to peck out a lengthy email such as this one. I would perform the three finger flick up and have the full screen keyboard at my finger tips. The full screen keyboard would allow me to more comfortably bake a longer string of text without the need to be as precise. This would be the dream keyboard for me in my everyday use. Ed
On Jul 7, 2018, at 3:10 PM, Chuck Dean <cadean329@gmail.com> wrote:
|
|
|
|
Re: Build 133
Chuck Dean
Hi Benny,
toggle quoted messageShow quoted text
Yes, my vision, and probably most people's vision of a half screen keyboard is a smaller keyboard that can be used like FlickType's tap typing and still have the ability to interact with the text fields and iPhone functions above. Perhaps this is not possible with the way FlickType operates. I also use fleksy, which works exactly like the iOS keyboard, in minimal mode, except it allows tap typing. If you happen to stray above the keyboard, nothing really happens and you can continue typing. Personally, I would continue using Fleksy's minimal keyboard if they fixed its two main flaws, the predictive engine is not as good as FlickType, and if it had a much easier way to toggle to the iOS keyboard. Fleksy also has a stuttering problem, but so did I when I was a kid, so I can live with it.😎 I answered 23 emails this morning using FlickType. The first four I was changing between the half screen and full screen until it locked up. Then I restarted my iPhone and finished the other emails by switching between the iOS keyboard and the full screen FlickType keyboard, which I found much easier to and much more stable. I mention this to Kosta because I think this is taking a wrong direction, has very little, if any benefit over changing to the iOS keyboard, and, in my opinion will not be well received by the general public. I'd rather see Kosta use his extreme talents on a better solution. Chuck
On Jul 7, 2018, at 12:51 PM, Benny Barber <rebelben@bellsouth.net> wrote:
|
|
|
|
Re: Build 133
Benny Barber
Chuck,
toggle quoted messageShow quoted text
I understand what you are saying and I assume you would prefer a smaller full featured tap typing keyboard. I just don't know if smaller is a good idea for those of us with unusable or no vision,. If Kosta can make the current version work a little more crisper and consistent, I can use this version just fine. Just my opinion. Thanks. Benny
-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of Chuck Dean Sent: Saturday, July 07, 2018 2:01 PM To: Alpha Subject: [FlickType-alpha] Build 133 Hi kosta, I have played with Build 133 for a while, I really do not see an advantage with this keyboard over just switching between the FlickType and iOS keyboards. When I leave this email, I will switch to the iOS keyboard, which will open the next email I send, ready to input my contact. I realize you put a lot of work into this, But I don't get it. Chuck
|
|
|
|
Re: Build 133
Michael Maslo
Chuck, I do not know or understand what your saying. I think it is a nice step forward. I find it extremely useful and for me the need to change keyboard less often being needed. Just because you do not find it useful does not mean you speak for everyone else. How do you feel the email shown below is helpful or assist in making this keyboard better?
toggle quoted messageShow quoted text
On Jul 7, 2018, at 14:01, Chuck Dean <cadean329@gmail.com> wrote:
|
|
|
|
Re: Build 133
Benny Barber
Kosta,
toggle quoted messageShow quoted text
I like where you are going with this. I would like there to be consistency in the focus when the custom keyboard is invoked. Sometimes it will open, the initial announcements are spoken and you can start tap typing immediately (optimal scenario). Other times when it opens there are no announcements. If I start typing, the initial announcements begin to speak and I have to clear my taps and start over. As stated in an earlier email, I would prefer the option to toggle off the initial tutor announcements. I would prefer the announcement to simply be "FlickType Full Screen" or FlickType Standard Screen". When one does the 3 finger flick up or down, I would like the same FlickType screen announcement (Full or Standard). With the 3 finger gesture either way, I would like to see the focus to remain in the custom keyboard until you either touch near the top of the screen or flick out of the standard screen. I understand to put focus back into the standard screen, that you must either flick back into it or touch in it. Of course when you 3 finger flick up, the focus should be immediate and ready to tap type in the full screen. For clarity, when I say "focus", I mean "in a ready to type Mode". I don't think I am in favor of a standard sized full featured tap typing screen. Maybe those that have some usable vision may prefer that, but if you have limited or no vision some of the gestures could be difficult, especially some of the 3 finger gestures and any other flick up or down gestures that might be introduced. Again, this is just my opinion. I respect those that have differing thoughts. Thanks. Benny
-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType Sent: Saturday, July 07, 2018 1:57 AM To: alpha@flicktype.groups.io Subject: [FlickType-alpha] Build 133 Another experimental build, based on some of the earlier feedback. - Added a 3-finger flick up and down gesture to switch between fullscreen and standard size modes. Standard size is the same size as the iOS keyboard, and only supports touch typing. The idea is that you would use the standard size mode instead of dismissing the keyboard entirely, and potentially resume fullscreen typing with a 3-finger flick up. The keyboard will commit all changes to the underlying textfield upon entering standard size mode. The keyboard will always default to fullscreen mode when popping up. Please keep the ideas and thoughts coming, smile!
|
|
|
|
Build 133
Chuck Dean
Hi kosta,
I have played with Build 133 for a while, I really do not see an advantage with this keyboard over just switching between the FlickType and iOS keyboards. When I leave this email, I will switch to the iOS keyboard, which will open the next email I send, ready to input my contact. I realize you put a lot of work into this, But I don't get it. Chuck
|
|
|
|
Re: Build 133
Ed Worrell
Hello kosta,
toggle quoted messageShow quoted text
I love the new gesture to make the keyboard standard sized. That's as much as I like in this build. You're just teasing me Doug with the idea of a smaller keyboard...☺️ Things I would like to see... One: a toggle in settings to select which style you would like to be default. Standard size. This being the ios sized keyboard. Option two full sized keyboard. Selecting one of these would make the keyboard launch in that mode every time you enter into a text field. Two: full functionality in the smaller keyboard. Three: the gesture could announce what the keyboard is doing. Swipe up with three fingers and VoiceOver could announce full screen mode. Swipe down and Voiceover could announce something like standard mode... These were my thoughts after playing with the keyboard last night before bed. Thanks, Ed
On Jul 7, 2018, at 9:12 AM, Benny Barber <rebelben@bellsouth.net> wrote:
|
|
|
|
Re: Build 133
Benny Barber
Ok, I am learning that the 3 finger flick up or down must be short and quick. It should not be a long swipe. I'm getting better at it. Thanks.
toggle quoted messageShow quoted text
Benny
On Jul 7, 2018, at 1:57 AM, FlickType <hello@flicktype.com> wrote:
|
|
|
|
Re: Build 133
Benny Barber
I wish we had the option to toggle off the announcements when FlickType is opened. The only announcement that I would like to hear is FlickType full screen or FlickType standard screen. The announcements are good when you are first learning, but they are a little verbose after a while. Just my opinion. Thanks.
toggle quoted messageShow quoted text
Benny
On Jul 7, 2018, at 1:57 AM, FlickType <hello@flicktype.com> wrote:
|
|
|
|
Re: Build 133
Benny Barber
Ok, I'm trying to buy into the latest version. Sometimes the 3 finger gesture does not always work. I have to do it multiple times to get it to work. Sometimes in the full screen, I will start to do the 3 finger flick down and VoiceOver will say space.
toggle quoted messageShow quoted text
Their doesn't seem to be adequate notification if you have changed from full or standard screen. With limited vision, sometimes I don't know which screen I'm in. The inconsistency of the 3 finger flick up and down contributes to this. In the messages app and in standard screen, when you touch in the top the focus is random. I wish focus would be in the text message that you just typed. You have to find the message and then you can swipe to the send button. This may be an iOS issue. Maybe more later. Thanks. Benny
On Jul 7, 2018, at 1:57 AM, FlickType <hello@flicktype.com> wrote:
|
|
|
|
Re: Build 133
Serina Gilbert
I would also like to see the half screen mode have the same ability as the full screen mode. I personally would like to see the text typed displayed smaller in the half screen version as well.
|
|
|
|
Re: Build 133
David Nason
With it just supporting touch typing, I may as well be switching to the standard iOS keyboard. Navigation around the app above the keyboard does seem a little better, but until I can combine this with tap typing on a half screen FlickType, it's hard to really say. An issue to be aware of. I keep the spacebar row hidden in settings, and as a result have no space or delete key. With gestures not working in the half screen mode, I cannot space or delete unless I change that setting. Dave
On 7 Jul 2018, at 08:13, George Cham <George.cham@...> wrote:
|
|
|
|
Re: Build 131
David Nason
I don't like deleting my messages if I can help it, so hopefully won't have to try that. Dave
On 4 Jul 2018, at 19:44, FlickType <hello@...> wrote:
|
|
|
