Consider how/if we want to allow text typing input
Open, Needs TriagePublic


Yes, obviously inputting text with no keyboard and touchscreen is cumbersome but to give a preset a short name or to choose a label for metadata, etc it might still be required.

What would be the best approach?

I would definitely opt for a QWERTY layout not an ABC...

Reference, maybe not the best idea though:

I thought about this quite a bit and think the reason that the ABC layouts are used is that every locale has a slightly different keyboard layout so international corps are afraid of the QWERTY approach not fitting anyone but the UK/US folks.

Adding different keyboard layouts per country is definitely an overkill but maybe there are hybrid solutions, thoughts?

eppisai added a subscriber: eppisai.Jan 5 2021, 6:57 PM

few points,

0. Playstation (which also does not support keyboard and nor have touchscreen,but a touchpad) uses QWERTY as default and is sold worldwide.

  1. Although Alphabetical order might not matter that much, but separating alphabets,from numbers and symbols might be a good idea. (numeric keys screen differnt from alphabet keys screen as in conon and other cameras).
  1. Usablity wise, above point can be argued, but still all the characters in one screen gives very cluttered look, to small extend.
  1. Except for France, all the major countries use QWERTY. So, "not fitting anyone except UK/US folk" might not be true, I live in India and have been using QWERTY since I knew what the keyboard was.
  1. Hybrid keyboard would only give a small learning curve to get friendly for the user.

Small correction, not all major countries, e.g. Germany uses QWERTZ.

right, then lets give a QWERTY keyboard prototype a go.

I would opt for upper case only to reduce size/complexity.

We will also need numbers and a few special characters like "-_[]#+,.()/"

sebastian assigned this task to eppisai.Jan 17 2021, 6:59 PM

Aman, could you upload some of your progress reported at the last IRC meetings here? pictures/videos?

eppisai added a comment.EditedJan 17 2021, 8:16 PM

Hello!! This was till 11 January 2020, after taking your and everyone's suggestion, I am incorporating them into the keyboard. I have made quite some changes since then, like changing the underlying algo to an optimized one(using an array of char and not drawing each button individually, which bAndiT1983 had suggested), added knob control, and a few more still doing...(side buttons and up and down navigation and other things)

In the above the keyboard is not yet QWERTY,will be making it proper QWERTY
I'll be finished by tomorrow before the IRC meet I think, so will also update last week's proper progress!

Very cool, thanks!

One thing to think about is how to "finish" typing as "Enter" adds one character currently I assume -> Could say "Done" and the knob push adds a character?

eppisai added a comment.EditedJan 17 2021, 8:24 PM

hmm...I can use the knob to select the alphabets(pressing the knob) since it is being used to navigate(trial basis), and keep the enter button reserved for when the user had finished typing.

Yes, that's what I meant :)

Progress So far..

I couldn't share the complete progress in today's IRC meet due to network issues, but this is the keyboard screen. now, I am adding carriage in the text field, as suggested by Sebastian, and changing the code by using proper data structures (unsigned char or uint8_t), while using the custom button method instead of pushbutton, bandiT1983 is helping with this.

Stay tuned for more ;)

Beautiful, keep it up! 💃

eppisai edited projects, added Restricted Project; removed AXIOM Remote.May 27 2021, 4:44 PM
eppisai edited projects, added AXIOM Remote; removed Restricted Project.
eppisai edited projects, added Restricted Project; removed AXIOM Remote.May 27 2021, 5:15 PM

Please clean up the keyboard code and create a PR for this branch, then code review will follow and ultimately end in a merge.