On Nov 16, 2007, at 2:51 AM, Alexander von Below wrote:
InputMangers got the boot for 10.5, so if they are involved I would think those are the culprit
I just ran into this message while catching up on list mail. I read on the Cocoa list that actually they are still supported in this release, but the guidelines are more stringent now and they will in fact go away sometime in the future. There is also a new API apparently.
In Leopard, we introduced InputMethodKit. The framework provides API for input method developers moving forward.
It's based on the client server design similar to NSInputServer and, thus, works with all clients regardless of various technologies they are using. It works with Carbon and Cocoa clients, input methods don't have to care about 32bit vs 64bit, running in Rosetta or not, GC-enabled or not, etc, etc.
In favor of IMKit, we're phasing out support for both TSM and NSInputServer based input methods gradually over upcoming releases.
In Leopard, all existing TSM-based input methods are supported.
The documented NSInputServer and NSInputManager API is still supported.
Only significant change we had in terms of binary compatibility is that we tightened the conditions for plug-in NSInputServer.
The specific can be referenced at <
file:///Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/releasenotes/Cocoa/AppKit.html>.