site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Paul, Am 19.03.2006 um 21:02 schrieb Paul Miller <paul@fxtech.com>: Indeed :-) Do you know if it is possible to create installer plugins using C++/Carbon instead of Objective C++/Cocoa? Actually it's Objective C not Objective C++. Mike -- Mike Fischer Softwareentwicklung, EDV-Beratung Schulung, Vertrieb Web: <http://homepage.mac.com/mike_fischer/index.html> Note: I read this list in digest mode! Send me a private copy for faster responses. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Mike - good news. I'm pretty sure you could make most of your plugin use C/C++/Carbon if you wanted to. There is nothing preventing you from mixing ObjC/ Cocoa code with C/C++/Carbon. I'd say that you probably need to keep the basic ObjC structure as an interface to the InstallerPlugins.framework. Or at least you'd make your life way too difficult trying to get around that. It would probably be possible though since ObjC is based on C and anything you can do in ObjC you can also do with plain C - albeit less elegantly. The ObjC syntax is not hard to learn though if that's your concern. Given that there is no documentation other than the ObjC framework headers at the moment, you already have enough problems to deal with, I'd say. Me, I don't care. I'll use ObjC/Cocoa and if I need something from Carbon I'll just call a Carbon API. The Integration of Interface Builder is way better for Cocoa than it is for Carbon so for the UI part Cocoa is actually a solid advantage, maybe even a requirement. Also mixing a Carbon UI with Cocoa UI tends to be difficult and the Apple Installer seems to be based on Cocoa. So, as the saying goes: when in Rome... This email sent to site_archiver@lists.apple.com