Topics

Build 133

George Cham
 

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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>



Chanelle Allen
 

Hello,
I, also, do not understand the rationale behind having the half screen keyboard only support touch typing. I am not trying to be critical; maybe there is something I am just not understanding. I think that some of you have tried to explain, but I still don't get it. To me, it seems easier to just switch to the iOS keyboard or dismiss FlickType rather than toggling the half screen mode on since VoiceOver navigation is more consistent when FlickType goes away completely. Does this make sense? After typing some text, I flick three fingers down to bring up the half screen or standard mode. Quite often, FlickType reads back what I have written. Then, I place my finger far above where I think the keyboard should be. Problems arise after I have located the edit field where text has been entered and I attempt to use standard VoiceOver gestures to read by word or character. Sometimes, the process works flawlessly, whetting my eagerness to continue testing this new dimension of FlickType and exploring its potential. More often than not, as soon as I begin moving by a specified rotor setting, and the direction I flick my finger makes no difference, I hear the message " FlickType: Flick up with three fingers to switch to full screen mode." but, I just realized something as I have resumed writing the rest of this email. When using VoiceOver navigation, my finger continually needs to remain near the top of the screen. So, if flicking down to read by word, I cannot place my finger somewhere in the middle of the screen where it is more comfortable--even if I have already taken focus away from FlickType by touching the top of the screen. Before figuring out that I need to perform VoiceOver gestures near the top of the screen, sometimes, VoiceOver navigation functioned normally for two or three words/characters before the FlickType message was announced.
The gesture for switching between half and full screen modes is great. If we call the half screen mode "standard mode" I wonder if people would confuse that with the way in which FlickType normally operates--that is, as a full screen keyboard. It's something to consider. I also would like to have an option in Settings to choose my default mode. I have never had vision and struggle with spatial orientation, but I think that testing FlickType's full functionality in the size of the iOS keyboard would be interesting. I need to determine the benefit of tap typing in a half screen mode versus dismissing FlickType altogether. As someone on list said, there could be certain situations where a half screen keyboard is more practical and others where a full screen is more appropriate. I am glad that Kosta is giving us different models to think about and explore.
Chanelle

On Jul 7, 2018, at 12:05, Benny Barber <rebelben@...> wrote:

Kosta,

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!




-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
You automatically follow any topics you start or reply to.

View/Reply Online (#1703): https://flicktype.groups.io/g/alpha/message/1703
Mute This Topic: https://groups.io/mt/23180547/140150
Group Owner: alpha+owner@flicktype.groups.io
Unsubscribe: https://flicktype.groups.io/g/alpha/leave/defanged [chanellem.allen@...]

Benny Barber
 

Kosta,
I want to reiterate that if we go back to the half screen of build 132, it does not work well in the native iOS mail app. It covers up the message body on the iPhone 5S. It may work well for others, but I have to try to scroll up to get to the message body. That is a difficult task with the 3 finger flick up in such a small area. I wanted to put in my 2 cents. Thanks. Get well soon.
Benny

On Jul 7, 2018, at 1:57 AM, FlickType <@FlickType> wrote:

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!