3 ms·
A bit of a tangential question ... If one were to write a simple text editor from scratch - is there some place with a "spec" or list of standard modern text e
by geokon 3y ago
A bit of a tangential question ...
If one were to write a simple text editor from scratch - is there some place with a "spec" or list of standard modern text editor UI paradigms one would need to implement to make the editor feel natural/normal ? (so it feels like Kate/GEdit/contenteditable)
I kinda get there are a lot of little subtle quirks and corner cases that need to be covered so it doesnt feel weird or janky
For instance EMACS CUA-mode is an example of a incredibly incomplete implemention
- jitl 3y agoIt’s not a spec, but I like “Text editing hates you too” [1] and the article that inspired it, “text rendering hates you” [2]. Also Apple’s old documentation about how their text layout system works. That link is annoying to find so I don’t have it on hand. [1]: https://lord.io/text-editing-hates-you-too/ https://lord.io/text-editing-hates-you-too/ [2]: https://faultlore.com/blah/text-hates-you/ https://faultlore.com/blah/text-hates-you/
- richthegeek 3y agoI work on a project at a large (although not Google-scale) company building a collaborative RTE. The short is answer is no, there are very few universal truths about how text editing works. You'll experience differences between combinations of operating systems, input modes (Japanese IME for example), software keyboards on Android, languages (RTL languages) and that's just for text itself. Then when you are thinking about more complex features simple things like "what happens when I double or triple click on this" are a complete crapshoot.