FROM : Ricky Sharp
DATE : Wed Jan 09 22:23:28 2008
On Jan 9, 2008, at 9:25 AM, Sean McBride wrote:
> On 1/9/08 2:13 PM, Matt Gough said:
>
>>> 1. Can I get the same NSWorkspace notifications from somewhere else?
>>> I've
>>> nosed through /System/Library/Frameworks without stumbling across
>>> anything
>>> obvious but I may just be blind.
>>
>> Carbon events seems a good way to go:
>>
>> See kEventClassApplication in CarbonEvents.h
>
> I'm not sure I'd recommend Carbon Events for new code. Apple
> decided to
> kill 64 bit Carbon, and if you look through CarbonEvents.h you'll see
> that most APIs are 32 bit only.
Bad advice; there is still a definite need for Carbon. I would thus
recommend that it is indeed used for new code when necessary. For
example, to get better support for speech synthesis, speech
recognition and Ink, I've had to rely upon the Carbon APIs. Cocoa
APIs do exist for some of these areas, but do not expose all the
capabilities of the underlying APIs.
If/when Apple decides to obsolete Carbon, I'm sure Cocoa APIs will be
added to ensure apps will still have the necessary functionality.
___________________________________________________________
Ricky A. Sharp mailto:<email_removed>
Instant Interactive(tm) http://www.instantinteractive.com
DATE : Wed Jan 09 22:23:28 2008
On Jan 9, 2008, at 9:25 AM, Sean McBride wrote:
> On 1/9/08 2:13 PM, Matt Gough said:
>
>>> 1. Can I get the same NSWorkspace notifications from somewhere else?
>>> I've
>>> nosed through /System/Library/Frameworks without stumbling across
>>> anything
>>> obvious but I may just be blind.
>>
>> Carbon events seems a good way to go:
>>
>> See kEventClassApplication in CarbonEvents.h
>
> I'm not sure I'd recommend Carbon Events for new code. Apple
> decided to
> kill 64 bit Carbon, and if you look through CarbonEvents.h you'll see
> that most APIs are 32 bit only.
Bad advice; there is still a definite need for Carbon. I would thus
recommend that it is indeed used for new code when necessary. For
example, to get better support for speech synthesis, speech
recognition and Ink, I've had to rely upon the Carbon APIs. Cocoa
APIs do exist for some of these areas, but do not expose all the
capabilities of the underlying APIs.
If/when Apple decides to obsolete Carbon, I'm sure Cocoa APIs will be
added to ensure apps will still have the necessary functionality.
___________________________________________________________
Ricky A. Sharp mailto:<email_removed>
Instant Interactive(tm) http://www.instantinteractive.com
| Related mails | Author | Date |
|---|---|---|
| Matt Gough | Jan 9, 14:13 | |
| Jean-Daniel Dupas | Jan 9, 14:17 | |
| Sean McBride | Jan 9, 16:25 | |
| Ricky Sharp | Jan 9, 22:23 | |
| Sean McBride | Jan 9, 22:42 | |
| Nick Zitzmann | Jan 9, 23:19 | |
| Ricky Sharp | Jan 10, 02:21 | |
| Sean McBride | Jan 10, 02:23 | |
| Eric Schlegel | Jan 10, 02:41 |






Cocoa mail archive

