Browser plug-ins for Mac OS X follow the same basic plug-in architecture
for traditional Mac OS that was introduced by Netscape. A browser plug-in is
implemented as a CFM (Code Fragment Manager) library; all calls
between the browser and the plug-in assume CFM-calling conventions.
All calls between the browser and plug-in are made using simple
Required changes from Earlier Versions of Mac OS
Browser plug-ins for Mac OS X are similar to browser plug-ins for Mac OS 7, 8 and 9 with the following differences:
A plug-in can be a simple CFM library, but may also be built as a
package, or as a packaged data-fork-only file. Packaged data-fork-only plug-ins are encouraged since they can be installed on non-HFS file
On traditional Mac OS, many browsers will look for plug-ins in a
directory adjacent to the browser as well as in the System Folder's
"Internet Plug-Ins" folder. On Mac OS X plug-ins should only be placed in
the /Library/ Internet Plug-Ins directory. The location of the
directory can be determined programmatically with
See Apple Technical Note TN2003 for general information about Carbonizing your code, http://developer.apple.com/technotes/tn/tn2003.html. For more information about how to write a browser plug-in for traditional Mac browser plug-in information, see Netscape's plug-in documentation at the address http://developer.netscape.com/docs/manuals/communicator/plugin/index.htm.
Contact ADC | ADC Site Map | ADC Advanced Search
|For information about Apple Products, please visit Apple.com.|
Contact Apple | Privacy Notice
Copyright © 2002 Apple Computer, Inc. All rights reserved.