Information Technology Reference
In-Depth Information
NOTE
A library is usually just a collection of code, with source files. A framework typically builds a single binary and sup-
plies a list of headers for a #import directive. Frameworks can include media content, property lists, and other in-
formation as well as code. The framework's folder structure is fixed. In theory, frameworks include a complete
class architecture, with implied usage patterns and relationships, while libraries are more likely to contain isolated
discrete components. In practice, the distinction is sometimes less clear-cut.
Introducing Plug-in templates
The plug-in templates are specialized, and the details of plug-in design are outside the scope of this topic.
In outline, the Application Plug-in templates are designed to add custom features to existing Apple applications,
such as Address Book, Automator, and so on. These applications are designed with a standard interface, and the
plug-in templates generate code and resource files that match their specific requirements. Experienced deve-
lopers can use them to add new features to these applications. For example, you can use the Interface Builder
plug-in to define your own collection of UI objects and add it to the standard list already built into IB.
The System plug-ins are more low level and can work with more than one application. For example, the Quick
Look Plug-in can implement a preview of a custom data type used in your applications. Some of the plug-in
templates are minimally complex. The IOKit driver plug-in creates a complete empty C++ file and links it
against the Kernel framework. If you're a newcomer to Apple development, you can ignore these more ad-
vanced options.
Search WWH ::




Custom Search