• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Handling international text without text views
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handling international text without text views


  • Subject: Re: Handling international text without text views
  • From: Aki Inoue <email@hidden>
  • Date: Mon, 31 Aug 2009 11:45:55 -0700

The bottom-line window approach was mainly for supporting Carbon applications that cannot be moved from the WNE design model due to its own legacy application structuring.

Since Cocoa is not based on responder message handling design, such event handling model is unnecessary. And the user experience was mostly accepted unfavorably by users, and, thus, Apple is moving away.

We recommend applications to integrate NSTextVIew for all text input needs. It allows you to take advantage of future text enhancements from the Cocoa framework transparently if applicable.

Another option is to implement the NSTextInputClient protocol for your text editing view.
There is a new sample at /Developer/Examples/AppKit/TextInputView coming with Xcode 3.2 showing how to interact with the protocol.


The 3rd option is to implement the bottom-line window behavior by yourself using NSTextView.

Aki

On 2009/08/22, at 19:52, Kyle Sluder wrote:

On Aug 22, 2009, at 12:57 PM, Wade Williams <email@hidden> wrote:

When the application was Carbon, as I recall, I would setup a new TSM document, and that would automatically give me the bottom-line text input bar and I would process the input with my Carbon event handlers. I've been doing some searching on how to accomplish the same thing on Cocoa (enable the bottom-line text entry window and getting events containing the Unicode text), but haven't been able to find anything yet. It appears I might have to do something with NSInputManager, but I haven't really seen how I can accomplish what I want.

Not an expert in this field (though I find myself in the bowels of the text system more and more often), but take a look at the protocols NSText and NSTextView implement. I believe the one you want is NSTextInput.


As for the bottom bar, that might be a legacy Carbon thing. Cocoa input servers provide their own UI.

(But take a look at the stack trace that occurs in -keyDown:. Cocoa creates a TSM document and does all sorts of Carbony things anyway, but you don't get to play with them. Dunno about 64-bit, but you might be able to cross this bridge yourself in 32 bit code.)

Some text system engineers participate on this list. Hopefully one of them, or someone else more knowledgable than I am at the moment, can help you out more.

Good luck!

--Kyle Sluder

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Handling international text without text views (From: Wade Williams <email@hidden>)
 >Re: Handling international text without text views (From: Kyle Sluder <email@hidden>)

  • Prev by Date: Re: How To Unbind
  • Next by Date: Re: 10.6: Check Box Cells in NSTableViews always editable!
  • Previous by thread: Re: Handling international text without text views
  • Next by thread: NSTableView and OutineView resizing bugs
  • Index(es):
    • Date
    • Thread