• 1 Post
  • 3 Comments
Joined 10 months ago
cake
Cake day: February 9th, 2024

help-circle

  • dvorakOPtoThumb-KeyToo much variants of thumb keyboard
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    well, it depends. I prefer have 20 good films that 1000 films that are really hard to see. I’m no saying that have many options is bad, I say that is not good have weird options. Like I said a keyboard is class of app very sensible and training the muscular memory is hard and long, and have keyboards with the same name of the official layout supported by the developer is not good because people can think that that’s the variant that the developer gives for that language and is not. I think a quality filter is necesary to add a new keyboard not only a kotlin format filter. If not it will be 1000 layouts and no one can know have to choose.


  • dvorakOPtoThumb-KeyToo much variants of thumb keyboard
    link
    fedilink
    arrow-up
    3
    ·
    10 months ago

    I really hate forks in most of cases, because In most of cases it has the same effect as adding variants and more variants of the same keyboard without any further control that the Kotlin format is correct, because perhaps the arrangement of the letters is not correct, and of course a keyboard is not a mp3 player that you can try for a while and if you see that it is not the right one you change, changing keyboards requires a huge effort and affects muscle memory and is not a game. I used messagease for more than a decade and I didn’t change it for anything. When I discovered thumb-key, what attracted me the most, besides of course being opensource, was that the developer commented that his new distribution was better than Messagease’s, but from what I’ve seen, the only keyboard he maintains is the English version of Thumb-Key. key all the other versions are custom versions from someone who thought that this was the correct distribution for that other language without having provided any argument. Nor has that distribution been approved by the developer beyond that person having uploaded the kotlin file In correct format, there may already be a carrot in the letter “a” that the keyboard will be published as x language keyboard. And when someone else arrives and wants to put a tomato on the “i”, there will be a keyboard that draws tomato emojis on the letter “i”. Of course I understand the position of the developer who considers that in-app modification is not feasible for him, he is the owner of his time and he did a lot by contributing a keyboard like this to the community. But I also think that allowing every person who wants to make a new keyboard to change a key to do so is not the solution at all. and maybe control at least the variants of his own layout because when you open the keyboard you think or I at least thought that the layouts of his keyboard were his, not someone who decided to make the language variant on his own with or without any criteria. For example, I have seen that in French there are two thumb keys, which one starts with the keyboard? which is better? Are any of them supported by the developer or were they created by someone who put the letters by eye without really knowing what they were doing? I believe that this system only creates confusion and fills the list with often absurd layouts. But of course this is just my opinion.