TextKit 2 is a nice improvement, but getting the glyph paths in TextKit 1 was so much easier. Now I have to make a wild mix of Core Text and TextKit 2.
#TextKit2
TextKit 2 - the promised land

After 4 years with Apple's TextKit 2: The promised 'better' text engine has unstable scrolling, unreliable height estimates, and viewport issues so bad that even Apple's TextEdit suffers from them. Good architecture, but the implementation makes it frustratingly difficult for real-world apps.

Marcin Krzyżanowski

Account auto-completion has arrived in #Oliphaunt!

Start typing @ in the composer and you’ll get a native-style auto-completion window — right at the caret, just like in Xcode. No clunky bars or overlays — this is proper #Mac behaviour.

It’ll be available in the next build.
Is #Oliphaunt the first Mastodon client to do it like this?

#TextKit #TextKit2 #NSTextView #Cocoa #AppKit #Swift #SwiftUI #macOS #MacDev #macOSDev

I’ve upgraded the toot composer in #Oliphaunt to use TextKit 2 and improved the custom emoji picker — it now appears right at the caret position! I’m really pleased with how this turned out.

#TextKit #TextKit2 #NSTextView #Cocoa #AppKit #Swift #SwiftUI #macOS #MacDev #macOSDev #Mac

I couldn't help myself… #TextKit2
I have started messing with #textkit2 and it is surely interesting. It really is not documented unless I am missing something... But it is definitely a fun challenge!

Gosh there really isn’t a sanctioned way to go from NSTextRange to NSRange, is there? #iOS #TextKit2

I suppose @krzyzanowskim would know if there was