[missing-sync-palmos-dev-talk] Using Cocoa in a Carbon conduit

[Joe Goh]

On 5/17/06, Stuart A. Malone <samalone at llamagraphics.com> wrote:
> Our main application and our conduit are both mainly Carbon code with
> a little Cocoa mixed in, and both use libMissingSyncBridge.a.  So far
> everything is working pretty smoothly under both Missing Sync and the
> HotSync Manager.  We're using NSImage, NSBundle, NSWorkspace, NSSound
> and NSAutoreleasePool and so far have not had any problems with them.

Is there any need to bundle all the Cocoa functionality into a
seperate bundle and load it lazily like that mentioned
http://developer.apple.com/documentation/Cocoa/Conceptual/CarbonCocoaDoc/Articles/LazyCocoaLoading.html
in order to let the conduit work under Palm Desktop?

I ask because it says in the article, "You may want to use lazy
initialization if the Cocoa functionality that you need is not always
required by all users or your application uses CFM."

Thanks!
Joe