Multi-repository display system using separate presentation, adaptation and access layers

Abstract

In a software object display system, an adaptation layer is used to isolate the presentation layer from expectations of the structure of the software objects displayed. A small set of data can be transferred between the adaptation layer and the presentation layer in order to provide for the display.

Description

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention relates to software systems for providing the display and access to software objects in a computer system.

[0004] 2. State of the Art

[0005] Typically, in a computer system, the files which are available for selection by different applications are displayed in a hierarchical manner. The display is part of a user interface on the file management system of the computer system. The user can select a file to be opened by clicking on a representation of the file, or performing a related operation which issues a command to open the file.

[0006] A difficulty occurs when different types of software objects are accessible. In the past, the user interface has been designed with certain, sometimes hidden, expectations of the software objects to be accessed. Most file access systems assume that the software objects are based on a single model. Typically, the local file system forms the basis for this model, since files are the most common types of software objects. When a new type of software object is introduced, it is often forced into this file system model. Some types of software objects, however, do not have a good conceptual fit with the file system model. For example, in file systems, small portions of the file can be independently accessed and modified. This type of access is not possible for some other types of software objects, such as database objects, or web pages on the Internet. For these objects, the entire software object is replaced when a change is to be made.

[0007] As another example of the differences between types of software objects, file systems are typically based upon containment relationships, where one object can have child, or dependent objects, as well as parent objects. This type of relationship may not apply to other types of objects, such as database records, or web pages, since they are not inherently hierarchical.

[0008] In the past, when a new type of software object is introduced, either the user interface software is modified to recognize and handle the new type of software object, or the new type of software object is forced into an existing model, such as the file system model. Because of hidden links between the file system model and the user interface software, modifying the interface to add a new object type can be difficult.

[0009] It is desired to have an improved system of displaying and accessing software objects that avoid some of the problems of the prior art, and facilitate access to a variety of different types of software objects.

SUMMARY OF THE PRESENT INVENTION

[0010] In accordance with the present invention, an adaptation layer is used to isolate a presentation layer of a user interface from the details of accessing the software objects. For each object to be displayed, a standard set of information is transferred to the presentation layer from the adaptation layer. This information, in one embodiment, includes the type of object (e.g. file, web page, etc.) the name and/or icon of the software object, and an indication of the presence of children objects of the software object. This data is provided by the adaptation layer which can call different access units for the different types of software objects. Thus, if there are three different types of software objects, there will be three different access software units called by the adaptation layer to get the appropriate information about the software object. Each of the access units can obtain a standard set of information from the respective types of software objects in vastly different manners. In a preferred embodiment, the amount of data required to be transferred from the adaptation layer to the presentation layer is relatively minimal. Optional information can also be transferred, including, but not limited to, the date and time of the last modification, and the object size.

[0011] An advantage of the present invention is that new types of software objects can be added without requiring modifications to the presentation layer. The presentation layer can display representations of software objects having vastly different software object types. For example, web pages, databases, file transfer protocol (FTP) objects, and regular file types can be displayed in the same hierarchical structure.

[0012] Another embodiment of the present invention concerns a hierarchical display which allows for the selection of software objects having different heterogeneous types. In one embodiment, such a system is made possible by the use of the adaptation layer. Representations of software objects of different types can be shown in the same display, and viewed and selected by the user. The selection of representations in the hierarchical display call access units to access the software objects. The presentation layer is not burdened with figuring out how to access the different software objets. The presentation layer merely sends an “open software object” signal to the different access units which can access the software objects in their own manner.

[0013] The software objects can be from a variety of different sources and repositories. These different repositories can contain heterogeneous types of objects, which would previously have been considered to be incompatible. For example, the software objects can include file objects, database objects, FTP objects, or internet web objects.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The present invention may be further understood from the following description in conjunction with the appended drawings. In the drawings:

[0015] FIG. 1 is a diagram of a conventional software object display system.

[0016] FIG. 2A is a diagram of a software object display system of the present invention.

[0017] FIG. 2B is a diagram of an alternate embodiment of a software object display system of the present invention.

[0018] FIG. 3 is a diagram illustrating the operation of one embodiment of the software object display system of the present invention.

[0019] FIG. 4 is a diagram illustrating a display for the embodiment of FIG. 3.

[0020] FIG. 5 is a diagram illustrating a display used with the present invention.

[0021] FIG. 6 is a diagram illustrating the selection of different software objects in the display of FIG. 5.

[0022] FIG. 7 is a diagram of a computer system including a computer readable medium suitable for storing a program of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] FIG. 1 illustrates a conventional display system with the presentation layer and software objects. The presentation layer is part of a user interface for the file management system of the computer system. The presentation layer allows the user to select a file or folder to be opened by clicking on a representation of the file or folder. The presentation layer may include application programming interfaces that allow an application program to obtain access to software objects. For instance, the application programming interfaces may provide access to open and save dialog boxes via which the user can select a particular file or other object at a designated location.

[0024] Typically, conventional presentation systems were produced with knowledge of the types of software objects to be used. Conventional presentation systems can be tightly meshed with the details of the expected software object types. Often, the presentation layer expects the software objects to behave as files. The file system model is useful for a variety of different types of software objects, such as sound files, movie files, and text files. The prevalence of the file system model has influenced software designers to force new objects into this model.

[0025] A problem occurs when a new type of software object is introduced that does not easily fit the file system model, such as an Internet web page. Modifying the presentation software to allow display of a web page is quite difficult because the presentation software was written expecting all of the software objects to behave in the same manner as a file.

[0026] FIG. 2A is a diagram illustrating one embodiment of the present invention. In this embodiment, the presentation layer is isolated from the details of the software object access by an adaptation layer. The presentation layer is designed to require only a small amount of pre-specified data to produce the display of the different software objects. The adaptation layer provides the set of required data for each software object. This set includes the name of the software object, icon data for the software object, and the existence of children objects for the software object. The required data set could even be smaller, merely providing the name and the existence of children. The presentation layer is isolated from the details of the software object access. Thus, the presentation layer does not expect the software objects to have specific characteristics, and does not require the software objects themselves to have a particular structure.

[0027] The software objects can be from a variety of different sources and repositories. These different repositories can contain heterogeneous types of objects, which would previously be considered incompatible. For example, the software objects can include file objects, database objects, and internet web objects, including FTP server objects.

[0028] The details of the software object access is provided by the adaptation layer and access units. Certain other types of information can be provided by the adaptation layer to the presentation layer, but is not required. This data can include the file size, and the time and date of the last modification. For some types of objects where this information does not make sense, it need not be transferred to the presentation layer. In a preferred embodiment, the adaptation layer is a “thin” layer of software that uses the access units to obtain the display information. The access units may be unmodified commercially available software.

[0029] The presentation layer also preferably sends signals to the lower levels in a fixed form. Thus, if the user selects a command to open a software object, an “open object” instruction is sent to the lower levels which interpret this instruction to open the software object in its own fashion.

[0030] As shown in FIG. 2A, a variety of different software objects can be simultaneously accessed with the present invention. The different types of objects might be stored on different respective repositories. Thus, file objects might be stored on a local disk drive, FTP objects can be stored at a remote FTP site, and database objects are accessed via a separate database server. Access units for file objects, database objects, and web objects are shown. It is easy to support new types of software objects. The adaptation layer can be changed and additional access units added. Since the presentation layer only expects certain fixed data, the new object types can be added without modifying the presentation layer.

[0031] In a preferred embodiment, the presentation layer does not require the identifying data to be returned within a fixed time period. With a file system, when data is requested by the presentation unit, the computer system can quickly obtain this data. A presentation layer that expects the objects to conform to a file system model may require that data be received within a certain amount of time. For example, the system could time out after a short period if the data is not obtained by the presentation layer. However, in the preferred embodiment of the present invention, the presentation layer does not have any expectations of when the identification data is to be presented. The presentation layer requests data a few times, and can produce a display whenever the data is sent from the lower levels. The presentation layer does not have any expectations as to when this data is to be received.

[0032] This feature is particularly advantageous when web objects are accessed. Since Internet access is typically much slower than access over the computer system files, the timing out of the system can cause problems. In other embodiments, a time limit may be set.

[0033] Different access units can obtain the required data from the objects in vastly different manners. The presentation layer has no expectations of how this data is to be produced. For a file unit access, the data can be obtained in the conventional manner. For a web access system, the system can search for text to use as the name of the object, either from the web page or the web page's uniform resource locator (URL), and can go through the web page to identify URLs contained within it to produce an indication of the children objects of that web page. An access unit for a database can use the details of the database structure to produce the name and links to any children objects. The adaptation layer is preferably quite thin and merely an intermediary between the presentation layer and the different software object access units.

[0034] The access units can also provide different ways of manipulating the software objects as a result of instructions from the presentation layer. For example, if the user selects “open a file”, this instruction is interpreted as appropriate by each of the different access units, to retrieve a file.

[0035] An access unit may be able to access more than one type of object. Additionally, a single type of object can be accessed by more than one access unit.

[0036] FIG. 2B illustrates an alternate embodiment in which the adaptation layer is comprised of a number of adaptation units corresponding to the access units.

[0037] FIG. 3 illustrates the operation of the adaptation layer. Consider object I. The type of object I is checked in block 22. The type of the object can be indicated by a type field for the object; based upon the object's parent; by having the access layer and access units interpret the object, or any other suitable manner. In this example, adaptation layer unit C recognizes the object I, and the name and icon information for the object I is sent to the presentation software. In block 24, it is checked whether object I has any children objects. When children objects are found, the name icon and children status of the objects are checked. Once the parent-child relationships between objects are established, the presentation layer might display, at the top of its hierarchy, all of the top-level nodes for containers that can be accessed.

[0038] FIG. 4 is a diagram illustrating the example of FIG. 3. When object I, which is a file, is opened, the system finds the names, icons, and children status for the three children objects: child object I, child object II, and child object III. When one of these children objects, such as child object III, are selected, data on the child is received and displayed by the display. In this example, a web page is a child of the child object III. Note, this is an entirely different type of object from the child object III, but it is displayed in the same manner as any other type of software object. In FIGS. 4-6, the names given to the different objects are for illustrative purposes; actual object names of the software objects typically do not indicate the type of objects.

[0039] FIG. 5 is a diagram illustrating the display of an embodiment of the present invention. Note that in FIG. 5, software objects from different heterogeneous repositories are shown. For example, data from database records, and from files on the computer system are shown in the same hierarchical display. This is made easier by the use of the adaptation layer of the present invention, since the presentation layer has no expectations about the software object other than the existence of a name. Thus, displays of objects from heterogeneous repositories are allowed, even when the objects are of different, non-compatible types.

[0040] FIG. 6 illustrates a diagram of the display of FIG. 5 in which different objects are selected. In a preferred embodiment of the present invention, different objects of heterogeneous file types can be selected at the same time. The presentation layer makes no assumptions about the types of software objects, and

Claims

1. A computer system including: a plurality of repositories containing a variety of different respective types of software objects; access units respectively associated with said repositories to access at least some of the software objects; an adaptation layer operably connected to the access units to obtain information about the software objects; and presentation software operably connected to the adaptation layer, the presentation layer displaying representations of the software objects, wherein the presentation software receives display information from the adaptation layer, and wherein the display information includes the name of the software object.

2. The computer system of claim 1, wherein the presentation software includes a user interface.

3. The computer system of claim 2, wherein the presentation software includes an open user interface.

4. The computer system of claim 2, wherein the presentation software includes a save user interface.

5. The computer system of claim 1, wherein the transferred display information further includes a software object icon.

6. The computer system of claim 1, wherein the presentation software is such that access units can be added without modifying the presentation software.

7. The computer system of claim 1, wherein the adaptation layer is adapted to determine whether there is any children objects of a software object.

8. A method of forming a hierarchal display of software objects, comprising: providing a software object; checking the software object with an adaptation layer, the adaptation layer being adapted to determine display information for the software object and determine any children objects of the software object; and producing a hierarchal display using display information provided by the adaptation layer, the hierarchal display including different types of software objects, wherein the display information includes the name of the software object.

9. The method of claim 8, wherein the hierarchal display is produced by a presentation layer.

10. The method of claim 8, wherein the display information includes the an icon of the software object.

11. The method of claim 8, wherein the adaptation layer is operably connected to accessing units.

12. The method of claim 11, wherein the adaptation layer is arranged to cause the accessing units to obtain the display information for the software object.

13. The method of claim 8, wherein the different types of objects include database objects.

14. The method of claim 8, wherein the different types of objects include internet web page objects.

15. The method of claim 8, wherein the different types of objects include FTP objects.

16. The method of claim 8, wherein the hierarchal display allows for the selection of multiple objects of heterogeneous types.

17. A method of using multiple heterogenous repositories containing different types of software objects, the method comprising: displaying the software objects in a hierarchical fashion; and selecting more than one of the software objects at the same time, at least some of the more than one selected objects coming from different heterogeneous repositories.

18. The method of claim 17, wherein one of the heterogenous repositories contains database objects.

19. The method of claim 17, wherein one of the heterogeneous repositories contains internet web pages.

20. The method of claim 17, wherein the different types of objects include FTP objects.

21. The method of claim 17, wherein the displaying step includes obtaining display information about the users from an adaptation layer.

22. The method of claim 21, wherein the adaptation layer produces name and icon of the software object for display and tests for children of the software object.

23. The method of claim 21, wherein the adaptation layer includes multiple adaptation units.

24. A computer-readable medium containing a program which executes the following procedure: checking a software object of a computer system with an adaptation layer, the adaptation layer being adapted to determine display information for the software object and determine any children objects of the software object; and producing a hierarchal display using display information provided by the adaptation layer, the hierarchal display including different types of software objects, wherein the display information includes the name of the software object.

25. The computer-readable medium of claim 24, wherein the hierarchal display is produced by a presentation layer.

26. The computer-readable medium of claim 24, wherein the display information includes the an icon of the software object.

27. The computer-readable medium of claim 24, wherein the adaptation layer is operably connected to accessing units.

28. The computer-readable medium of claim 27, wherein the adaptation layer is arranged to cause the accessing units to obtain the display information for the software object.

29. The computer-readable medium of claim 24, wherein the different types of objects include database objects.

30. The computer-readable medium of claim 24, wherein the different types of objects include internet web page objects.

31. The computer-readable medium of claim 24, wherein the different types of objects include FTP objects.

32. The computer-readable medium of claim 24, wherein the hierarchal display allows for the selection of multiple objects of heterogeneous types.