Line 5: |
Line 5: |
| OpenDoc is a multi-platform software componentry framework standard created by [[Apple Computer]] for compound documents, intended as an alternative to Microsoft's Object Linking and Embedding (OLE). | | OpenDoc is a multi-platform software componentry framework standard created by [[Apple Computer]] for compound documents, intended as an alternative to Microsoft's Object Linking and Embedding (OLE). |
| | | |
− | Apple, WordPerfect, Novell, Borland and IBM share a common goal of making | + | Apple, WordPerfect, Novell, Borland and [[IBM]] share a common goal of making |
− | the user¹s computing experience as easy and productive as possible, and | + | the user's computing experience as easy and productive as possible, and |
| that goal has become increasingly elusive. People are using personal | | that goal has become increasingly elusive. People are using personal |
| computers for more and more complex tasks, often involving multiple | | computers for more and more complex tasks, often involving multiple |
Line 268: |
Line 268: |
| Part handlers can be divided into two types, editors and viewers: | | Part handlers can be divided into two types, editors and viewers: |
| * An editor displays a part¹s content and provides a user interface for modifying that content. This user interface may include menus, controls, tool palettes, rulers, and other modes of interaction. | | * An editor displays a part¹s content and provides a user interface for modifying that content. This user interface may include menus, controls, tool palettes, rulers, and other modes of interaction. |
− | * A viewer offers a subset of an editor¹s functionality; it allows users to display and print a part¹s content, but not to edit it. Viewers can be useful in two document sharing situations: when the recipient of a document does not hold a license to some of the kind of parts included in the document, or when the person sending the document does not want the | + | * A viewer offers a subset of an editor¹s functionality; it allows users to display and print a part¹s content, but not to edit it. Viewers can be useful in two document sharing situations: when the recipient of a document does not hold a license to some of the kind of parts included in the document, or when the person sending the document does not want the recipient to alter it. |
− | recipient to alter it. | |
| | | |
| Both editors and viewers can interpret the contents of the part and | | Both editors and viewers can interpret the contents of the part and |
Line 310: |
Line 309: |
| vendors on many platforms. | | vendors on many platforms. |
| | | |
| + | =The Competition= |
| + | Apple is not alone in recognizing the problems with computing today. In |
| + | fact, we are also far from alone in our efforts to define and implement |
| + | the OpenDoc architecture. Apple's experience with human computer |
| + | interaction, WordPerfect's experience in document-centric computing and |
| + | compound documents, and Novell's expertise in distributed, collaborative |
| + | systems are all playing a part in the definition and implementation of |
| + | this technology. In addition, input has been sought for and discussed |
| + | with many other systems and software vendors, including Borland and [[IBM]], |
| + | and we expect support from many of these other companies for the OpenDoc |
| + | architecture. You can expect to see more announcements in the future |
| + | regarding companies that will be helping implement OpenDoc on additional |
| + | platforms and from software vendors who will be supporting OpenDoc APIs |
| + | in their applications. We are working closely with independent systems |
| + | vendors as well as looking toward cooperation with recognized industry |
| + | associations, such as as the Object Management Group (OMG), Open Software |
| + | Foundation (OSF), and X Consortium. Apple's stated intent is to make |
| + | OpenDoc technology not only cross-platform but also truly open‹with both |
| + | systems vendors and independent software vendors able to obtain the |
| + | source code easily. In contrast, the other major effort along these |
| + | lines, Microsoft's OLE 2.0, is a proprietary approach. Currently, the OLE |
| + | 2.0 source code is held by [[Microsoft]], and provided only under Microsoft |
| + | license. However, OpenDoc will be interoperable with OLE 2.0, so |
| + | developers can take advantage of OpenDoc's broader feature set and |
| + | additional supported platforms without sacrificing OLE support. |
| | | |
− | ==Related Articles== | + | Part of the work the WordPerfect and Novell OpenDoc teams will be doing |
| + | is an implementation of OpenDoc on Windows in such a way that it will |
| + | interoperate with OLE 2.0. Applications that also support the additional |
| + | capabilities represented in OpenDoc will have the ability to interoperate |
| + | at a higher level of functionality on Windows or Macintosh, and to |
| + | interoperate across multiple platforms and distributed systems as well. |
| + | Apple, [[IBM]], and [[Taligent]] plan to design complete interoperability between |
| + | OpenDoc and Taligent, similar to the interoperability between OpenDoc and |
| + | OLE 2.0. This is intended to enable developers and customers to migrate |
| + | to Taligent without losing their investment in software or legacy |
| + | information. |
| + | |
| + | In addition to being much more open, OpenDoc offers a number of specific |
| + | advantages to users and developers: |
| + | |
| + | ===Human interface=== |
| + | The OpenDoc human interface reflects Apple's |
| + | user-centered approach to product design. User testing indicates that |
| + | OpenDoc is a more comfortable, efficient model for users. |
| + | |
| + | ===Cleanliness and simplicity of API=== |
| + | OpenDoc is designed from a minimalist |
| + | viewpoint; it defines as few as possible, flexible features, with |
| + | available source code and clean application programming interface. |
| + | ===Network readiness=== |
| + | OpenDoc handles networking support easily and |
| + | flexibly. Through IBM's System Object Model and the CORBA industry |
| + | standard, it will provide access to distributed object services. This |
| + | aspect of its architecture has been thoroughly reviewed by vendors |
| + | concerned with distributed systems, such as Novell. |
| + | ===Range of platforms=== |
| + | OpenDoc will be initially released on the Macintosh and Windows |
| + | platforms. It is designed to be highly portable and will probably become |
| + | available on other desktop systems, such as UNIX. OpenDoc is also |
| + | designed with the future in mind: OpenDoc parts and documents are |
| + | designed to be interoperable with other compound document systems, such |
| + | as Taligent. |
| + | ===Consistent object model=== |
| + | OpenDoc's object model is compliant with the |
| + | Common Object Request Broker (CORBA) specifications released by the |
| + | Object Management Group (OMG). OMG is a standards body that has defined |
| + | CORBA as a common, industry wide specification for access to object |
| + | services. Because OpenDoc is CORBA-compliant, OpenDoc documents and parts |
| + | will be able to use CORBA-compliant services and interoperate with other |
| + | CORBA-compliant architectures. |
| + | |
| + | =The Shape of the Future= |
| + | The benefits of widespread adoption of the OpenDoc architecture are |
| + | revolutionary for both users and developers. Yet it will be a gentle |
| + | revolution‹one without dramatic upheavals. Because the OpenDoc |
| + | architecture is designed to work with existing applications and |
| + | documents, users will benefits from OpenDoc features without disruption. |
| + | OpenDoc parts will behave much like current applications, enabling |
| + | customers to upgrade without having to go through a new learning process. |
| + | As customers become more familiar with the full scope of OpenDoc |
| + | capabilities (in-place editing, plug-and-play customizing, and more) they |
| + | will build new, convenient, efficient work environments while maintaining |
| + | their current computer-software investment. |
| + | |
| + | This is particularly true for users, who will at first experience little |
| + | or no change, as developers begin to take advantage of the new |
| + | architecture by binding together parts to form units that are virtually |
| + | indistinguishable from the applications of today. It is only over time |
| + | that the full benefits that OpenDoc brings (in-place editing within |
| + | compound documents, the ability to customize applications by adding or |
| + | substituting parts, and more) will become obvious. |
| + | |
| + | For developers, the impact will be felt more rapidly. But here, too, the |
| + | change will not be sudden or disruptive in nature. Developers will simply |
| + | find that OpenDoc empowers them to work in new ways, enabling them both |
| + | to concentrate on existing areas of expertise and to develop new ones. |
| + | OpenDoc will also encourage the vertical market industry, with |
| + | applications increasingly targeting specialized tasks. |
| + | |
| + | The primary concern for each of these companies remains the experience of |
| + | the user (not technology for the sake of technology). OpenDoc represents |
| + | that continuing commitment: to empower people through the provision of |
| + | technology that is both powerful and easy to use, helping them to take |
| + | full advantage of the growing capabilities of computing. |
| + | |
| + | =Related Articles= |
| * [[About OpenDoc]] | | * [[About OpenDoc]] |
| + | * [[The OpenDoc User Experience]] |
| + | * [[Getting Started With OpenDoc Graphics]] |
| + | * [[OpenDoc Parts and SOM Dynamic Inheritance]] |
| + | * [[Working With OpenDoc Part Kinds]] |
| + | * [[Getting Started With OpenDoc Storage]] |
| + | * [[Using Apple Guide 2.1 With OpenDoc]] |
| + | * [[The OpenDoc Road: Facilitating Part Editor Unloading]] |
| + | * [[The OpenDoc Road: OpenDoc Memory Management and the Toolbox]] |
| + | * [[The OpenDoc Road: Making the Most of Memory in OpenDoc]] |
| + | * [[OpenDoc Development Framework]] |
| + | |
| + | =Downloads= |
| + | * ftp://ftp.atlas.altexxa.net/software/mac/os/components/OpenDoc_1.2.1.img.bin |
| | | |
| + | =See Also= |
| + | * [[Apple Computer]] |
| + | * [[Apple Open Collaboration Environment]] |
| | | |
| [[Category:Apple]][[Category:Software]] | | [[Category:Apple]][[Category:Software]] |