Support and General Use > User Interface and Voice
Proposal for a better text editor
Chronon:
I know. ;)
I'm just trying to build a bridge.
DancemasterGlenn:
--- Quote from: Chronon on April 17, 2008, 05:49:22 PM ---I think larger font is kind of tangential to this discussion. Wouldn't that be addressed by support for multi-font capability?
--- End quote ---
Yes. I said that earlier, and realize that it will eventually be addressed. Not really a problem for me, but something I was thinking ahead about.
--- Quote ---As well, if you load a custom keyboard then it should use the user font instead of the system font.
--- End quote ---
Most definitely.
--- Quote ---It seems to me that there's no fundamental difference between the ideas of paging and toggling between character sets. Basically, you're changing the topological structure from being a single LONG ring into a set of disconnected rings. It's very often much faster to jump to the ring you want and then scroll within the ring than to have to scroll all the way through a long, monolithic ring. Paging jumps you to a new set of characters that the scroll functionality allows you to traverse. This is all that the toggling action that DancemasterGlenn has described accomplishes, as well.
--- End quote ---
I think I understand? I definitely don't want all the character sets on one huge line, so yes, I think this is correct.
Also, I think I just actually realized what everyone meant by paging. Let's see if I'm correct: all the capital letters would be on the display at once, and you could scroll through them as they wrap around the screen and all. Then you would press a button (whatever, a long next I guess on an ipod?) and it would display lowercase (turning a page, as it were. This is the paging part, right?). Another click, symbols, another click, numbers (order doesn't matter here, I'm just trying to understand). Is this correct?
Assuming it is, I have no problem whatsoever with this idea. I like my idea fine because in my head it looks pretty, but this sounds like this would be just as easy to use, more visible everything (only having one of these sets on the screen at once frees up more space than the current model of having everything on the screen at once), the idea of having a permanent cursor always on (like my comment in the flyspray task) for moving around with next/prev on an ipod, or deleting something with a long select (examples) still works, and it would even keep the menu button freed up if we wanted to keep using it for morse code. Excellent. Unless I missed something and I'm getting this all wrong.
--- Quote ---That's what I suggested, but I'm having a hard time understanding Glenn and Definebyte's objection to it.
--- End quote ---
It seems I was not understanding quite what you meant, but I never had an outright objection to anything you said. I already told you, your idea was a good one. And it's even better now that (I think) I understand it completely.
EDIT (classic me...): I also can appreciate how this setup would work better than my original idea for non-english languages.
Chronon:
Good. I'm glad my post had some apparent effect in clarifying the situation.
And to confirm, yes, by using pages you could consolidate all capital ASCII letters into one scrollable page, lowercase into another, uppercase Greek into another, etc.
Llorean:
And (in my opinion) a significant benefit is that it wouldn't be fundamentally different than the display for non-wheel targets, they'd just have a more classical way of navigating around the screen full of characters. And touchscreen UIs could allow you to simply tap the desired character. Thus, you wouldn't have different input screens for different targets, just different controls for that screen.
DancemasterGlenn:
Sounds fine to me.
EDIT (I'm on a roll!!!): The more I think about paging, the more I like it. This would really benefit smaller screens, like the nano. I like this idea a lot!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version