Support and General Use > User Interface and Voice
usability: On-screen keyboard
pabouk:
Salival thank you for your ideas. I think there is a need for an on-screen keyboard not occupying the whole screen. Here are my thoughts:
Why are there the boxes around the characters? I think they are completely useless and they take a lot of valuable space.
What are the cursor keys for? The cursor can be much easily moved using button combinations (e.g. ON/PLAY + RIGHT on H100s).
What about other useful characters like
--- Code: ---!@#$%^&*()-_,<.>/?;:' "\|`~[{]}=+
--- End code ---
I have an idea for accented characters:
Double press or long press on a letter can show accented variants for the letter. I.e. for "e" it could be é ě è ë ē ė ę ẹ ẻ ẽ ế Ỡể ễ ệ etc.
To reduce loading of new unicode characters to the font cache it would be usefull to add an option to restrict available characters. It would be fine if the user could select his preferred ISO charset sets as an unicode subset. For example one could enable ISO 8859-1 + 8859-2 for the on-screen keyboard.
JdGordon:
i had an idea of a single line at the bottom (or top) of the screen, which is bassiaclly a slider of all available charachters and u use left/right to choose the char and enter to select it...
much simpler and easier to use than the current one...
Zoide:
I think there could also be Han Zi (Chinese characters), but we'd need something like Pinyin (where you type the romanization and it gives you a list of characters to choose from) and that would probably take a lot of programming... Has anyone thought about this?
salival:
--- Quote from: pabouk on March 16, 2006, 05:38:49 AM ---Why are there the boxes around the characters? I think they are completely useless and they take a lot of valuable space.
--- End quote ---
To make it a little more pleasing to the eye. obviously this may be subject to change.
--- Quote ---What are the cursor keys for? The cursor can be much easily moved using button combinations (e.g. ON/PLAY + RIGHT on H100s).
--- End quote ---
Some programs, like rockword and rocalendar use these to navigate around the "paper". So I thought they would come in handy. Another option would be to be able to quickly toggle between the keyboard and paper. That way these keys become obsolete
--- Quote ---What about other useful characters like
--- Code: ---!@#$%^&*()-_,<.>/?;:' "\|`~[{]}=+
--- End code ---
I have an idea for accented characters:
Double press or long press on a letter can show accented variants for the letter. I.e. for "e" it could be é ě è ë ē ė ę ẹ ẻ ẽ ế Ỡể ễ ệ etc.
--- End quote ---
Those are located under the "acc" (for accents) and "sym" (symbols) buttons.
Ofcourse my version is only a setup and I intended this thread to come to a widely accepted, easy to use, pleasing to the eye (etc. ) solution.
--- Quote from: jdgordon on March 16, 2006, 05:53:28 AM ---i had an idea of a single line at the bottom (or top) of the screen, which is bassiaclly a slider of all available charachters and u use left/right to choose the char and enter to select it...
much simpler and easier to use than the current one...
--- End quote ---
That would mean an awful lot of unnessecary keypresses. IMHO this is only an option to the target where you only have one line available, like remotes.
--------------------------------------------------------------------------------------------------
I played around a little with the japanese layout. As a reference I used the onscreen keyboard which comes with the windows IME. this can use the JIS layout.
(click for the full image)(the characters are less readable because of antialiasing)
Llorean:
Just as a note:
Rockbox is a music player. The first concern should be ease of use for inputting filenames on any of the music player targets. Rockword isn't even in CVS yet, and should it become so it's still not part of the objective of Rockbox to be a PDA replacement.
Any virtual keyboard ideas should be focused around maintaining as much simplicity and ease of use across all targets, and not increasing the binary size any more than absolutely necessary.
I'm of the opinion that the current vkeyboard doesn't have any serious disadvantages other than the characters being too small for some people on the larger screen or higher resolution targets. I think maybe reconsidering the font choice of those and maybe having a larger font and just showing the subset that the H1x0s show is a better solution.
I think any complicated keyboard ideas should be heavily weighed against the "how much bigger will it make the core on Archos" question, because if it doesn't add functionality (If it *just* looks better, and doesn't significantly increase ease of use) is it really worth sacrificing some of the limited binary size you already have?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version