![]() ![]() Just now, when I wanted to manually enter typos in the bottom line, it was clunky to dismiss without changing the words. But I don't run into those scenarios often enough that it'd be worth the other downsides. Perhaps if I was hesitating on spelling a challenging word (does it have two of that letter or just one?) it would help me out. I just turned the feature on for the first time since originally disabling it whenever it was introduced.Īfter playing with it briefly, it isn't fast enough to offer me any real help. Sorry that this isn't very likely to help you gain much actionable insight. I like that and will probably copy, but am looking for more autocorrect systems to learn from. On the other hand in Google docs all you need to do is backspace and it undoes the autocorrect. ![]() Then another few keystrokes to get back to what you wanted. but that will remove the space and then select "hello". If that's not what you wanted then there aren't really easy options to undo. In this regard I think macOS is pretty poor.įor example on macOS if you type "hello " then after the space it will be corrected to "Hello ". I'm more interested in UI problems of indication that correction has happened and easy undo when corrections go wrong. I want to integrate with their autocomplete system so users will have consistent experience that way. but I think I'll leave the actual autocomplete logic to macOS. I maybe didn't explain well in my question. I hope to expand on this in future, but right now I'm more focused on text editing fundamentals. Right now it does very little, mostly just expand/collapse and delete. Outline mode is inspired by vim, it's a mode where there is no text input, so you can use typing keys for other purposes. Instead what I do is always exit to "outline mode" with escape key, and then use left/right arrow keys. Hard to beat an app that you make yourself and can change when you see fit.īike does have a keyboard shortcut for expand/collapse, but truth is I don't remember what it is without looking. If you would like me to explain more, please feel free to reach out! ![]() Compress and hard-code this list into the app (or alternatively make it download/update from your site infrequently). Then ask GPT3 (or equivalent) for 3 possible suggestion for next 1-2 words and save them. If I were to do this today, I would still try to get a large volume of text in my target use case (what do most of your users type? Tech project notes? home construction items? grocery lists) and break them down into large lists of 2-3 n-grams. Here's what I did - basically broke down tweets into n-grams (1-4) and then used the 5 most likely next words as suggestions. Long ago, I tried to make a better autocomplete feature so people with speech disabilities have fewer buttons to push. Not sure what your keyboard binding for collapse/expand is but I played with backtick (single key) and loved it because it just feels natural and I never type ` in my notes. While I am right in your target user base, over a decade ago I built for myself and even though there are now so many better solutions to the text outlining problem, it is just too difficult for me to switch. Great product and new features! Will definitely try it out when I get a chance. (I learned a lot about this stuff while working on Notion's rich-text editor, which is all custom.) If you want reliable, relatively low-level control of rich text input on the web, use ProseMirror. The variance of contentEditable is a huge impediment to using the API raw. In Safari, the browser API accepts the arguments to set the selection to the first position inside the strong tag, but normalizes during the API call, and the selection always ends up right before the strong tag. In Chrome, the browser API allows positioning the selection there, but during the input event, the selection ends up normalized to just before the strong tag, so the characters aren't inserted into the tag. On my Mac, Firefox 104.0.2 inserts new characters inside the, so they're bold. Click the button to set the selection to the first position inside the first tag in the contenteditable div. The behavior for inserting text varies by browser and/or OS, unfortunately. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |