Resource fork

Abstract: An improved method for enumerating resources for use by a client is described. In an exemplary embodiment, the method includes method steps of: storing a source set of resources; receiving a request from the client for resources appropriate for the client; based at least in part on the request, determining a type for the client; based at least in part on the determined type, determining capabilities of the client; determining possible media types that may be derived from the source set of resources that are appropriate for the client; based on the possible media types and based on the set of resources, generating an extended set of resources; communicating the extended set of resources to the client; and processing requests from the client for access to resources from the extended set of resources.

Abstract: A method for automatically registering resources required for an application program module to execute. After the application program module is booted, a registration cache, which is stored in association with the application program module, is examined to determine its status. It indicates whether a registry on the computer system needs to be updated, e.g., after the user has moved files or renamed files. If so, a search is made through a predetermined directory to look for an application file or a dynamic link library file. If either is found, a resource fork in association with the file is opened, and it is determined whether there is a self-registration resource or an Object Linking and Embedded (OLE) Type Library (OTLB) in the resource fork. If found, any self-registration resource is registered by initiating a self-registration dynamic link library, and any OTLB resource is registered by initiating an OLE call.

Abstract: A system and method providing an optimal way to create, manage and use resource data is provided. In an exemplary embodiment, the system and method provide the ability to store resource data in a library, namely a resource library. A resource library includes resource files that can be attached to a regular data file either automatically, for example, by setting an environment variable, or manually. More than one resource library or resource file may be created and simultaneously attached to a data file. The resource file defines attributes of elements that may be used in creating the CAD model. Typically, the resource library includes attributes that are to be standardized across a project, file, or model.

Abstract: A client terminal to support multiple operating systems (OSes) runs a first OS and includes a memory having a data area and an OS area, and a processor configured to back up a file stored in the data area to an OS providing apparatus, to format the OS area, to install a second OS received from the OS providing apparatus, and to restore the backed-up file to the data area. Upon rebooting, the client terminal runs the second OS and reuses the restored file if the file is executable under both the first OS and the second OS. The OS providing apparatus includes a data receiving unit, a memory to store the second OS, and a data transmitting unit to transmit the backed-up file and the second OS to the client terminal.