cocoa-carbon interface design quandary
cocoa-carbon interface design quandary
- Subject: cocoa-carbon interface design quandary
- From: Daniel Child <email@hidden>
- Date: Wed, 07 Dec 2005 00:53:48 -1000
Hi All,
I am writing a Carbon text service (component) that will, among other
things, call up code written in Cocoa. However, I am realizing that
there are all kinds of design possibilities, and I am wondering how to
go.
Possibility A:
The Carbon component initializes a Cocoa application (which has main,
controller, etc.), causing it to launch using something like
NSLaunchApplication wrapped in some kind of C-Callable wrapper. (Is
there a Carbon equivalent?)
Possibility B:
The Carbon component initializes Cocoa bundles, which have their own
functionality.
Requirements:
No matter what, I need there to be communication between the Carbon
component and whatever gets set up in Cocoa. For that, I am assuming
that CFMessagePort is the way to go. (Am open to alternative
suggestions.) There will be more than one "app/bundles", but it is not
necessarily the case that the "app/bundle" will have a full-fledged
menu-bar. Some will definitely not have such a menu.
Having never used or written a bundle, it is hard for me to envision
what the difference would be between setting up a full-fledged app or
simply writing a Cocoa bundle.
If anyone has experience in this area and can give me the heads-up in
advance, I would really appreciate it.
Thanks,
Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden