CA2155357C - Dynamic linking system - Google Patents
Dynamic linking system Download PDFInfo
- Publication number
- CA2155357C CA2155357C CA002155357A CA2155357A CA2155357C CA 2155357 C CA2155357 C CA 2155357C CA 002155357 A CA002155357 A CA 002155357A CA 2155357 A CA2155357 A CA 2155357A CA 2155357 C CA2155357 C CA 2155357C
- Authority
- CA
- Canada
- Prior art keywords
- document
- anchor
- command
- const
- virtual
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 claims abstract description 47
- 238000010276 construction Methods 0.000 claims description 2
- 230000009471 action Effects 0.000 abstract description 13
- 150000001768 cations Chemical class 0.000 abstract 1
- 230000003068 static effect Effects 0.000 description 15
- 238000012545 processing Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 10
- 230000006399 behavior Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 238000013461 design Methods 0.000 description 6
- 238000013459 approach Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000005538 encapsulation Methods 0.000 description 3
- 239000004956 Amodel Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 239000003550 marker Substances 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 239000003607 modifier Substances 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000004873 anchoring Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000002243 precursor Substances 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/543—User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/134—Hyperlinking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Document Processing Apparatus (AREA)
- User Interface Of Digital Computer (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
- Digital Computer Display Output (AREA)
Abstract
A method and system for selecting a location in a first document, selecting a location in a second document, performing an action on the second document and performing the identical action on the first documen t at the defined location. An alternative embodiment lin ks a first objet to a second object and performs an action, such as launching an application of the second object, and remembering the lo cation where the document was last accessed. Another embodiment, termed the whole m odel embodiment, provides an anchor to an entire object. The anchor enables an action to be applied to the whole object. For example, to copy data from a clipboard object, the copy command is directed to the anchor of the clipboard object. Still another embodiment pro vides an anchor representative of the first misspelled w ord or highest value in a document or a spreadsheet.
Description
._ ~ . . - _ .... ~ ,nJ n . . ...G..- , z;J v. ~.u.~:.."IT~.
AAd~t~ED ShE
B~NAMIC LINKING SYSTEM
Copyright Notification This patent application contains copyrighted material the reproduction of which is permitted only as part of the patent application for its informative purposes.
All other rights, in particular the right of a commercial exploitation of such material, are reserved.
Field of the Invention This invention generally relates to improvements in computer systems and more particularly to a system and method for linking operations and areas of information between documents.
Background of the Invention Document processing is currently the most prey alent application of personal computer technology. Examples of state of the art word processing technology include the WordPerfect ~ text processor and the Word text processor from Microsoft ~ Corporation. These products are designed to run on various operating systems and different hardware platforms. It would be convenient to share information between applications resident on a single hardware platform.
This capability has been hard coded into some applications establishing an automatic update of business chart data by editing a graphic chart as illustrated in US Patent 4,b74,043. Other examples of linking a saved file to another document are found in Microsoft Wir~dows, Version 3.I, "User's Guide," pp. 487-514 which describes a cold link capability. On pages 494-495 of the document the procedures for creating a link between a saved document and another document are described. In the described system, changes to the linked document that are saved on a disk will be reflected in the document that contains the link.
C ~...._.
~.~.L'e,: ~J .
-lA-However, dynamic anchoring of information in ~ first document and exchanging updates based on actions ta~en in a second document, in accordance with the subject invention, is not possible in today's word processing environment Summary of the Invention Accordingly, it is a primary objective of the present invention to provide a system and method for selecting a location in a fist document, selecting a location in a second document, performing an action on the second document and automatically performing the identical action on the first document at the defined location. An alternative embodiment links a first abject to a second object and performs an action, such as launching an application of the second object, and performs an action, such as launching an application of the second object, and remembering the location where the document was last accessed. Another embodiment, termed the whole model embodiment, provides an anchor to an entire object. The anchor enables an action to be applied to the whole object. For example, to copy data from a clipboard object, the copy command is directed to the whole object anchor of the clipboard object. Still another embodiment provides an anchor representative of the first misspelled word or highest value in a document or a spreadsheet.
In accordance with one aspect of the present invention there is provided an apparatus for dynamically linking a first document to a second document under control of an application program so that changes made in one document are made to the other document, the apparatus being operable in a computer system having a processor, means controlled by the application progr~un for selecting a portion of the first document and a display for displaying portions of the first and the second documents, the apparatus comprising: (a) means responsive to a selection of a first document portion for constructing a first anchor object having data identifying the selected first document portion; (b) means responsive to a selection of the first document portion for constructing a second anchor object having data identifying a portion of the second document to be selected; (c) means responsive to the construction of the second anchor object for creating a link object having methods for streaming data between the first and the second anchor objects; (d) means controlled by the first anchor object for creating a command object having methods for modifying documents and for applying the command object methods to the selected first document portion; (e) means in the first anchor object for providing the command object to the link object in order to stream the command object from the first anchor object to the second anchor object; (f) means responsive to the streamed command object for selecting a portion of the second document; and (g) means responsive to the selection of the second document portion for applying the command object methods to the selected second document portion.
In accordance with another aspect of the present invention there is provided a method for dynamically linking a first document to a second document under control of an application program so that changes made in one document are made to the other document, the method being operable in a computer system having a processor, means controlled by the application program for selecting a portion of the first document and a display for displaying portions of the first and the second documents, the method comprising the steps o~ (a) constructing a first anchor object having data identifying the selected first document portion; (b) constructing a second anchor object associated with the second document; (c) creating a link object having methods for streaming data between the first and the second anchor objects; (d) creating a command object having ..,r,y, .. 215535 7 -2a-methods for modifying documents and applying the command object methods to the selected first document portion; (e) using the link object to stream the command object from the first anchor object to the second anchor object; (f) receiving the command object in the second anchor object and selecting a portion of the second document based on the command object; and (g) applying the command object methods to the selected second document portion identified in the second anchor object.
Brief Description of the Drawings Figure 1 is a block diagram of a personal computer system in accordance with a preferred embodiment;
Figure 2 is an illustration of a document display with a selected area and an anchor in accordance with a preferred embodiment;
Figure 3 is a flowchart presenting the processing that transpires in accordance with a preferred embodiment;
Figure 4 is an illustration of a document display illustrating two documents with their corresponding anchors;
Figure 5 is an illustration of a document display when a first command has been executed on a first document in accordance with a preferred embodiment; and Figure 6 is an illustration of a document display when a first command has been executed on a second anchored document in accordance with a preferred embodiment.
Detailed Description of the Invention The invention is preferably practiced in the context of an operating system resident on a personal computer such as the IBM ~ PS/2 ~ or Apple ~ Macintosh computer. A representative hardware environment is depicted in Figure l, which illustrates a typical hardware configuration of a workstation in accordance with the subject invention having a central processing unit 10, such as a conventional microprocessor, with a built in non-volatile storage 11, and a number of other units interconnected via a system bus 12. The workstation shown in Figure 1 includes a Random Access Memory (RAM) 14, Read Only Memory (ROM) 16, an I/O adapter 18 for connecting peripheral devices such as a disk unit 20, and a diskette unit 21 to the bus, a user interface adapter 22 for connecting a keyboard 24, a mouse 26, a speaker 28, a microphone 32, and/or other user interface devices such as a touch screen device (not shown) to the bus, a communication adapter 34 for connecting the workstation to a data processing network 23 and a display adapter 36 for connecting the bus to a display device 38. The workstation has resident thereon an operating system such as the Apple System/? ~ operating system.
WO 95/03574 PCTI(TS94/00099 215 5 3 5 a _3_ In a preferred embodiment, the invention is implemented in the C++
programming language using object oriented programming techniques. As will be understood by those skilled in the art, Object-Oriented Programming (OOP) objects are software entities comprising data structures and operations on the data.
Together, these elements enable objects to model virtually any real-world entity in terms of its characteristics, represented by its data elements, and its behavior, represented by its data manipulation functions. In this way, objects can model concrete things like people and computers, and they can model abstract concepts like numbers or geometrical concepts. The benefits of object technology arise out of three basic principles: encapsulation, polymorphism and inheritance.
Objects hide, or encapsulate, the internal structure of their data and the algorithms by which their functions work. Instead of exposing these implementation details, objects present interfaces that represent their abstractions cleanly with no extraneous information. Polymorphism takes encapsulation a step further. The idea is many shapes, one interface. A software component can make a request of another component without knowing exactly what that component is.
The component that receives the request interprets it and figures out according to its variables and data, how to execute the request. The third principle is inheritance, which allows developers to reuse pre-existing design and code. This capability allows developers to avoid creating software from scratch. Rather, through inheritance, developers derive subclasses that inherit behaviors, which the developer then customizes to meet their particular needs.
A prior art approach is to layer objects and class libraries in a procedural environment. Many application frameworks on the market take this design approach. In this design, there are one or more object layers on top of a monolithic operating system. While this approach utilizes all the principles of encapsulation, polymorphism, and inheritance in the object layer, and is a substantial improvement over procedural programming techniques, there are limitations to this approach. These difficulties arise from the fact that while it is easy for a developer to reuse their own objects, it is difficult to use objects from other systems and the developer still needs to reach into the lower non-object layers with procedural Operating System (OS) calls.
Another aspect of object oriented programming is a framework approach to application development. One of the most rational definitions of frameworks come from Ralph E. Johnson of the University of Illinois and Vincent F. Russo of Purdue.
In their 1991 paper, Reusing Object-Oriented Designs, University of Illinois tech report UIUCDCS91-1696 they offer the following definition: "An abstract class is a design of a set of objects that collaborate to carry out a set of responsibilities. Thus, a framework is a set of object classes that collaborate to execute defined sets of WO 95/03574 ~ ~ ~ ~ PCT/US94/00099 computing responsibilities." From a programming standpoint, frameworks are essentially groups of interconnected object classes that provide a pre-fabricated structure of a working application. For example, a user interface framework might provide the support and "default" behavior of drawing windows, scrollbars, menus, etc. Since frameworks are based on object technology, this behavior can be inherited and overridden to allow developers to extend the framework and create customized solutions in a particular area of expertise. This is a major advantage over traditional programming since the programmer is not changing the original code, but rather extending the software. In addition, developers are not blindly working through layers of code because the framework provides architectural guidance and modeling but at the same time frees them to then supply the specific actions unique to the problem domain.
From a business perspective, frameworks can be viewed as a way to encapsulate or embody expertise in a particular knowledge area. Corporate development organizations, Independent Software Vendors (ISV)s and systems integrators have acquired expertise in particular areas, such as manufacturing, accounting, or currency transactions. This expertise is embodied in their code.
Frameworks allow these development organizations to capture and package the common characteristics of that expertise by embodying it in the organization's code.
First, this allows developers to create or extend an application that utilizes the expertise, thus the problem gets solved once and the business rules and design are enforced and used consistently. Also, frameworks and the embodied expertise behind the frameworks have a strategic asset implication for those organizations who have acquired expertise in vertical markets such as manufacturing, accounting, or bio-technology would have a distribution mechanism for packaging, reselling, and deploying their expertise, and furthering the progress and dissemination of technology.
Historically, frameworks have only recently emerged as a mainstream concept on personal computing platforms. This migration has been assisted by the availability of object-oriented languages, such as C++. Traditionally, C++ was found mostly on UNIX systems and researcher's workstations, rather than on Personal Computers in commercial settings. It is languages such as C++ and other object-oriented languages, such as Smalltalk and others, that enabled a number of university and research projects to produce the precursors to today's commercial frameworks and class libraries. Some examples of these are Interviews from Stanford University, the Andrew toolkit from Carnegie-Mellon University and University of Zurich's ET++ framework.
There are many kinds of frameworks depending on what level of the system you are concerned with and what kind of problem you are trying to solve. The WO 95103574 ~ 1 ~ 3 ~ 7 PCT/US94/00099 types~of frameworks range from application frameworks that assist in developing the user interface, to lower level frameworks that provide basic system software services such as communications, printing, file systems support, graphics, etc.
Commercial examples of application frameworks are MacApp (Apple), Bedrock (Symantec), OWL (Borland), NeXTStep App Kit (NeXT), and Smalltalk-80 MVC
(ParcPlace) to name a few.
Programming with frameworks requires a new way of thinking for developers accustomed to other kinds of systems. In fact, it is not like "programming" at all in the traditional sense. In old-style operating systems such as DOS or UNIX, the developer's own program provides all of the structure. The operating system provides services through system calls-the developer's program makes the calls when it needs the service and control returns when the service has been provided. The program structure is based on the flow-of-control, which is embodied in the code the developer writes.
When frameworks are used, this is reversed. The developer is no longer responsible for the flow-of-control. The developer must forego the tendency to understand programming tasks in term of flow of execution. Rather, the thinking must be in terms of the responsibilities of the objects, which must rely on the framework to determine when the tasks should execute. Routines written by the developer are activated by code the developer did not write and that the developer never even sees. This flip-flop in control flow can be a significant psychological barrier for developers experienced only in procedural programming. Once this is understood, however, framework programming requires much less work than other types of programming.
In the same way that an application framework provides the developer with prefab functionality, system frameworks, such as those included in a preferred embodiment, leverage the same concept by providing system level services, which developers, such as system programmers, use to subclass/override to create customized solutions. For example, consider a multi-media framework which could provide the foundation for supporting new and diverse devices such as audio, video, MIDI, animation, etc. The developer that needed to support a new kind of device would have to write a device driver. To do this with a framework, the developer only needs to supply the characteristics and behavior that is specific to that new device.
The developer in this case supplies an implementation for certain member functions that will be called by the mufti-media framework. An immediate benefit to the developer is that the generic code needed for each category of device is already provided by the mufti-media framework. This means less code for the device driver developer to write, test, and debug. Another example of using system WO 95/03574 ~ 3 ~ ~ PCT/US94100099 framework would be to have separate I/O frameworks for SCSI devices, NuBus cards, and graphics devices. Because there is inherited functionality, each framework provides support for common functionality found in its device category.
Other developers could then depend on these consistent interfaces to all kinds of devices.
A preferred embodiment takes the concept of frameworks and applies it throughout the entire system. For the commercial or corporate developer, systems integrator, or OEM, this means all the advantages that have been illustrated for a framework such as MacApp can be leveraged not only at the application level for such things as text and user interfaces, but also at the system level, for services such as graphics, multi-media, file systems, I/O, testing, etc.
Application creation in the architecture of a preferred embodiment will essentially be like writing domain-specific puzzle pieces that adhere to the framework protocol. In this manner, the whole concept of programming changes.
Instead of writing line after line of code that calls multiple API
hierarchies, software will be developed by deriving classes from the preexisting frameworks within this environment, and then adding new behavior and/or overriding inherited behavior as desired.
Thus, the developer's application becomes the collection of code that is written and shared with all the other framework applications. This is a powerful concept because developers will be able to build on each other's work. This also provides the developer the flexibility to customize as much or as little as needed.
Some frameworks will be used just as they are. In some cases, the amount of customization will be minimal, so the puzzle piece the developer plugs in will be small. In other cases, the developer may make very extensive modifications and create something completely new. In a preferred embodiment, as shown in Figure 1, a program resident in the RAM 14, and under the control of the CPU 10, is responsible for managing various tasks using an object oriented document framework.
Overview of Synchronization Links The system's document architecture provides the technology for linking. One part of this architecture includes the presentation and commands for general purpose data-oriented links. The linking architecture will also be used to implement other features that may not resemble the general purpose data linking human interface, such as annotation. In addition, third party developers may use the linking architecture to implement special capabilities in their own applications, like a calendar, or a classic hypertext environment.
_,_ A synchronization link enables the same information to be seen in more than one location. The frequency and direction that the two pieces of information are updated with each other can be controlled at either end of the link. A
link anchor is the special visual indication of the extent of the linked data in a document.
Creating Links Creating a synchronization link is very similar to cut/copy and paste. To initiate a link, a user selects some data, using whatever means necessary and appropriate for the data type. Using the menu commands, the user would copy the selection. Then, in the desired destination, the user selects a command from a menu item and selects another command from the ensuing dialog box. Something can be copied, then pasted as a link later or more than once, even after the source document is closed. When the original source document is reopened, it will show the link anchor where the source data was copied from.
A direct manipulation method would be to choose a special drag-with-link tool to drag the selection to the new location. Holding down the option and command keys would be a shortcut for getting into this tool. This adds together the semantic of the other two modifier keys - the option key for copy and the command key for reference link. The modifier keys, therefore, are a shortcut for getting into a tool. The Link Preferences menu item is available after a selection was pasted (or option dragged) and is still selected. Then, a user could copy and paste something in the normal manner, then while the pasted information was still selected, turn the link on to facilitate application of the command to another document.
Deleting Deleting a link that only receives information would be just like deleting any other object. The source object would at some point be informed that the receiver no longer exists. Deleting a link that sends out information may require an alert to notify the user that deleting the link will affect parts of other documents.
When a document is opened, a notification indicates that the sending link no longer exists.
When a link source is deleted, it's receiving links will be embedded or absorbed data.
Editing data A user interacts with linked data as they would with any other embedded or absorbed data. When linked data is selected, the anchor showing the extent of the link and commands pertaining to the linking capabilities are available in the menus. Depending on the privileges of the document and the properties of the link, the user may be able to fully edit and make changes, or may be restricted to WO 95/03574 5 3 ~ ~ PCT/US94/00099 _g_ only making selections in the data. When linked data is editable at either end, changes made in one end appear at the other end, in accord with how frequently the link is set to be updated.
When a link's information flows only from one end to the other, the data on the receiving end is not editable, but it is selectable. Words and sentences can be selected inside a paragraph of linked text, for example. A document's privileges can also affect the editability of a link within that document. Linked information may be selectable but uneditable in a locked document. Selections containing links retain their links when copied and pasted. For example, copying and pasting a word from a linked sentence will copy and paste the link as well. Paste Special would allow the data to be pasted without the link. Linked extents can contain links, and overlap with other linked areas.
How much the information can be changed in one end of the link without affecting the other end of the link is dependent on the implementation of that type of data. It is possible that through the use of styles users can make local changes to linked data.
Following the link The other end of the link can be found by getting preferences ("Get info" or "Link info" menu items) on the link. A preferences panel contains an actual reference link to the other end. Or at the very least, it could contain a button labeled "Open source", "Open destination", "Open other end", or a list of the other ends of the link if there are more than one.
Updating frequency and direction A newly created synchronization link will be created with certain default properties. A new link will push data on demand from the user, and a single direction - from the source to the destination. It will not be editable in the destination. These settings were chosen because they are safe and understandable.
Changes to the data flow only in the direction that the link was created -from where the link originated to the new location. Changes to the data will only happen when the user requests them to happen. The user must explicitly turn on the options to have changes to the data flow both directions, or update more frequently.
Preferences for the link can change any of these settings at either end of the link. The preference panel can be accessed whenever the link anchor is visible. A
preference panel for a selected link will contain the following information and commands:
~ History of the link: created in..., goes to..., last updated on...
WO 95/03574 1 5 3 5 ~ PCTlUS94100099 ~ Update when: (default: none selected) - on close - on open - on date & time - on frequency ~ Open Source/Destination/Other end document ~ Unlink ~ Update now ~ Allow editing in destination (two way link) Changes to the data can be "pushed" out to the other end of the link. If the document containing the other end of the link is open, it will receive notification that new information is available. If the receiving document is closed at the time, it will get the notification and the new information when it is opened. A link can also "pull" data from the other end of the link. This can happen regardless of whether the document containing the other end is open or closed. If nothing has changed in the other end, the data received may not visibly change.
A preferred embodiment creates dynamic anchors, which can be analogized to a sticky selection or a synchronized linkage. Selections are used to select a range (contiguous or discontiguous) of text or spreadsheet cells or a particular graphic in a draw document. An example of a selection is presented in Figure 2 at 210. An anchor is a selection that is valid over time and enables the recall of the selection through some other means. Usually there is a marker 220 associated with the selection. A user can click on the marker to make the selection current again.
A
link in a preferred embodiment is a connection between two anchors. An example of a dynamic anchor operation occurs when two selections and two supported operations push data across a link and pull data on the link. A unique characteristic of a preferred embodiment is the ability to support a dynamic location rather then a fixed location for the link.
For example, if a user has two word processing documents, A and B, and an anchor is attached to a paragraph in document A and a corresponding paragraph in document B has another anchor attached to it, then data can be passed back and forth between the two documents using push and pull commands. The interesting thing about dynamic anchors is that the destination is unbound until the tune that the link is activated. Rather than binding to a specific selection in a document, a dynamic binding can transpire. For example, a spelling checker can be dynamically bound to a document to select the first misspelled word in the document.
Alternatively, by binding a spreadsheet, the largest value in the spreadsheet could be selected. Basically, the dynamic anchor allows a run time computation to occur to determine the actual, specific physical data you are linked to.
WO 95/03574 ~ 5 3 5 7 PCTIiJS94/00099 Given a prior art linkage model in which everything in the model has been selected, and a link attached to it, then when additions are made to the model, the linkage does not include the newly added data, it only includes what was selected initially. With the dynamic, whole model anchor of a preferred embodiment, all data of the model is included, no matter how much was added later. The anchor is computed at the moment data is requested. Then, if more data is added to the model, it computes a different range for the anchor then would have been active initially. A copy of the data in a model is retrieved when a copy operation is performed from the clipboard. Then, a publish link operation is performed to the dynamic anchor that represents all the data in that model, and whenever a paste of clipboard data is requested, a query of the link is performed to pull the data across the link. This architecture exploits the implementation of dynamic anchors and enhances the ability to pull information across anchors and links to implement a clipboard. No special code is necessary beyond what is used by normal pushing and pulling data across a link.
Figure 3 is a flowchart presenting the processing that transpires in accordance with a preferred embodiment. Processing commences at terminal 300 and immediately passes to function block 310 where the first and second objects are opened. The obects could be text documents, graphic images, spreadsheets or other computer applications. Then, at function block 320, an anchor location is created in the two objects. The anchor merely marks a selection area and abstractly specifies an action. The action is resolved at follow or lookup time. Function block 330 illustrates the creation processing for the follow command on the start side.
This processing selects the location of the link and creates the follow command at the start side of the document. While this example has both the start side and dest side in two different documents, one of ordinary skill in the art will recognize that the two anchors could reside in the same document. Then, at function block 340, the command is sent to the dest side to the other document's anchor. The send operation entails querying the linkage as shown in function block 350, setting the selection equal to the anchor, and scrolling the position of the anchor into view as set forth in function block 360. Then, the command applied at the start side is applied at the dest side as shown in function block 370. Finally, processing is completed at terminal 380.
Figure 4 is an illustration of a document display illustrating two documents with their corresponding anchors. The two anchors appear at 410 and 420 as dashed lines around the selected area. As described above, the anchor in the source document 410 allows a command executed on the source document to be applied to the anchored destination document. Figure 5 is an illustration of a document WO 95/03574 ~ ~ 5 5 3 5 7 PCT/US94/00099 display when a first command has been executed on a first document in accordance with a preferred embodiment. The command in this case is an update of the sales numbers appearing in the anchored area 500.
Figure 6 is an illustration of a document display when a first command has been executed on a second anchored document in accordance with a preferred embodiment. In Figure 6, the source document has had a command applied to the anchored area at 600. The anchored area reflects the same changes as were made on the source document. Alternatively, in Figure 6, the largest value in the spreadsheet could be selected from the dynamic anchor at 600. Basically, the dynamic anchor allows a run time computation to occur to determine the actual, specific physical data of interest to a user.
ANCHOR Program Listing C++ language /MAbstractModelAnchor/
class MAbstractModelAnchor : public MCollectible {
public:
virtual ~MAbstractModelAnchor();
virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator=(TStream&
fromwhere);
virtual long Hash() const;
virtual Boolean IsEqual(const MCollectible*) const;
virtual void PrintMe() const;
VersionDeclarationsMacro(MAbstractModelAnchor);
TGlobalID GetUniqueID() const;
virtual void SetUniqueID(const TGlobalID&);
virtual TModelSurrogate* CopyModelSurrogate() const = 0;
virtual const TModelSurrogate* GetModelSurrogate() const = 0;
virtual void SetModel(const TAbstractModel&) = 0;
WO 95/03574 ~ ~ 3 ~ ~' PCT/L1S94/00099 protected:
MAbstractModelAnchor(const MAbstractModelAnchor&);
MAbstractModelAnchor();
MAbstractModelAnchor& operator=(const MAbstractModelAnchor&);
private:
TGlobalID fUniqueID;
static const VersionInfo kOriginalVersion;
); -/*-*/
/*TModelAnchorSurrogate*/
class TModelAnchorSurrogate : public MAbstractModelAnchor {
public:
TModelAnchorSurrogate(const TModelAnchorSurrogate&);
TModelAnchorSurrogate(const MAbstractModelAnchor&);
TModelAnchorSurrogate();
virtual ~TModelAnchorSurrogate();
TModelAnchorSurrogate& operator=(const TModelAnchorSurrogate&);
TModelAnchorSurrogate& operator=(const MAbstractModelAnchor&);
virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator=(TStream&
fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TModelAnchorSurrogate);
virtual TModelSurrogate* CopyModelSurrogate() const;
virtual const TModelSurrogate* GetModelSurrogate() const;
virtual void SetModel(const TAbstractModel&);
/ / Check if surrogate is for valid anchor.
virtual Boolean IsValid() const;
virtual TModelAnchor* GetAnchor() const;
/ / Data exchange virtual void _ CreatePreferredTypeList(TSequence& theTypes) const;
virtual TTypeDescription*
ChoosePreferredType(const TSequence& theChoices, ETypeAcceptKind&) const;
virtual TModel*
CopyDataAndAnchors(const TTypeDescription& theType) const;
/ / Constants static const TModelAnchorSurrogate& kInvalidAnchor;
private:
TModelSurrogateStreamer fModel;
static const VersionInfo kOriginalVersion;
);
/ *-*/
/*TModelAnchor*/
class TModelAnchor : public MAbstractModelAnchor, public TModelSelection public:
TModelAnchor(const TAbstractModel&, const TTime& modifydate );
TModelAnchor(const TModelSelection&, const TTime& modifydate);
TModelAnchor(const TModelAnchor&);
WO 95/03574 ' PCT/fJS94/00099 ~'~55~5T
TModelAnchor();
TModelAnchor& operator=(const TModelAnchor&);
virtual ~TModelAnchor();
virtual Boolean IsEqual(const MCollectible*) const;
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator=(TStream& fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TModelAnchor);
virtual void _ Touch();
virtual void GetModifyDate(TTime&
theDate) const;
virtual void SetModifyDate(const TTime&
theDate);
virtual void SetSelection(const TModelSelection& theSelection);
virtual void AdoptSelection(TModelSelection* theSelection);
virtual const TModelSelection* GetSelection() const;
virtual void Follow(const TModelLinkSurrogate& theLink);
virtual void Execute(const TModelLinkSurrogate& theLink, TModelCommand& theCommand);
/ / TModelSelection overrides virtual TModelAnchor* CreateAnchor() const;
virtual Boolean IsAnchorable() const;
virtual Boolean IsReadable() const;
virtual Boolean IsWriteable() const;
virtual Boolean IsClearable() const;
virtual void SetModel(const TAbstractModel& theModel);
virtual TModelSurrogate* CopyModelSurrogate() const;
virtual const TModelSurrogate* GetModelSurrogate() const;
WO 95/03574 ~ 1 5 3 5 7 PCTIUS94/00099 virtual void SetPresentation(const TPresentation& thePresentation);
virtual void SetPresentation(const TPresentationSurrogate& thePresentation);
virtual void CreatePreferredTypeList(TSequence& theTypes) const;
virtual TTypeDescription* ChoosePreferredType(const TSequence& theChoices, ETypeAcceptKind&) const;
virtual TModel* CopyDataAndAnchors() const;
virtual TModel*
CopyDataAndAnchors(const TTypeDescription& theType) const;
virtual TModel*
AbsorbDataAndAnchors(TModel* theData, TModelSelection*& theNewSelectionIfDifferent);
virtual TModel*
AbsorbDataAndAnchorsForUndoRedo(TModel* theData);
virtual TModel*
EmbedDataAndAnchors(TModel* theData, TModelSelection*& theNewSelectionIfDifferent);
virtual TModel*
ClearDataAndAnchors(TModelSelection*& theNewSelectionIfDifferent);
virtual TModel*
ClearDataAndAnchorsForUndoRedo();
virtual TModel*
ImportDataAndAnchors(TModel*) const;
virtual Boolean IsA(const TToken& theType) const;
virtual Boolean IsValid() const;
virtual void SetValid(Boolean isValid = TRUE);
virtual Boolean IsEmpty() const;
virtual void AddAnchor(const MAbstractModelAnchor& anAnchor);
virtual void RemoveAnchor(const MAbstractModelAnchor& anAnchor);
virtual void RemoveAllAnchors();
virtual TIterator* CreateAnchorIterator() const;
virtual void WO 95/03574 ~ ~ ~ ~ ~ PCT/US94/00099 AddModel(const TAbstractModel& aModel);
virtual void RemoveModel(const TAbstractModel& aModel);
virtual void RemoveAllModels();
virtual TIterator* CreateModelIterator() const;
virtual TIterator* CreateSelectionIterator() const;
virtual TModelSelection*
CopyAndExtendToStart() const;
virtual TModelSelection*
CopyAndExtendToEnd() const;
/ / Anchor attributes virtual void AddAttribute(const TAttribute& theAttribute);
virtual void DeleteAttribute(const TAttribute& theName);
virtual const TAttribute*
LookupAttribute(const TAttribute& theName) const;
virtual void DeleteAllAttributes();
virtual TIterator* CreateAttributeIterator() const;
/ / Links virtual void AdoptLink(TModelLink*
aLink);
virtual TModelLink*
OrphanLink(const TAbstractModelLink& aLink);
virtual TModelLink*
LookupLink(const TModelLinkSurrogate& aLink);
virtual void DeleteAllLinks();
virtual TIterator*
CreateLinkIterator() const;
virtual void SetVisibility(Boolean visible =
TRUE);
virtual Boolean GetVisibility() const;
virtual Boolean IsDynamic() const;
private:
TTime fModifyStamp;
TModelSelection* fSelection;
TSimpleAttributeGroup* fAttributes;
TDeque fLinks;
Boolean fVisible;
static const Versionlnfo kOriginalVersion;
#ifndef NO_INTERNAL
public:
virtual void FinalizeAfterLookup();
#endif };
/ *-* /
/*TDynamicAnchor*/
class TDynamicAnchor : public TModelAnchor {
public:
virtual ~TDynamicAnchor();
virtual TStream& operator=(TStream& towhere) const;
virtual TStream& operator=(TStream& fromwhere);
virtual void PrintMe() const;
VersionDeclarationsMacro(TDynamicAnchor);
/ / TModelAnchor overrides virtual void SetVisibility(Boolean);
virtual Boolean GetVisibility() const;
virtual Boolean IsDynamic() const;
virtual void FinalizeAfterLookup();
protected:
TDynamicAnchor(const TAbstractModel&, const TGlobalID&);
TDynamicAnchor(const TDynamicAnchor&);
TDynamicAnchor();
WO 95/03574 5 ~ PCT/(JS94100099 TDynamicAnchor& operator=(const TDynamicAnchor&);
virtual TModelSelection* CreateDynamicSelection() const = 0;
private:
static const VersionInfo kOriginalVersion;
);
/*-*/
/ *TCurrentSelectionAnchor*/
class TCurrentSelectionAnchor : public TDynamicAnchor {
public:
TCurrentSelectionAnchor(const TAbstractModel&);
TCurrentSelectionAnchor(const TCurrentSelectionAnchor&);
TCurrentSelectionAnchor& operator=(const TCurrentSelectionAnchor&);
virtual ~TCurrentSelectionAnchor();
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator«=(TStream& fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TCurrentSelectionAnchor);
protected:
TCurrentSelectionAnchor();
virtual TModelSelection* CreateDynamicSelection() const;
private:
static const VersionInfo kOriginalVersion;
}:
/*-'~/
/ *TWholeModelAnchor* /
WO 95/03574 ~ ~ ~ ~ ~ ~ PCT/US94/00099 class TWholeModelAnchor : public TDynamicAnchor {
public:
TWholeModelAnchor(const TAbstractModel&);
TWholeModelAnchor(const TWholeModelAnchor&);
TWholeModelAnchor& operator=(const TWholeModelAnchor&);
virtual ~TWholeModelAnchor();
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& _ operator«=(TStream& fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TWholeModelAnchor);
protected:
TWholeModelAnchor();
virtual TModelSelection* CreateDynamicSelection() const;
private:
static const VersionInfo kOriginalVersion;
);
/*-*/
/*TAbstractModelLink*/
class TAbstractModelLink : public MCollectible {
public:
virtual ~TAbstractModelLink();
TGlobalID GetUniqueID() const;
virtual void SetUniqueID(const TGlobalID&);
const TModelAnchorSurrogate* GetHere() const;
const TModelAnchorSurrogate* GetThere() const;
WO 95/03574 2 1 5 5 3 5 ~ PCTIUS94/00099 VersionDeclarationsMacro(TAbstractModelLink);
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator«=(TStream& fromwhere);
virtual long Hash() const;
virtual Boolean IsEqual(const MCollectible*) const;
virtual void PrintMe() const;
protected:
TAbstractModelLink();
TAbstractModelLink(const TAbstractModelLink&);
TAbstractModelLink(const TModelAnchorSurrogate& here, const TModelAnchorSurrogate& there);
TAbstractModelLink& operator=(const TAbstractModelLink&);
private:
TGlobalID fUniqueID;
TModelAnchorSurrogate fHere;
TModelAnchorSurrogate fThere;
static const VersionInfo kOriginalVersion;
};
/*-*/
/*TModelLinkSurrogate*/
class TModelLinkSurrogate : public TAbstractModelLink {
public:
TModelLinkSurrogate(const TModelLinkSurrogate&);
TModelLinkSurrogate(const TAbstractModelLink&);
TModelLinkSurrogate();
virtual TModelLinkSurrogate();
TModelLinkSurrogate& operator=(const TModelLinkSurrogate&);
TModelLinkSurrogate& operator=(const TAbstractModelLink&);
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator=(TStream& fromwhere);
MCollectibleDeclarationsMacro(TModelLinkSurrogate);
/ / Check if surrogate is for valid link.
virtual Boolean IsValid() const;
/ / Constants static const TModelLinkSurrogate& kInvalidLink;
static const VersionInfo kOriginalVersion;
);
/ *-* /
/*TModelLink*/
class TModelLink : public TAbstractModelLink public:
TModelLink(const TModelAnchorSurrogate& here, const TModelAnchorSurrogate& there);
TModelLink(const TModelLink&);
TModelLink();
virtual ~TModelLink();
TModelLink& operator=(const TModelLink&);
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator«=(TStream& fromwhere);
MCollectibleDeclarationsMacro(TModelLink);
/ / Link attributes virtual void AddAttribute(const TAttribute& theAttribute);
WO 95103574 5 3 ~ ~ PCT/US94/00099 virtual void DeleteAttribute(const TAttribute& theName);
virtual const TAttribute* LookupAttribute(const TAttribute&
theName) const;
virtual void DeleteAllAttributes();
virtual TIterator* CreateAttributeIterator() const;
virtual Boolean IsBidirectional() const;
virtual void SetBidirectional(Boolean =
TRUE);
private:
TSimpleAttributeGxoup* fAttributes;
Boolean fBidirectional;
static const VersionInfo kOriginalVersion;
J;
/~ */
/*TModelAnchorCollection*/
/ / TModelAnchorCollection provides the abstract protocol for a collection of model anchors.
/ / This protocol is used by TModel to manage its list of anchors and links.
This class is / / abstract and may be subclassed to provide a specific implementation.
TModelAnchorCollections / / own their anchors and are responsible all associated memory management.
class TModelAnchorCollection : public MCollectible public:
/ *
...............................................................................
..........* /
/* Constructors and Destructors*/ ' TModelAnchorCollection();
TModelAnchorCollection( const TModelAnchorCollection& );
WO 95/03574 2 1 5 5 3 5 7 ' PCT/US94/00099 virtual ~TModelAnchorCollection();
TModelAnchorCollection& operator=(coast TModelAnchorCollection&);
/ *
...............................................................................
..........* /
/* Cwerrides*/
virtual TStream& operator»= ( TStream&
towhere ) coast;
virtual TStream& operator«= ( TStream&
fromwhere ); _ VersionDeclarationsMacro(TModelAnchorCollection);
/*
...............................................................................
..........*/
/* Collection methods*/
virtual void Adopt( TModelAnchor* anAnchor ) = 0;
virtual TModelAnchor*Orphan( coast MAbstractModelAnchor& ) = 0;
virtual TModelAnchor*Member( coast MAbstractModelAnchor& ) coast = 0;
virtual unsigned long Count(;) coast = 0;
virtual TIterator*CreateIterator(Boolean includeInvisibleAnchors, Boolean includeDynamicAnchors) coast = 0;
virtual void AnchorsFixedUp() = 0;
private:
static coast Versionlnfo kOriginalVersion;
};
/*-*/
/*TModelAnchorSet*/
/ / TModelAnchorSet is a concrete subclass of TModelAnchorCollection that implements the / / anchor collection using a TSet.
class TModelAnchorSet : public TModelAnchorCollection public:
WO 95103574 5 ~ J 5 ~ ' PCTIUS94100099 /* ..........................................................*/
/* Constructors and Destructors*/
TModelAnchorSet();
TModelAnchorSet( const TModelAnchorSet& );
virtual ~TModelAnchorSet();
TModelAnchorSet& operator=(const TModelAnchorSet&);
/*
............................................................................*/
/ * Overrides* /
virtual TStream& operator»= ( TStream& towhere ) const;
virtual TStream& operator«= ( TStream& fromwhere );
MCollectibleDeclarationsMacro(TModelAnchorSet);
/ *
...............................................................................
..........* /
/* Collection methods*/
virtual void Adopt( TModelAnchor* anAnchor );
virtual TModelAnchor* Orphan( const MAbstractModelAnchor& );
virtual TModelAnchor* Member( const MAbstractModelAnchor& ) const;
virtual unsigned long Count() const;
virtual TIterator* CreateIterator(Boolean includeInvisibleAnchors, Boolean includeDynamicAnchors) const;
virtual void AnchorsFixedUp();
private:
TSet fAnchors;
static const VersionInfo kOriginalVersion;
};
/*-*/
/ *TAnchorNotification* /
class TAnchorNotification : public TNotification 3 5 7 a-25-public:
TAnchorNotification(const TInterest& theInterest, const MAbstractModelAnchor& theAnchor);
TAnchorNotification(const TAnchorNotification&);
virtual ~TAnchorNotification();
TAnchorNotification& operator=(const TAnchorNotification&); _ virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator«=(TStream&
towhere);
MCollectibleDeclarationsMacro(TAnchorNotification);
virtual const TModelAnchorSurrogate&
GetAnchorSurrogate() const;
protected:
TAnchorNotification();
private:
TModelAnchorSurrogate fAnchor;
static const VersionInfo kOriginalVersion;
};
*/
/*TModelLinkNotification*/
class TModelLinkNotification : public TNotification public:
TModelLinkNotification(const TInterest& theInterest, WO 95103574 5 ~ 5 ~ ' PCT/US94100099 const TAbstractModelLink& theAnchor);
TModelLinkNotification(const TModelLinkNotification&);
virtual TModelLinkNotification();
TModelLinkNotification& operator=(const TModelLinkNotification&);
virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator«=(TStream&
towhere); _ MCollectibleDeclarationsMacro(TModelLinkNotification);
virtual const TModelLinkSurrogate&
GetModelLinkSurrogate() const;
protected:
TModelLinkNotification();
private:
TModelLinkSurrogate fLink;
static const VersionInfo kOriginalVersion;
);
/* */
AAd~t~ED ShE
B~NAMIC LINKING SYSTEM
Copyright Notification This patent application contains copyrighted material the reproduction of which is permitted only as part of the patent application for its informative purposes.
All other rights, in particular the right of a commercial exploitation of such material, are reserved.
Field of the Invention This invention generally relates to improvements in computer systems and more particularly to a system and method for linking operations and areas of information between documents.
Background of the Invention Document processing is currently the most prey alent application of personal computer technology. Examples of state of the art word processing technology include the WordPerfect ~ text processor and the Word text processor from Microsoft ~ Corporation. These products are designed to run on various operating systems and different hardware platforms. It would be convenient to share information between applications resident on a single hardware platform.
This capability has been hard coded into some applications establishing an automatic update of business chart data by editing a graphic chart as illustrated in US Patent 4,b74,043. Other examples of linking a saved file to another document are found in Microsoft Wir~dows, Version 3.I, "User's Guide," pp. 487-514 which describes a cold link capability. On pages 494-495 of the document the procedures for creating a link between a saved document and another document are described. In the described system, changes to the linked document that are saved on a disk will be reflected in the document that contains the link.
C ~...._.
~.~.L'e,: ~J .
-lA-However, dynamic anchoring of information in ~ first document and exchanging updates based on actions ta~en in a second document, in accordance with the subject invention, is not possible in today's word processing environment Summary of the Invention Accordingly, it is a primary objective of the present invention to provide a system and method for selecting a location in a fist document, selecting a location in a second document, performing an action on the second document and automatically performing the identical action on the first document at the defined location. An alternative embodiment links a first abject to a second object and performs an action, such as launching an application of the second object, and performs an action, such as launching an application of the second object, and remembering the location where the document was last accessed. Another embodiment, termed the whole model embodiment, provides an anchor to an entire object. The anchor enables an action to be applied to the whole object. For example, to copy data from a clipboard object, the copy command is directed to the whole object anchor of the clipboard object. Still another embodiment provides an anchor representative of the first misspelled word or highest value in a document or a spreadsheet.
In accordance with one aspect of the present invention there is provided an apparatus for dynamically linking a first document to a second document under control of an application program so that changes made in one document are made to the other document, the apparatus being operable in a computer system having a processor, means controlled by the application progr~un for selecting a portion of the first document and a display for displaying portions of the first and the second documents, the apparatus comprising: (a) means responsive to a selection of a first document portion for constructing a first anchor object having data identifying the selected first document portion; (b) means responsive to a selection of the first document portion for constructing a second anchor object having data identifying a portion of the second document to be selected; (c) means responsive to the construction of the second anchor object for creating a link object having methods for streaming data between the first and the second anchor objects; (d) means controlled by the first anchor object for creating a command object having methods for modifying documents and for applying the command object methods to the selected first document portion; (e) means in the first anchor object for providing the command object to the link object in order to stream the command object from the first anchor object to the second anchor object; (f) means responsive to the streamed command object for selecting a portion of the second document; and (g) means responsive to the selection of the second document portion for applying the command object methods to the selected second document portion.
In accordance with another aspect of the present invention there is provided a method for dynamically linking a first document to a second document under control of an application program so that changes made in one document are made to the other document, the method being operable in a computer system having a processor, means controlled by the application program for selecting a portion of the first document and a display for displaying portions of the first and the second documents, the method comprising the steps o~ (a) constructing a first anchor object having data identifying the selected first document portion; (b) constructing a second anchor object associated with the second document; (c) creating a link object having methods for streaming data between the first and the second anchor objects; (d) creating a command object having ..,r,y, .. 215535 7 -2a-methods for modifying documents and applying the command object methods to the selected first document portion; (e) using the link object to stream the command object from the first anchor object to the second anchor object; (f) receiving the command object in the second anchor object and selecting a portion of the second document based on the command object; and (g) applying the command object methods to the selected second document portion identified in the second anchor object.
Brief Description of the Drawings Figure 1 is a block diagram of a personal computer system in accordance with a preferred embodiment;
Figure 2 is an illustration of a document display with a selected area and an anchor in accordance with a preferred embodiment;
Figure 3 is a flowchart presenting the processing that transpires in accordance with a preferred embodiment;
Figure 4 is an illustration of a document display illustrating two documents with their corresponding anchors;
Figure 5 is an illustration of a document display when a first command has been executed on a first document in accordance with a preferred embodiment; and Figure 6 is an illustration of a document display when a first command has been executed on a second anchored document in accordance with a preferred embodiment.
Detailed Description of the Invention The invention is preferably practiced in the context of an operating system resident on a personal computer such as the IBM ~ PS/2 ~ or Apple ~ Macintosh computer. A representative hardware environment is depicted in Figure l, which illustrates a typical hardware configuration of a workstation in accordance with the subject invention having a central processing unit 10, such as a conventional microprocessor, with a built in non-volatile storage 11, and a number of other units interconnected via a system bus 12. The workstation shown in Figure 1 includes a Random Access Memory (RAM) 14, Read Only Memory (ROM) 16, an I/O adapter 18 for connecting peripheral devices such as a disk unit 20, and a diskette unit 21 to the bus, a user interface adapter 22 for connecting a keyboard 24, a mouse 26, a speaker 28, a microphone 32, and/or other user interface devices such as a touch screen device (not shown) to the bus, a communication adapter 34 for connecting the workstation to a data processing network 23 and a display adapter 36 for connecting the bus to a display device 38. The workstation has resident thereon an operating system such as the Apple System/? ~ operating system.
WO 95/03574 PCTI(TS94/00099 215 5 3 5 a _3_ In a preferred embodiment, the invention is implemented in the C++
programming language using object oriented programming techniques. As will be understood by those skilled in the art, Object-Oriented Programming (OOP) objects are software entities comprising data structures and operations on the data.
Together, these elements enable objects to model virtually any real-world entity in terms of its characteristics, represented by its data elements, and its behavior, represented by its data manipulation functions. In this way, objects can model concrete things like people and computers, and they can model abstract concepts like numbers or geometrical concepts. The benefits of object technology arise out of three basic principles: encapsulation, polymorphism and inheritance.
Objects hide, or encapsulate, the internal structure of their data and the algorithms by which their functions work. Instead of exposing these implementation details, objects present interfaces that represent their abstractions cleanly with no extraneous information. Polymorphism takes encapsulation a step further. The idea is many shapes, one interface. A software component can make a request of another component without knowing exactly what that component is.
The component that receives the request interprets it and figures out according to its variables and data, how to execute the request. The third principle is inheritance, which allows developers to reuse pre-existing design and code. This capability allows developers to avoid creating software from scratch. Rather, through inheritance, developers derive subclasses that inherit behaviors, which the developer then customizes to meet their particular needs.
A prior art approach is to layer objects and class libraries in a procedural environment. Many application frameworks on the market take this design approach. In this design, there are one or more object layers on top of a monolithic operating system. While this approach utilizes all the principles of encapsulation, polymorphism, and inheritance in the object layer, and is a substantial improvement over procedural programming techniques, there are limitations to this approach. These difficulties arise from the fact that while it is easy for a developer to reuse their own objects, it is difficult to use objects from other systems and the developer still needs to reach into the lower non-object layers with procedural Operating System (OS) calls.
Another aspect of object oriented programming is a framework approach to application development. One of the most rational definitions of frameworks come from Ralph E. Johnson of the University of Illinois and Vincent F. Russo of Purdue.
In their 1991 paper, Reusing Object-Oriented Designs, University of Illinois tech report UIUCDCS91-1696 they offer the following definition: "An abstract class is a design of a set of objects that collaborate to carry out a set of responsibilities. Thus, a framework is a set of object classes that collaborate to execute defined sets of WO 95/03574 ~ ~ ~ ~ PCT/US94/00099 computing responsibilities." From a programming standpoint, frameworks are essentially groups of interconnected object classes that provide a pre-fabricated structure of a working application. For example, a user interface framework might provide the support and "default" behavior of drawing windows, scrollbars, menus, etc. Since frameworks are based on object technology, this behavior can be inherited and overridden to allow developers to extend the framework and create customized solutions in a particular area of expertise. This is a major advantage over traditional programming since the programmer is not changing the original code, but rather extending the software. In addition, developers are not blindly working through layers of code because the framework provides architectural guidance and modeling but at the same time frees them to then supply the specific actions unique to the problem domain.
From a business perspective, frameworks can be viewed as a way to encapsulate or embody expertise in a particular knowledge area. Corporate development organizations, Independent Software Vendors (ISV)s and systems integrators have acquired expertise in particular areas, such as manufacturing, accounting, or currency transactions. This expertise is embodied in their code.
Frameworks allow these development organizations to capture and package the common characteristics of that expertise by embodying it in the organization's code.
First, this allows developers to create or extend an application that utilizes the expertise, thus the problem gets solved once and the business rules and design are enforced and used consistently. Also, frameworks and the embodied expertise behind the frameworks have a strategic asset implication for those organizations who have acquired expertise in vertical markets such as manufacturing, accounting, or bio-technology would have a distribution mechanism for packaging, reselling, and deploying their expertise, and furthering the progress and dissemination of technology.
Historically, frameworks have only recently emerged as a mainstream concept on personal computing platforms. This migration has been assisted by the availability of object-oriented languages, such as C++. Traditionally, C++ was found mostly on UNIX systems and researcher's workstations, rather than on Personal Computers in commercial settings. It is languages such as C++ and other object-oriented languages, such as Smalltalk and others, that enabled a number of university and research projects to produce the precursors to today's commercial frameworks and class libraries. Some examples of these are Interviews from Stanford University, the Andrew toolkit from Carnegie-Mellon University and University of Zurich's ET++ framework.
There are many kinds of frameworks depending on what level of the system you are concerned with and what kind of problem you are trying to solve. The WO 95103574 ~ 1 ~ 3 ~ 7 PCT/US94/00099 types~of frameworks range from application frameworks that assist in developing the user interface, to lower level frameworks that provide basic system software services such as communications, printing, file systems support, graphics, etc.
Commercial examples of application frameworks are MacApp (Apple), Bedrock (Symantec), OWL (Borland), NeXTStep App Kit (NeXT), and Smalltalk-80 MVC
(ParcPlace) to name a few.
Programming with frameworks requires a new way of thinking for developers accustomed to other kinds of systems. In fact, it is not like "programming" at all in the traditional sense. In old-style operating systems such as DOS or UNIX, the developer's own program provides all of the structure. The operating system provides services through system calls-the developer's program makes the calls when it needs the service and control returns when the service has been provided. The program structure is based on the flow-of-control, which is embodied in the code the developer writes.
When frameworks are used, this is reversed. The developer is no longer responsible for the flow-of-control. The developer must forego the tendency to understand programming tasks in term of flow of execution. Rather, the thinking must be in terms of the responsibilities of the objects, which must rely on the framework to determine when the tasks should execute. Routines written by the developer are activated by code the developer did not write and that the developer never even sees. This flip-flop in control flow can be a significant psychological barrier for developers experienced only in procedural programming. Once this is understood, however, framework programming requires much less work than other types of programming.
In the same way that an application framework provides the developer with prefab functionality, system frameworks, such as those included in a preferred embodiment, leverage the same concept by providing system level services, which developers, such as system programmers, use to subclass/override to create customized solutions. For example, consider a multi-media framework which could provide the foundation for supporting new and diverse devices such as audio, video, MIDI, animation, etc. The developer that needed to support a new kind of device would have to write a device driver. To do this with a framework, the developer only needs to supply the characteristics and behavior that is specific to that new device.
The developer in this case supplies an implementation for certain member functions that will be called by the mufti-media framework. An immediate benefit to the developer is that the generic code needed for each category of device is already provided by the mufti-media framework. This means less code for the device driver developer to write, test, and debug. Another example of using system WO 95/03574 ~ 3 ~ ~ PCT/US94100099 framework would be to have separate I/O frameworks for SCSI devices, NuBus cards, and graphics devices. Because there is inherited functionality, each framework provides support for common functionality found in its device category.
Other developers could then depend on these consistent interfaces to all kinds of devices.
A preferred embodiment takes the concept of frameworks and applies it throughout the entire system. For the commercial or corporate developer, systems integrator, or OEM, this means all the advantages that have been illustrated for a framework such as MacApp can be leveraged not only at the application level for such things as text and user interfaces, but also at the system level, for services such as graphics, multi-media, file systems, I/O, testing, etc.
Application creation in the architecture of a preferred embodiment will essentially be like writing domain-specific puzzle pieces that adhere to the framework protocol. In this manner, the whole concept of programming changes.
Instead of writing line after line of code that calls multiple API
hierarchies, software will be developed by deriving classes from the preexisting frameworks within this environment, and then adding new behavior and/or overriding inherited behavior as desired.
Thus, the developer's application becomes the collection of code that is written and shared with all the other framework applications. This is a powerful concept because developers will be able to build on each other's work. This also provides the developer the flexibility to customize as much or as little as needed.
Some frameworks will be used just as they are. In some cases, the amount of customization will be minimal, so the puzzle piece the developer plugs in will be small. In other cases, the developer may make very extensive modifications and create something completely new. In a preferred embodiment, as shown in Figure 1, a program resident in the RAM 14, and under the control of the CPU 10, is responsible for managing various tasks using an object oriented document framework.
Overview of Synchronization Links The system's document architecture provides the technology for linking. One part of this architecture includes the presentation and commands for general purpose data-oriented links. The linking architecture will also be used to implement other features that may not resemble the general purpose data linking human interface, such as annotation. In addition, third party developers may use the linking architecture to implement special capabilities in their own applications, like a calendar, or a classic hypertext environment.
_,_ A synchronization link enables the same information to be seen in more than one location. The frequency and direction that the two pieces of information are updated with each other can be controlled at either end of the link. A
link anchor is the special visual indication of the extent of the linked data in a document.
Creating Links Creating a synchronization link is very similar to cut/copy and paste. To initiate a link, a user selects some data, using whatever means necessary and appropriate for the data type. Using the menu commands, the user would copy the selection. Then, in the desired destination, the user selects a command from a menu item and selects another command from the ensuing dialog box. Something can be copied, then pasted as a link later or more than once, even after the source document is closed. When the original source document is reopened, it will show the link anchor where the source data was copied from.
A direct manipulation method would be to choose a special drag-with-link tool to drag the selection to the new location. Holding down the option and command keys would be a shortcut for getting into this tool. This adds together the semantic of the other two modifier keys - the option key for copy and the command key for reference link. The modifier keys, therefore, are a shortcut for getting into a tool. The Link Preferences menu item is available after a selection was pasted (or option dragged) and is still selected. Then, a user could copy and paste something in the normal manner, then while the pasted information was still selected, turn the link on to facilitate application of the command to another document.
Deleting Deleting a link that only receives information would be just like deleting any other object. The source object would at some point be informed that the receiver no longer exists. Deleting a link that sends out information may require an alert to notify the user that deleting the link will affect parts of other documents.
When a document is opened, a notification indicates that the sending link no longer exists.
When a link source is deleted, it's receiving links will be embedded or absorbed data.
Editing data A user interacts with linked data as they would with any other embedded or absorbed data. When linked data is selected, the anchor showing the extent of the link and commands pertaining to the linking capabilities are available in the menus. Depending on the privileges of the document and the properties of the link, the user may be able to fully edit and make changes, or may be restricted to WO 95/03574 5 3 ~ ~ PCT/US94/00099 _g_ only making selections in the data. When linked data is editable at either end, changes made in one end appear at the other end, in accord with how frequently the link is set to be updated.
When a link's information flows only from one end to the other, the data on the receiving end is not editable, but it is selectable. Words and sentences can be selected inside a paragraph of linked text, for example. A document's privileges can also affect the editability of a link within that document. Linked information may be selectable but uneditable in a locked document. Selections containing links retain their links when copied and pasted. For example, copying and pasting a word from a linked sentence will copy and paste the link as well. Paste Special would allow the data to be pasted without the link. Linked extents can contain links, and overlap with other linked areas.
How much the information can be changed in one end of the link without affecting the other end of the link is dependent on the implementation of that type of data. It is possible that through the use of styles users can make local changes to linked data.
Following the link The other end of the link can be found by getting preferences ("Get info" or "Link info" menu items) on the link. A preferences panel contains an actual reference link to the other end. Or at the very least, it could contain a button labeled "Open source", "Open destination", "Open other end", or a list of the other ends of the link if there are more than one.
Updating frequency and direction A newly created synchronization link will be created with certain default properties. A new link will push data on demand from the user, and a single direction - from the source to the destination. It will not be editable in the destination. These settings were chosen because they are safe and understandable.
Changes to the data flow only in the direction that the link was created -from where the link originated to the new location. Changes to the data will only happen when the user requests them to happen. The user must explicitly turn on the options to have changes to the data flow both directions, or update more frequently.
Preferences for the link can change any of these settings at either end of the link. The preference panel can be accessed whenever the link anchor is visible. A
preference panel for a selected link will contain the following information and commands:
~ History of the link: created in..., goes to..., last updated on...
WO 95/03574 1 5 3 5 ~ PCTlUS94100099 ~ Update when: (default: none selected) - on close - on open - on date & time - on frequency ~ Open Source/Destination/Other end document ~ Unlink ~ Update now ~ Allow editing in destination (two way link) Changes to the data can be "pushed" out to the other end of the link. If the document containing the other end of the link is open, it will receive notification that new information is available. If the receiving document is closed at the time, it will get the notification and the new information when it is opened. A link can also "pull" data from the other end of the link. This can happen regardless of whether the document containing the other end is open or closed. If nothing has changed in the other end, the data received may not visibly change.
A preferred embodiment creates dynamic anchors, which can be analogized to a sticky selection or a synchronized linkage. Selections are used to select a range (contiguous or discontiguous) of text or spreadsheet cells or a particular graphic in a draw document. An example of a selection is presented in Figure 2 at 210. An anchor is a selection that is valid over time and enables the recall of the selection through some other means. Usually there is a marker 220 associated with the selection. A user can click on the marker to make the selection current again.
A
link in a preferred embodiment is a connection between two anchors. An example of a dynamic anchor operation occurs when two selections and two supported operations push data across a link and pull data on the link. A unique characteristic of a preferred embodiment is the ability to support a dynamic location rather then a fixed location for the link.
For example, if a user has two word processing documents, A and B, and an anchor is attached to a paragraph in document A and a corresponding paragraph in document B has another anchor attached to it, then data can be passed back and forth between the two documents using push and pull commands. The interesting thing about dynamic anchors is that the destination is unbound until the tune that the link is activated. Rather than binding to a specific selection in a document, a dynamic binding can transpire. For example, a spelling checker can be dynamically bound to a document to select the first misspelled word in the document.
Alternatively, by binding a spreadsheet, the largest value in the spreadsheet could be selected. Basically, the dynamic anchor allows a run time computation to occur to determine the actual, specific physical data you are linked to.
WO 95/03574 ~ 5 3 5 7 PCTIiJS94/00099 Given a prior art linkage model in which everything in the model has been selected, and a link attached to it, then when additions are made to the model, the linkage does not include the newly added data, it only includes what was selected initially. With the dynamic, whole model anchor of a preferred embodiment, all data of the model is included, no matter how much was added later. The anchor is computed at the moment data is requested. Then, if more data is added to the model, it computes a different range for the anchor then would have been active initially. A copy of the data in a model is retrieved when a copy operation is performed from the clipboard. Then, a publish link operation is performed to the dynamic anchor that represents all the data in that model, and whenever a paste of clipboard data is requested, a query of the link is performed to pull the data across the link. This architecture exploits the implementation of dynamic anchors and enhances the ability to pull information across anchors and links to implement a clipboard. No special code is necessary beyond what is used by normal pushing and pulling data across a link.
Figure 3 is a flowchart presenting the processing that transpires in accordance with a preferred embodiment. Processing commences at terminal 300 and immediately passes to function block 310 where the first and second objects are opened. The obects could be text documents, graphic images, spreadsheets or other computer applications. Then, at function block 320, an anchor location is created in the two objects. The anchor merely marks a selection area and abstractly specifies an action. The action is resolved at follow or lookup time. Function block 330 illustrates the creation processing for the follow command on the start side.
This processing selects the location of the link and creates the follow command at the start side of the document. While this example has both the start side and dest side in two different documents, one of ordinary skill in the art will recognize that the two anchors could reside in the same document. Then, at function block 340, the command is sent to the dest side to the other document's anchor. The send operation entails querying the linkage as shown in function block 350, setting the selection equal to the anchor, and scrolling the position of the anchor into view as set forth in function block 360. Then, the command applied at the start side is applied at the dest side as shown in function block 370. Finally, processing is completed at terminal 380.
Figure 4 is an illustration of a document display illustrating two documents with their corresponding anchors. The two anchors appear at 410 and 420 as dashed lines around the selected area. As described above, the anchor in the source document 410 allows a command executed on the source document to be applied to the anchored destination document. Figure 5 is an illustration of a document WO 95/03574 ~ ~ 5 5 3 5 7 PCT/US94/00099 display when a first command has been executed on a first document in accordance with a preferred embodiment. The command in this case is an update of the sales numbers appearing in the anchored area 500.
Figure 6 is an illustration of a document display when a first command has been executed on a second anchored document in accordance with a preferred embodiment. In Figure 6, the source document has had a command applied to the anchored area at 600. The anchored area reflects the same changes as were made on the source document. Alternatively, in Figure 6, the largest value in the spreadsheet could be selected from the dynamic anchor at 600. Basically, the dynamic anchor allows a run time computation to occur to determine the actual, specific physical data of interest to a user.
ANCHOR Program Listing C++ language /MAbstractModelAnchor/
class MAbstractModelAnchor : public MCollectible {
public:
virtual ~MAbstractModelAnchor();
virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator=(TStream&
fromwhere);
virtual long Hash() const;
virtual Boolean IsEqual(const MCollectible*) const;
virtual void PrintMe() const;
VersionDeclarationsMacro(MAbstractModelAnchor);
TGlobalID GetUniqueID() const;
virtual void SetUniqueID(const TGlobalID&);
virtual TModelSurrogate* CopyModelSurrogate() const = 0;
virtual const TModelSurrogate* GetModelSurrogate() const = 0;
virtual void SetModel(const TAbstractModel&) = 0;
WO 95/03574 ~ ~ 3 ~ ~' PCT/L1S94/00099 protected:
MAbstractModelAnchor(const MAbstractModelAnchor&);
MAbstractModelAnchor();
MAbstractModelAnchor& operator=(const MAbstractModelAnchor&);
private:
TGlobalID fUniqueID;
static const VersionInfo kOriginalVersion;
); -/*-*/
/*TModelAnchorSurrogate*/
class TModelAnchorSurrogate : public MAbstractModelAnchor {
public:
TModelAnchorSurrogate(const TModelAnchorSurrogate&);
TModelAnchorSurrogate(const MAbstractModelAnchor&);
TModelAnchorSurrogate();
virtual ~TModelAnchorSurrogate();
TModelAnchorSurrogate& operator=(const TModelAnchorSurrogate&);
TModelAnchorSurrogate& operator=(const MAbstractModelAnchor&);
virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator=(TStream&
fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TModelAnchorSurrogate);
virtual TModelSurrogate* CopyModelSurrogate() const;
virtual const TModelSurrogate* GetModelSurrogate() const;
virtual void SetModel(const TAbstractModel&);
/ / Check if surrogate is for valid anchor.
virtual Boolean IsValid() const;
virtual TModelAnchor* GetAnchor() const;
/ / Data exchange virtual void _ CreatePreferredTypeList(TSequence& theTypes) const;
virtual TTypeDescription*
ChoosePreferredType(const TSequence& theChoices, ETypeAcceptKind&) const;
virtual TModel*
CopyDataAndAnchors(const TTypeDescription& theType) const;
/ / Constants static const TModelAnchorSurrogate& kInvalidAnchor;
private:
TModelSurrogateStreamer fModel;
static const VersionInfo kOriginalVersion;
);
/ *-*/
/*TModelAnchor*/
class TModelAnchor : public MAbstractModelAnchor, public TModelSelection public:
TModelAnchor(const TAbstractModel&, const TTime& modifydate );
TModelAnchor(const TModelSelection&, const TTime& modifydate);
TModelAnchor(const TModelAnchor&);
WO 95/03574 ' PCT/fJS94/00099 ~'~55~5T
TModelAnchor();
TModelAnchor& operator=(const TModelAnchor&);
virtual ~TModelAnchor();
virtual Boolean IsEqual(const MCollectible*) const;
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator=(TStream& fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TModelAnchor);
virtual void _ Touch();
virtual void GetModifyDate(TTime&
theDate) const;
virtual void SetModifyDate(const TTime&
theDate);
virtual void SetSelection(const TModelSelection& theSelection);
virtual void AdoptSelection(TModelSelection* theSelection);
virtual const TModelSelection* GetSelection() const;
virtual void Follow(const TModelLinkSurrogate& theLink);
virtual void Execute(const TModelLinkSurrogate& theLink, TModelCommand& theCommand);
/ / TModelSelection overrides virtual TModelAnchor* CreateAnchor() const;
virtual Boolean IsAnchorable() const;
virtual Boolean IsReadable() const;
virtual Boolean IsWriteable() const;
virtual Boolean IsClearable() const;
virtual void SetModel(const TAbstractModel& theModel);
virtual TModelSurrogate* CopyModelSurrogate() const;
virtual const TModelSurrogate* GetModelSurrogate() const;
WO 95/03574 ~ 1 5 3 5 7 PCTIUS94/00099 virtual void SetPresentation(const TPresentation& thePresentation);
virtual void SetPresentation(const TPresentationSurrogate& thePresentation);
virtual void CreatePreferredTypeList(TSequence& theTypes) const;
virtual TTypeDescription* ChoosePreferredType(const TSequence& theChoices, ETypeAcceptKind&) const;
virtual TModel* CopyDataAndAnchors() const;
virtual TModel*
CopyDataAndAnchors(const TTypeDescription& theType) const;
virtual TModel*
AbsorbDataAndAnchors(TModel* theData, TModelSelection*& theNewSelectionIfDifferent);
virtual TModel*
AbsorbDataAndAnchorsForUndoRedo(TModel* theData);
virtual TModel*
EmbedDataAndAnchors(TModel* theData, TModelSelection*& theNewSelectionIfDifferent);
virtual TModel*
ClearDataAndAnchors(TModelSelection*& theNewSelectionIfDifferent);
virtual TModel*
ClearDataAndAnchorsForUndoRedo();
virtual TModel*
ImportDataAndAnchors(TModel*) const;
virtual Boolean IsA(const TToken& theType) const;
virtual Boolean IsValid() const;
virtual void SetValid(Boolean isValid = TRUE);
virtual Boolean IsEmpty() const;
virtual void AddAnchor(const MAbstractModelAnchor& anAnchor);
virtual void RemoveAnchor(const MAbstractModelAnchor& anAnchor);
virtual void RemoveAllAnchors();
virtual TIterator* CreateAnchorIterator() const;
virtual void WO 95/03574 ~ ~ ~ ~ ~ PCT/US94/00099 AddModel(const TAbstractModel& aModel);
virtual void RemoveModel(const TAbstractModel& aModel);
virtual void RemoveAllModels();
virtual TIterator* CreateModelIterator() const;
virtual TIterator* CreateSelectionIterator() const;
virtual TModelSelection*
CopyAndExtendToStart() const;
virtual TModelSelection*
CopyAndExtendToEnd() const;
/ / Anchor attributes virtual void AddAttribute(const TAttribute& theAttribute);
virtual void DeleteAttribute(const TAttribute& theName);
virtual const TAttribute*
LookupAttribute(const TAttribute& theName) const;
virtual void DeleteAllAttributes();
virtual TIterator* CreateAttributeIterator() const;
/ / Links virtual void AdoptLink(TModelLink*
aLink);
virtual TModelLink*
OrphanLink(const TAbstractModelLink& aLink);
virtual TModelLink*
LookupLink(const TModelLinkSurrogate& aLink);
virtual void DeleteAllLinks();
virtual TIterator*
CreateLinkIterator() const;
virtual void SetVisibility(Boolean visible =
TRUE);
virtual Boolean GetVisibility() const;
virtual Boolean IsDynamic() const;
private:
TTime fModifyStamp;
TModelSelection* fSelection;
TSimpleAttributeGroup* fAttributes;
TDeque fLinks;
Boolean fVisible;
static const Versionlnfo kOriginalVersion;
#ifndef NO_INTERNAL
public:
virtual void FinalizeAfterLookup();
#endif };
/ *-* /
/*TDynamicAnchor*/
class TDynamicAnchor : public TModelAnchor {
public:
virtual ~TDynamicAnchor();
virtual TStream& operator=(TStream& towhere) const;
virtual TStream& operator=(TStream& fromwhere);
virtual void PrintMe() const;
VersionDeclarationsMacro(TDynamicAnchor);
/ / TModelAnchor overrides virtual void SetVisibility(Boolean);
virtual Boolean GetVisibility() const;
virtual Boolean IsDynamic() const;
virtual void FinalizeAfterLookup();
protected:
TDynamicAnchor(const TAbstractModel&, const TGlobalID&);
TDynamicAnchor(const TDynamicAnchor&);
TDynamicAnchor();
WO 95/03574 5 ~ PCT/(JS94100099 TDynamicAnchor& operator=(const TDynamicAnchor&);
virtual TModelSelection* CreateDynamicSelection() const = 0;
private:
static const VersionInfo kOriginalVersion;
);
/*-*/
/ *TCurrentSelectionAnchor*/
class TCurrentSelectionAnchor : public TDynamicAnchor {
public:
TCurrentSelectionAnchor(const TAbstractModel&);
TCurrentSelectionAnchor(const TCurrentSelectionAnchor&);
TCurrentSelectionAnchor& operator=(const TCurrentSelectionAnchor&);
virtual ~TCurrentSelectionAnchor();
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator«=(TStream& fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TCurrentSelectionAnchor);
protected:
TCurrentSelectionAnchor();
virtual TModelSelection* CreateDynamicSelection() const;
private:
static const VersionInfo kOriginalVersion;
}:
/*-'~/
/ *TWholeModelAnchor* /
WO 95/03574 ~ ~ ~ ~ ~ ~ PCT/US94/00099 class TWholeModelAnchor : public TDynamicAnchor {
public:
TWholeModelAnchor(const TAbstractModel&);
TWholeModelAnchor(const TWholeModelAnchor&);
TWholeModelAnchor& operator=(const TWholeModelAnchor&);
virtual ~TWholeModelAnchor();
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& _ operator«=(TStream& fromwhere);
virtual void PrintMe() const;
MCollectibleDeclarationsMacro(TWholeModelAnchor);
protected:
TWholeModelAnchor();
virtual TModelSelection* CreateDynamicSelection() const;
private:
static const VersionInfo kOriginalVersion;
);
/*-*/
/*TAbstractModelLink*/
class TAbstractModelLink : public MCollectible {
public:
virtual ~TAbstractModelLink();
TGlobalID GetUniqueID() const;
virtual void SetUniqueID(const TGlobalID&);
const TModelAnchorSurrogate* GetHere() const;
const TModelAnchorSurrogate* GetThere() const;
WO 95/03574 2 1 5 5 3 5 ~ PCTIUS94/00099 VersionDeclarationsMacro(TAbstractModelLink);
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator«=(TStream& fromwhere);
virtual long Hash() const;
virtual Boolean IsEqual(const MCollectible*) const;
virtual void PrintMe() const;
protected:
TAbstractModelLink();
TAbstractModelLink(const TAbstractModelLink&);
TAbstractModelLink(const TModelAnchorSurrogate& here, const TModelAnchorSurrogate& there);
TAbstractModelLink& operator=(const TAbstractModelLink&);
private:
TGlobalID fUniqueID;
TModelAnchorSurrogate fHere;
TModelAnchorSurrogate fThere;
static const VersionInfo kOriginalVersion;
};
/*-*/
/*TModelLinkSurrogate*/
class TModelLinkSurrogate : public TAbstractModelLink {
public:
TModelLinkSurrogate(const TModelLinkSurrogate&);
TModelLinkSurrogate(const TAbstractModelLink&);
TModelLinkSurrogate();
virtual TModelLinkSurrogate();
TModelLinkSurrogate& operator=(const TModelLinkSurrogate&);
TModelLinkSurrogate& operator=(const TAbstractModelLink&);
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator=(TStream& fromwhere);
MCollectibleDeclarationsMacro(TModelLinkSurrogate);
/ / Check if surrogate is for valid link.
virtual Boolean IsValid() const;
/ / Constants static const TModelLinkSurrogate& kInvalidLink;
static const VersionInfo kOriginalVersion;
);
/ *-* /
/*TModelLink*/
class TModelLink : public TAbstractModelLink public:
TModelLink(const TModelAnchorSurrogate& here, const TModelAnchorSurrogate& there);
TModelLink(const TModelLink&);
TModelLink();
virtual ~TModelLink();
TModelLink& operator=(const TModelLink&);
virtual TStream& operator»=(TStream& towhere) const;
virtual TStream& operator«=(TStream& fromwhere);
MCollectibleDeclarationsMacro(TModelLink);
/ / Link attributes virtual void AddAttribute(const TAttribute& theAttribute);
WO 95103574 5 3 ~ ~ PCT/US94/00099 virtual void DeleteAttribute(const TAttribute& theName);
virtual const TAttribute* LookupAttribute(const TAttribute&
theName) const;
virtual void DeleteAllAttributes();
virtual TIterator* CreateAttributeIterator() const;
virtual Boolean IsBidirectional() const;
virtual void SetBidirectional(Boolean =
TRUE);
private:
TSimpleAttributeGxoup* fAttributes;
Boolean fBidirectional;
static const VersionInfo kOriginalVersion;
J;
/~ */
/*TModelAnchorCollection*/
/ / TModelAnchorCollection provides the abstract protocol for a collection of model anchors.
/ / This protocol is used by TModel to manage its list of anchors and links.
This class is / / abstract and may be subclassed to provide a specific implementation.
TModelAnchorCollections / / own their anchors and are responsible all associated memory management.
class TModelAnchorCollection : public MCollectible public:
/ *
...............................................................................
..........* /
/* Constructors and Destructors*/ ' TModelAnchorCollection();
TModelAnchorCollection( const TModelAnchorCollection& );
WO 95/03574 2 1 5 5 3 5 7 ' PCT/US94/00099 virtual ~TModelAnchorCollection();
TModelAnchorCollection& operator=(coast TModelAnchorCollection&);
/ *
...............................................................................
..........* /
/* Cwerrides*/
virtual TStream& operator»= ( TStream&
towhere ) coast;
virtual TStream& operator«= ( TStream&
fromwhere ); _ VersionDeclarationsMacro(TModelAnchorCollection);
/*
...............................................................................
..........*/
/* Collection methods*/
virtual void Adopt( TModelAnchor* anAnchor ) = 0;
virtual TModelAnchor*Orphan( coast MAbstractModelAnchor& ) = 0;
virtual TModelAnchor*Member( coast MAbstractModelAnchor& ) coast = 0;
virtual unsigned long Count(;) coast = 0;
virtual TIterator*CreateIterator(Boolean includeInvisibleAnchors, Boolean includeDynamicAnchors) coast = 0;
virtual void AnchorsFixedUp() = 0;
private:
static coast Versionlnfo kOriginalVersion;
};
/*-*/
/*TModelAnchorSet*/
/ / TModelAnchorSet is a concrete subclass of TModelAnchorCollection that implements the / / anchor collection using a TSet.
class TModelAnchorSet : public TModelAnchorCollection public:
WO 95103574 5 ~ J 5 ~ ' PCTIUS94100099 /* ..........................................................*/
/* Constructors and Destructors*/
TModelAnchorSet();
TModelAnchorSet( const TModelAnchorSet& );
virtual ~TModelAnchorSet();
TModelAnchorSet& operator=(const TModelAnchorSet&);
/*
............................................................................*/
/ * Overrides* /
virtual TStream& operator»= ( TStream& towhere ) const;
virtual TStream& operator«= ( TStream& fromwhere );
MCollectibleDeclarationsMacro(TModelAnchorSet);
/ *
...............................................................................
..........* /
/* Collection methods*/
virtual void Adopt( TModelAnchor* anAnchor );
virtual TModelAnchor* Orphan( const MAbstractModelAnchor& );
virtual TModelAnchor* Member( const MAbstractModelAnchor& ) const;
virtual unsigned long Count() const;
virtual TIterator* CreateIterator(Boolean includeInvisibleAnchors, Boolean includeDynamicAnchors) const;
virtual void AnchorsFixedUp();
private:
TSet fAnchors;
static const VersionInfo kOriginalVersion;
};
/*-*/
/ *TAnchorNotification* /
class TAnchorNotification : public TNotification 3 5 7 a-25-public:
TAnchorNotification(const TInterest& theInterest, const MAbstractModelAnchor& theAnchor);
TAnchorNotification(const TAnchorNotification&);
virtual ~TAnchorNotification();
TAnchorNotification& operator=(const TAnchorNotification&); _ virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator«=(TStream&
towhere);
MCollectibleDeclarationsMacro(TAnchorNotification);
virtual const TModelAnchorSurrogate&
GetAnchorSurrogate() const;
protected:
TAnchorNotification();
private:
TModelAnchorSurrogate fAnchor;
static const VersionInfo kOriginalVersion;
};
*/
/*TModelLinkNotification*/
class TModelLinkNotification : public TNotification public:
TModelLinkNotification(const TInterest& theInterest, WO 95103574 5 ~ 5 ~ ' PCT/US94100099 const TAbstractModelLink& theAnchor);
TModelLinkNotification(const TModelLinkNotification&);
virtual TModelLinkNotification();
TModelLinkNotification& operator=(const TModelLinkNotification&);
virtual TStream& operator»=(TStream&
towhere) const;
virtual TStream& operator«=(TStream&
towhere); _ MCollectibleDeclarationsMacro(TModelLinkNotification);
virtual const TModelLinkSurrogate&
GetModelLinkSurrogate() const;
protected:
TModelLinkNotification();
private:
TModelLinkSurrogate fLink;
static const VersionInfo kOriginalVersion;
);
/* */
Claims (22)
1. An apparatus for dynamically linking a first document to a second document under control of an application program so that changes made in one document are made to the other document, the apparatus being operable in a computer system having a processor, means controlled by the application program for selecting a portion of the first document and a display for displaying portions of the first and the second documents, the apparatus comprising:
(a) means responsive to a selection of a first document portion for constructing a first anchor object having data identifying the selected first document portion;
(b) means responsive to a selection of the first document portion for constructing a second anchor object having data identifying a portion of the second document to be selected;
(c) means responsive to the construction of the second anchor object for creating a link object having methods for streaming data between the first and the second anchor objects;
(d) means controlled by the first anchor object for creating a command object having methods for modifying documents and for applying the command object methods to the selected first document portion;
(e) means in the first anchor object for providing the command object to the link object in order to stream the command object from the first anchor object to the second anchor object;
(f) means responsive to the streamed command object for selecting a portion of the second document; and (g) means responsive to the selection of the second document portion for applying the command object methods to the selected second document portion.
(a) means responsive to a selection of a first document portion for constructing a first anchor object having data identifying the selected first document portion;
(b) means responsive to a selection of the first document portion for constructing a second anchor object having data identifying a portion of the second document to be selected;
(c) means responsive to the construction of the second anchor object for creating a link object having methods for streaming data between the first and the second anchor objects;
(d) means controlled by the first anchor object for creating a command object having methods for modifying documents and for applying the command object methods to the selected first document portion;
(e) means in the first anchor object for providing the command object to the link object in order to stream the command object from the first anchor object to the second anchor object;
(f) means responsive to the streamed command object for selecting a portion of the second document; and (g) means responsive to the selection of the second document portion for applying the command object methods to the selected second document portion.
2. An apparatus as recited in claim 1 further comprising:
(h) means controlled by the second anchor object for creating a second command object having methods for modifying documents and for applying the command object methods to the selected second document portion;
(i) means in the second anchor object for providing the second command object to the link object in order to stream the command object from the second anchor object to the first anchor object; and (j) means responsive to the streamed command object for applying the command object methods to the selected first document portion.
(h) means controlled by the second anchor object for creating a second command object having methods for modifying documents and for applying the command object methods to the selected second document portion;
(i) means in the second anchor object for providing the second command object to the link object in order to stream the command object from the second anchor object to the first anchor object; and (j) means responsive to the streamed command object for applying the command object methods to the selected first document portion.
3. An apparatus as recited in claim 1 wherein the means for providing the command object to the link object comprises means for periodically streaming a command object from the first anchor to the second anchor in order to periodically update the selected second document portion.
4. An apparatus as recited in claim 1 wherein the first anchor object comprises means for streaming a pull command object from the first anchor object to the second anchor object and means in the second anchor object responsive to the pull command object for returning data from the second anchor object to the first anchor object.
5. An apparatus as recited in claim 1 wherein the second anchor object comprises means responsive to a command object for displaying the second document on the display.
6. An apparatus as recited in claim 5 wherein the second anchor object comprises means responsive to a command object for displaying the selected second document portion on the display.
7. An apparatus as recited in claim 1 wherein the first anchor object comprises means for streaming a query command object from the first anchor object to the second anchor object and means in the second anchor object responsive to the query command object for examining the second document and for selecting a portion of the second document based on the query command.
8. An apparatus as recited in claim 1 wherein the second anchor object comprises data identifying a point in the second document at which data will be selected.
9. An apparatus as recited in claim 8 wherein the means for selecting a portion of the second document comprises means responsive to the streamed command object for determining the extent of the portion of the second document which is selected.
10. An apparatus as recited in claim 1 wherein the means for selecting a portion of the second document comprises means responsive to the streamed command for identifying a point in the second document at which data will be selected.
11. An apparatus as recited in claim 10 wherein the means for selecting a portion of the second document comprises means responsive to the streamed command object for determining the extent of the portion of the second document which is selected.
12. A method for dynamically linking a first document to a second document under control of an application program so that changes made in one document are made to the other document, the method being operable in a computer system having a processor, means controlled by the application program for selecting a portion of the first document and a display for displaying portions of the first and the second documents, the method comprising the steps of:
(a) constructing a first anchor object having data identifying the selected first document portion;
(b) constructing a second anchor object associated with the second document;
(c) creating a link object having methods for streaming data between the first and the second anchor objects;
(d) creating a command object having methods for modifying documents and applying the command object methods to the selected first document portion;
(e) using the link object to stream the command object from the first anchor object to the second anchor object;
(f) receiving the command object in the second anchor object and selecting a portion of the second document based on the command object; and (g) applying the command object methods to the selected second document portion identified in the second anchor object.
(a) constructing a first anchor object having data identifying the selected first document portion;
(b) constructing a second anchor object associated with the second document;
(c) creating a link object having methods for streaming data between the first and the second anchor objects;
(d) creating a command object having methods for modifying documents and applying the command object methods to the selected first document portion;
(e) using the link object to stream the command object from the first anchor object to the second anchor object;
(f) receiving the command object in the second anchor object and selecting a portion of the second document based on the command object; and (g) applying the command object methods to the selected second document portion identified in the second anchor object.
13. A method as recited in claim 12 further comprising the steps of:
(h) creating a second command object having methods for modifying documents and applying the command object methods to the selected second document portion;
(i) using the link object to stream the command object from the second anchor object to the first anchor object;
(j) receiving the command object in the first anchor object; and (k) applying the command object methods to the selected first document portion.
(h) creating a second command object having methods for modifying documents and applying the command object methods to the selected second document portion;
(i) using the link object to stream the command object from the second anchor object to the first anchor object;
(j) receiving the command object in the first anchor object; and (k) applying the command object methods to the selected first document portion.
14. A method as recited in claim 12 wherein step (e) comprises the step of:
(el) periodically streaming a command object from the first anchor to the second anchor in order to periodically update the selected second document portion.
(el) periodically streaming a command object from the first anchor to the second anchor in order to periodically update the selected second document portion.
15. A method as recited in claim 12 wherein step (d) comprises the step of:
(dl) creating a pull command object;
step (e) comprises the step of:
(e2) streaming the pull command object from the first anchor object to the second anchor object; and step (g) comprises the step of:
(gl) returning data from the second anchor object to the first anchor object in response to the pull command object.
(dl) creating a pull command object;
step (e) comprises the step of:
(e2) streaming the pull command object from the first anchor object to the second anchor object; and step (g) comprises the step of:
(gl) returning data from the second anchor object to the first anchor object in response to the pull command object.
16. A method as recited in claim 12 wherein step (g) comprises the step of:
(g2) displaying the second document on the display.
(g2) displaying the second document on the display.
17. A method as recited in claim 16 wherein step (g2) comprises the step of:
(g2a) displaying the selected second document portion on the display.
(g2a) displaying the selected second document portion on the display.
18. A method as recited in claim 12 wherein step (d) comprises the step of:
(d2) creating a query command object;
step (e) comprises the step of:
(e3) streaming the query command object from the first anchor object to the second anchor object; and step (g) comprises the step of:
(g3) examining the second document and selecting a portion of the second document in response to the query command object.
(d2) creating a query command object;
step (e) comprises the step of:
(e3) streaming the query command object from the first anchor object to the second anchor object; and step (g) comprises the step of:
(g3) examining the second document and selecting a portion of the second document in response to the query command object.
19. A method as recited in claim 12 wherein step (b) comprises the step of:
(b1) constructing a second anchor object including data identifying a point in the second document at which data will be selected.
(b1) constructing a second anchor object including data identifying a point in the second document at which data will be selected.
20. A method as recited in claim 19 wherein step (f) comprises the step of:
(fl) determining the extent of the portion of the second document which is selected in response to the streamed command object.
(fl) determining the extent of the portion of the second document which is selected in response to the streamed command object.
21. A method as recited in claim 12 wherein step (f) comprises the step of:
(f2) identifying a point in the second document at which data will be selected in response to the streamed command.
(f2) identifying a point in the second document at which data will be selected in response to the streamed command.
22. A method as recited in claim 21 wherein the step (f) comprises the step o~
(f3) determining the extent of the portion of the second document which is selected in response to the streamed command object.
(f3) determining the extent of the portion of the second document which is selected in response to the streamed command object.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US9465793A | 1993-07-19 | 1993-07-19 | |
| US094,657 | 1993-07-19 | ||
| PCT/US1994/000099 WO1995003574A1 (en) | 1993-07-19 | 1994-01-03 | Dynamic linking system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2155357A1 CA2155357A1 (en) | 1995-02-02 |
| CA2155357C true CA2155357C (en) | 2001-12-18 |
Family
ID=22246417
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002155357A Expired - Fee Related CA2155357C (en) | 1993-07-19 | 1994-01-03 | Dynamic linking system |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US5787448A (en) |
| EP (1) | EP0689692B1 (en) |
| JP (1) | JPH09500465A (en) |
| CN (1) | CN1110064A (en) |
| AU (1) | AU5990894A (en) |
| CA (1) | CA2155357C (en) |
| DE (1) | DE69400870T2 (en) |
| WO (1) | WO1995003574A1 (en) |
Families Citing this family (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5537526A (en) * | 1993-11-12 | 1996-07-16 | Taugent, Inc. | Method and apparatus for processing a display document utilizing a system level document framework |
| US5838906A (en) | 1994-10-17 | 1998-11-17 | The Regents Of The University Of California | Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document |
| US5805159A (en) * | 1996-08-22 | 1998-09-08 | International Business Machines Corporation | Mobile client computer interdependent display data fields |
| GB2323192B (en) * | 1996-10-29 | 2001-09-26 | Mitsubishi Electric Corp | Software linking system in information processor |
| US5987454A (en) * | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
| US6910184B1 (en) * | 1997-07-25 | 2005-06-21 | Ricoh Company, Ltd. | Document information management system |
| JPH11110194A (en) * | 1997-10-06 | 1999-04-23 | Toshiba Corp | Connection method to external library function and recording medium in which the connection method is recorded and programmed |
| US6061698A (en) * | 1997-10-22 | 2000-05-09 | International Business Machines Corporation | Merging tagged documents and scripts having dynamic content |
| DE19840000A1 (en) * | 1998-09-02 | 2000-03-09 | Esg Elektroniksystem Und Logis | Process for creating references between files from databases and computer network |
| DE19911653A1 (en) * | 1999-03-16 | 2000-09-21 | Asea Brown Boveri | Method of selective import of data in a tabular estimation/calculation program for design of technical installations |
| US6883176B1 (en) | 1999-12-15 | 2005-04-19 | Gateway, Inc. | Method and apparatus for launching applications based upon electronic program guide data |
| US20040210842A1 (en) * | 2000-05-23 | 2004-10-21 | Jaffer Qamar | Portable computing system for editing and linking text and mathematical expressions |
| JP2002108845A (en) * | 2000-09-26 | 2002-04-12 | Canon Inc | Information processor, its method and computer-readable memory |
| CN1591406A (en) * | 2001-11-09 | 2005-03-09 | 无锡永中科技有限公司 | Integrated multi-purpose data processing system |
| JP4039884B2 (en) * | 2002-05-16 | 2008-01-30 | 株式会社リコー | Information temporary storage management method, information temporary storage management apparatus, image forming apparatus, program, and storage medium |
| DE10304885A1 (en) * | 2003-02-06 | 2004-08-26 | Brandenburgische Technische Universität Cottbus | Method and computer device for automatically processing a system component in a computer operating environment |
| US8402384B2 (en) * | 2004-11-09 | 2013-03-19 | Research In Motion Limited | Dynamic bar oriented user interface |
| US20070130369A1 (en) * | 2005-12-06 | 2007-06-07 | Vasant Nayak | Email and Taskmanaging Software |
| US8261197B2 (en) * | 2006-08-04 | 2012-09-04 | Apple Inc. | Methods and systems for managing to do items or notes or electronic messages |
| US8219920B2 (en) * | 2006-08-04 | 2012-07-10 | Apple Inc. | Methods and systems for managing to do items or notes or electronic messages |
| US8037021B2 (en) * | 2007-06-10 | 2011-10-11 | Apple Inc. | Calendaring techniques and interfaces |
| US8824803B2 (en) * | 2012-08-31 | 2014-09-02 | Ancestry.Com Operations Inc. | Automated field position linking of indexed data to digital images |
| CN106294372B (en) * | 2015-05-15 | 2019-06-25 | 阿里巴巴集团控股有限公司 | Application program page quick access method and the mobile terminal for applying it |
| JP7423953B2 (en) * | 2019-09-20 | 2024-01-30 | 富士フイルムビジネスイノベーション株式会社 | Information processing device and information processing program |
Family Cites Families (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4821220A (en) * | 1986-07-25 | 1989-04-11 | Tektronix, Inc. | System for animating program operation and displaying time-based relationships |
| US4885717A (en) * | 1986-09-25 | 1989-12-05 | Tektronix, Inc. | System for graphically representing operation of object-oriented programs |
| US5142618A (en) * | 1986-11-21 | 1992-08-25 | Hitachi, Ltd. | Window management apparatus for a document creating apparatus |
| US5226161A (en) * | 1987-08-21 | 1993-07-06 | Wang Laboratories, Inc. | Integration of data between typed data structures by mutual direct invocation between data managers corresponding to data types |
| US4891630A (en) * | 1988-04-22 | 1990-01-02 | Friedman Mark B | Computer vision system with improved object orientation technique |
| US4953080A (en) * | 1988-04-25 | 1990-08-28 | Hewlett-Packard Company | Object management facility for maintaining data in a computer system |
| EP0347162A3 (en) * | 1988-06-14 | 1990-09-12 | Tektronix, Inc. | Apparatus and methods for controlling data flow processes by generated instruction sequences |
| US5041992A (en) * | 1988-10-24 | 1991-08-20 | University Of Pittsburgh | Interactive method of developing software interfaces |
| US4975690A (en) * | 1988-11-07 | 1990-12-04 | Ibm Corporation | Method for concurrent data entry and manipulation in multiple applications |
| US5133075A (en) * | 1988-12-19 | 1992-07-21 | Hewlett-Packard Company | Method of monitoring changes in attribute values of object in an object-oriented database |
| US5050090A (en) * | 1989-03-30 | 1991-09-17 | R. J. Reynolds Tobacco Company | Object placement method and apparatus |
| US5157384A (en) * | 1989-04-28 | 1992-10-20 | International Business Machines Corporation | Advanced user interface |
| US5060276A (en) * | 1989-05-31 | 1991-10-22 | At&T Bell Laboratories | Technique for object orientation detection using a feed-forward neural network |
| US5125091A (en) * | 1989-06-08 | 1992-06-23 | Hazox Corporation | Object oriented control of real-time processing |
| US5181162A (en) * | 1989-12-06 | 1993-01-19 | Eastman Kodak Company | Document management and production system |
| US5093914A (en) * | 1989-12-15 | 1992-03-03 | At&T Bell Laboratories | Method of controlling the execution of object-oriented programs |
| US5075848A (en) * | 1989-12-22 | 1991-12-24 | Intel Corporation | Object lifetime control in an object-oriented memory protection mechanism |
| US5151987A (en) * | 1990-10-23 | 1992-09-29 | International Business Machines Corporation | Recovery objects in an object oriented computing environment |
| DE69230842T2 (en) * | 1991-02-15 | 2000-11-09 | Sun Microsystems, Inc. | Method and device for managing extensible connections between application programs |
| US5430836A (en) * | 1991-03-01 | 1995-07-04 | Ast Research, Inc. | Application control module for common user access interface |
| US5119475A (en) * | 1991-03-13 | 1992-06-02 | Schlumberger Technology Corporation | Object-oriented framework for menu definition |
| JPH05225181A (en) * | 1991-03-14 | 1993-09-03 | Nec Corp | Editing device |
| FR2690260B1 (en) * | 1992-04-17 | 1997-01-03 | Bull Sa | USE OF A VERY HIGH LEVEL BIDIRECTIONAL PROTOCOL FOR COMMUNICATION BETWEEN A HYPERMEDIA SYSTEM AND A PLURALITY OF EDITORS. |
| US5396630A (en) * | 1992-10-06 | 1995-03-07 | International Business Machines Corporation | Method and system for object management across process boundries in a data processing system |
| US5412772A (en) * | 1992-10-13 | 1995-05-02 | Novell, Inc. | System for permitting a view of an object or a user interface to be exchanged between operating system environments |
| US5437006A (en) * | 1993-01-27 | 1995-07-25 | Microsoft Corporation | Spreadsheet command/function capability from a dynamic-link library |
| US5559942A (en) * | 1993-05-10 | 1996-09-24 | Apple Computer, Inc. | Method and apparatus for providing a note for an application program |
| US5481666A (en) * | 1993-08-25 | 1996-01-02 | Taligent, Inc. | Object-oriented navigation system |
-
1994
- 1994-01-03 CN CN94190308A patent/CN1110064A/en active Pending
- 1994-01-03 JP JP7505109A patent/JPH09500465A/en active Pending
- 1994-01-03 EP EP94906022A patent/EP0689692B1/en not_active Expired - Lifetime
- 1994-01-03 AU AU59908/94A patent/AU5990894A/en not_active Abandoned
- 1994-01-03 WO PCT/US1994/000099 patent/WO1995003574A1/en active IP Right Grant
- 1994-01-03 CA CA002155357A patent/CA2155357C/en not_active Expired - Fee Related
- 1994-01-03 DE DE69400870T patent/DE69400870T2/en not_active Expired - Lifetime
-
1995
- 1995-12-13 US US08/571,578 patent/US5787448A/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| CN1110064A (en) | 1995-10-11 |
| US5787448A (en) | 1998-07-28 |
| JPH09500465A (en) | 1997-01-14 |
| DE69400870T2 (en) | 1997-05-15 |
| EP0689692A1 (en) | 1996-01-03 |
| WO1995003574A1 (en) | 1995-02-02 |
| DE69400870D1 (en) | 1996-12-12 |
| EP0689692B1 (en) | 1996-11-06 |
| AU5990894A (en) | 1995-02-20 |
| CA2155357A1 (en) | 1995-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2155357C (en) | Dynamic linking system | |
| US5379430A (en) | Object-oriented system locator system | |
| US5396626A (en) | Object-oriented locator system | |
| US5912666A (en) | Object-oriented global cursor tool | |
| US5544302A (en) | Object-oriented framework for creating and using container objects with built-in properties | |
| US5634129A (en) | Object oriented system for representing physical locations | |
| US5781732A (en) | Framework for constructing shared documents that can be collaboratively accessed by multiple users | |
| US5524190A (en) | Command object logging system for restoring documents | |
| US5481666A (en) | Object-oriented navigation system | |
| EP0679278B1 (en) | Object-oriented constructive area system | |
| US5729745A (en) | Methods and apparatus for creating a base class for manipulating external data connections in a computer generated document | |
| US5634057A (en) | Place object display system having place objects selected in response to a user identifier | |
| US5479589A (en) | Object-oriented system for selecting a graphic image on a display | |
| US5848429A (en) | Object-oriented global cursor tool which operates in an incompatible document by embedding a compatible frame in the document | |
| JP4339376B2 (en) | Object-oriented cursor tool |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |