Support and General Use > User Interface and Voice

Proposal for a better text editor

<< < (5/13) > >>

Llorean:
I think the simplest solution would be, for scrollwheel targets, to have it so if you scrolled off the right side of the screen you entered the next side one line down. Then it would behave similar to the line, but without a complicated new system, just one slight change to the behaviour?

DancemasterGlenn:

--- Quote ---It would be worth reading this...
--- End quote ---

Interesting... I'll check this out, looks like a good read.

But yes, the main reason I looked into it at all was the fact that using the scroll wheel to move up and down felt very unintuitive. I'm sure that on targets with four-directional scrolling have a better time with the current model (such as the gigabeat? I've never even held one, but it looks like it's got four directionals...). If the implementation of my idea was even slightly like using the pictureflow plugin, or entering one's name in an arcade game, it seems like it would make it pretty fun to do, as well :)


--- Quote ---I think the simplest solution would be, for scrollwheel targets, to have it so if you scrolled off the right side of the screen you entered the next side one line down. Then it would behave similar to the line, but without a complicated new system, just one slight change to the behaviour?
--- End quote ---

That alone would be a nice change in the current behaviour... one of the weirder aspects is having all the empty space be treated as lots and lots of usable blank characters.

I'm not throwing out ideas simply to shake things up and cause a stir or anything (hopefully you don't think so)... I'm just off in my own little world brainstorming. Your suggestion would be great for the current model, but I'm still hoping someone with some actual skill (i.e. not me) will take enough of an interest in the idea to at least make a simple plugin for people to test out. I have a feeling this would be really fun in practice, and maybe being able to try it out would make more people take interest. And finally, you probably didn't mean this when you said complicated, but at least in my first picture I drew, wouldn't you agree that one line to navigate should potentially be less complicated to navigate?

Llorean:
"Complicated" as in "Adding yet another text input method, causing there to be a yet more code of debatable merit." There would be no practical difference between having scrolling increment/decrement at line end, just a visual difference that would require new code. With my suggestion, existing custom .kbd files would still be entirely usable with it, and a user can usually see all the letters to know whether forward or backward is the shortest path to them (possibly important with non-alphabetical characters such as those in other languages, or symbols, which are not always placed predictably).

DefineByte:
Having all characters on screen at once puts severe limitations on the potential size of the text. Something which I have a particular interest in. :)

shotofadds:
Out of interest, why does the default keyboard use the system font, when a Loadable Keyboard uses the UI font?

Navigation

[0] Message Index

[#] Next page

[*] Previous page