JPH08194597A - Storing system for information on embodyment of hypertext interface - Google Patents

Abstract

PURPOSE: To easily realize a hypertext interface in a computer system centering around a relation data base. CONSTITUTION: The relation data base 20 stores the internal representation of a page, the internal representation of a link button, correspondence relation between the page and the link button, and hypertext interface realizing information provided with information to show procedure bound to the link button in an application unit together with data other than hypertext interface realizing information. A hypertext interpreter 30 issues a retrieving formula on the basis of the designation of a user, and takes out the hypertext interface realizing information in the relation data base 20, and generates the page and the link button on a display 10, and when the link button on the display 10 is designated by the user, it executes the procedure bound to the link button.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a hypertext interface implementation information storage system for storing information (hypertext interface implementation information) for implementing a hypertext interface on a display. The hypertext interface implementation information is handled in units of applications (application areas of the hypertext system), and pages (also called nodes).
It contains the internal representation of the, the internal representation of the link button, the correspondence between the page and the link button, and information indicating the procedure bound to the link button.

[0002]

2. Description of the Related Art Conventionally, a man-machine interface has been realized by interactively presenting data on a display (screen on a display device) of a computer system using a hypertext structure (a type of data structure). There is a method to do. The interface realized in this way is called a hypertext interface.

In the hypertext interface, a page is arranged on the display, and an arbitrary number of link buttons are arranged in the data (in-page data) held in the page (see FIG. 1). When a link button is selected and specified by an instruction from the mouse, the procedure (corresponding) bound to the link button is executed, and the desired page (association with the link button by the designer in advance) is executed. A page having the data defined as is the in-page data) is immediately displayed on the display. Data associated with each other in this way are successively displayed on the display, and a large amount of data regarding each application is efficiently presented to the user.

Here, the procedure bound to each link button is a procedure for simply calling a desired page (a procedure for realizing a static link), and a certain processing is performed and based on the processing result. There is a procedure for calling a page specified by (a procedure for realizing a dynamic link).

Further, in the hypertext interface, multimedia data such as texts, images, sounds, animations, and records in databases are targets for presentation.

[0006] As a reference regarding the hypertext interface (or hypertext system), for example, "Hypercard Developer's Guide (Hypercard Developer's Guide)
Guide), Goodman (D. Goodman)
Written by Bantam Books, 1988 ”.

In the conventional hypertext system, for example, the following hypertext interface realization information storage systems have been adopted.

[Hyper Card (H
Hypercard) ”is a hypertext system that describes Hypercards.
The talk program is stored in the form of a file (see the above reference). Note that, here, "a program of Hypertalk, which is a language that describes a hypercard" corresponds to the hypertext interface implementation information.

Microsoft's OS (Ope)
Windows (Rating System)
In the WinHelp-type hypertext system on 3.1, the internal representation format compiled by the Help Compiler is saved in the form of a file (reference: "Microsoft Access Developer's Kit (Microsoft Access Device).
Loper's Kit) Manual, Microsoft Corporation, 1994 ”). In addition, here, "Help C
The internal representation format compiled by the compiler corresponds to the hypertext interface implementation information.

An existing general-purpose development language, for example, Mic
The program and data written in Visual Basic of Microsoft Corporation are saved (stored) in the form of a file as hypertext interface implementation information.
(Reference: "Microsoft Visual Basic Version 3.0 (Microsoft
Visual Basic Version 3.
0) Manual, Microsoft Corporation, 1994 ”).

As described above, in the conventional hypertext interface implementation information storage system, the hypertext interface implementation information is stored in the file. Therefore, if a hypertext interface is to be realized by a computer system such as a corporate information system that is mainly composed of a relational database, the hypertext interface realization information stored in the file will be compared with the data stored in the relational database. It was supposed to exist in isolation.

[0012]

In the conventional hypertext interface realization information storage system described above, the hypertext interface realization information is stored in a file separate from the relational database, so that the relational database is the main component. Attempts to realize a hypertext interface in a computer system have caused the following problems and.

Problems Due to Mixing of Multiple Data Representation Formats Since data stored in different representation formats such as a database format and a file format coexist in one computer system, management of data in the computer system is troublesome. become. This problem occurs not only when there is a mutual relationship between the data in the relational database and the hypertext interface implementation information in the file, but also when there is no mutual relationship between them.

Problems Concerning Data Conversion Between Hypertext Interface Implementation Information and Other Data (Data in Relational Database) There is a mutual relationship between the data in the relational database and the hypertext interface implementation information in the file. In some cases, it may be necessary to convert data between the two
The management at the time of this data conversion becomes troublesome. For example, if you want to present some of the data stored in the relational database to the user with a hypertext interface,
It is necessary to extract the data from the relational database, convert the data into a file format for hypertext interface implementation information, and incorporate it into the file. Also, regarding the problem of (1), it becomes necessary to duplicate the data of the same content in the database and the file and hold them in different expression formats.

In view of the above points, an object of the present invention is to store all hypertext interface implementation information in a relational database, so that a hypertext interface can be easily implemented in a computer system centered on a relational database. It is to provide a hypertext interface implementation information storage method that can be used.

[0016]

According to the hypertext interface implementation information storage method of the present invention, in a hypertext system for implementing a hypertext interface on a display, data in a page in which a link button is arranged is presented to a user. A display for displaying the page and data other than the hypertext interface implementation information, the internal representation of the page, the internal representation of the link button, the correspondence between the page and the link button,
And a relational database that stores, for each application, hypertext interface implementation information having information indicating the procedure bound to the link button, and a hypertext in the relational database that issues a search formula based on the user's designation. A hypertext interpreter for extracting interface realization information, generating a page and a link button on the display, and executing a procedure bound to the link button when the link button on the display is designated by a user. Have.

[0017]

According to the hypertext interface implementation information storage method of the present invention, in the hypertext system for implementing the hypertext interface on the display, the display displays a page for presenting the in-page data in which the link button is arranged to the user. , The relational database has information other than the hypertext interface realization information, the internal representation of the page, the internal representation of the link button, the correspondence between the page and the link button, and the hypertext indicating the procedure bound to the link button. The interface realization information is stored for each application, and the hypertext interpreter issues a search formula based on the user's specification to retrieve the hypertext interface realization information in the relational database. Link button on the display to produce di- and link button on the display to perform a procedure that is tied to the specified the link button by the user.

[0018]

The present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a hypertext interface implementation information storage system according to an embodiment of the present invention.

The hypertext interface implementation information storage system of this embodiment comprises a display 10, a relational database 20, and a hypertext interpreter 30.

A page, which is a unit for implementing the hypertext interface, is displayed on the display 10. Each page holds in-page data for multimedia data, and any number of link buttons are arranged in the in-page data.

When a link button is selected and designated by the user's instruction from the mouse or the like, the procedure associated with the link button is executed. The procedure bound to the link button is a part of the hypertext interface implementation information and is stored in the link button information table 23 (FIG. 2).
(See "Execution procedure" in (c)).

The procedure includes a procedure for merely calling a desired page (a procedure for realizing a static link that directly links pages) and a page specified based on the processing for performing a certain process. There is a procedure to be called (a procedure that indirectly realizes a dynamic page to call a desired page). In Fig. 1, arrows pointing from a link button on a page to another page indicate a procedure for realizing a static link, and a box called "Procedure" indicates another procedure (procedure for realizing a dynamic link).
Is shown.

The relational database 20 stores hypertext interface realization information in a table format together with ordinary data existing in the prior art. Here, the hypertext interface implementation information in the relational database 20 is the page information table 21.
And a page / link button correspondence table 22, a link button information table 23, and an application information table 24.

The hypertext interface implementation information in the relational database 20 is managed in units of applications. That is, the identification information (page information table number, page / link button correspondence table number and link button information) of the page information table 21, page / link button correspondence table 22 and link button information table 23 corresponding to each application in the application information table 24. A table number) is managed, and a page information table 21, a page / link button correspondence table 22 and a link button information table 23 are provided for each application.

2A to 2D are diagrams showing the structures of the page information table 21, the page / link button correspondence table 22, the link button information table 23, and the application information table 24 in the relational database 20.

The page information table 21 holds an arbitrary number of entries having a page name (page unique name) and in-page data (see FIG. 2A).

Page / link button correspondence table 22
Holds an arbitrary number of entries having a page name and a link button name (link button unique name) (see FIG. 2).
(B)).

The link button information table 23 includes the link button name, the physical position of the link button page (information indicating the physical position of the link button on the page), and the execution procedure (specified by the link button). And an arbitrary number of entries each having a procedure (which is executed when executed) (see FIG. 2C).

The application information table 24 includes an application name, a page information table number, a page / link button correspondence table number, a link button information table number, and a top page name (of the hypertext interface implementation information corresponding to the application. And an arbitrary number of entries having the unique name of the page to be displayed first) (see FIG. 2D).

FIG. 3 shows a hypertext interpreter 3
11 is a flowchart showing the process of Step 0. This processing includes application name receiving step 301, table identification step 302, page generation step 303, link button generation step 304, link button designation standby step 305, and link button corresponding procedure execution step 30.
6, a procedure processing content determination step 307, and a top page mimicry step 308.

Next, the operation of the hypertext interface realization information storage system of the present embodiment thus constructed will be described.

In this embodiment, and by extension, in the hypertext interface implementation information storage system of the present invention, the hypertext interface implementation information is stored in the relational database 20 in a table format as shown in FIGS. 2 (a) to 2 (d). . The hypertext interface implementation information storage method is applied to a computer system (for example, a corporate information system) centering on the relational database 20. That is, the ordinary data (for example, various kinds of company information) stored in the relational database 20 according to the conventional technique and the hypertext interface realization information are centrally managed in the relational database 20 in the present invention. Become.

The hypertext interpreter 30 performs the following processing on the premise of the existence of such a relational database 20 (see FIG. 3).

The unique name (application name) of the application given by the user is received (step 3).
01).

Referring to the application information table 24, the page information table number, the page / link button correspondence table number, the link button information table number and the first page name in the entry having the application name received in step 301 are extracted (step Three
02). As a result, the page information table 21, the page / link button correspondence table 22, the link button information table 23, and the first page corresponding to the application name are specified. Note that such retrieval is realized by issuing a search formula (SQL formula) in SQL, which is a typical database query language (the same applies to a search for the relational database 20 below). By the way, as a reference about SQL, for example, "AN
SI Database Language SQL with Integrity Enhancement (ANSI Database L
Angular SQL with Enhance
ent), ANSI X3.135.1-11989, 1
989 ”.

Next, the contents of the first page (first page specified by the fetching process of step 302) is generated on the display 10 by referring to the page information table 21 specified by the fetching process of step 302 (step). 303). That is, the in-page data in the entry in the page information table 21 having the page name of the first page name extracted in step 302 after issuing the SQL expression is searched, and the search result (in-page data)
The page having "" is displayed on the display 10 as the first page.

Further, referring to the page / link button correspondence table 22 and the link button information table 23 specified by the extraction processing in step 302, a link button is generated in the in-page data in the first page (step 304). . That is, the following processes (1) to (4) are performed. The SQL expression is issued, and the link button name in the entry in the page / link button correspondence table 22 having the first page name fetched in step 302 as the page name is searched. The SQL expression is issued, the link button name is used as an index, and the physical position within the link button page in the entry in the link button information table 23 having the link button name is extracted. The link button is generated using the physical position in the link button page, placed on the first page, and output (displayed) on the display 10.

In the process of interactive processing based on the display on the display 10, the user waits for the designation of the link button in the page on the display 10 (designation by an instruction from the mouse or the like). (Step 3
05).

When a certain link button is designated in the standby process of step 305, the procedure corresponding to the designated link button (the execution procedure in the entry having the link button name of the link button) is linked button information table 23 ( Retrieved from the link button information table 23 specified by the retrieval processing in step 302) (retrieved by issuing an SQL expression and searching)
The procedure is executed (step 306).

After the execution of the procedure of step 306, the processing relating to the executed procedure is "processing for the same page (processing for calling the same page)" or "processing for generating a new page (new Processing for calling another page) ”(step 307).

If it is determined in step 307 that the process is for the same page, the process returns to step 305 (standby state).

If it is determined in step 307 that the process is to generate a new page, the new page is interpreted (supposed) as the first page (step 308) and the process returns to step 303.

As described above, the hypertext interpreter 30 performs the action (operation of the mouse, etc.) from the user.
Accordingly, the process corresponding to the link button designated by the user and the process of generating a new page on the display 10 based on the execution are interactively advanced. The realization of the hypertext interface in the process of this processing (takeout of the hypertext interface realization information) is due to the fact that each table shown in FIGS. 2A to 2D is stored as a table in the relational database 20. Then, a search using the SQL expression becomes possible.

In this embodiment, as shown in the flow chart of FIG. 3, when the hypertext interface is realized on the display 10, the necessary hypertext interface is realized according to the designation of the link button from the user. Information is retrieved and retrieved from the relational database 20 each time. However, when it is necessary to promptly generate a screen related to the hypertext interface, all the hypertext interface implementation information (related to the application name) first identified by the application name (when the application name is specified). The page information table 21, the page / link button correspondence table 22, the link button information table 23, and the application information table 24) are collectively (loaded) in the main memory, and the user specifies the link button. It is also possible to deal with it by "reading from main memory" instead of "accessing the relational database 20" (see the invention of claim 2).

Further, in this embodiment, FIGS. 2 (a) to 2 (d) are used.
The case where each table in the relational database 20 is designed in the manner as shown in FIG. 2 has been described. The table allocation method (design method) of the hypertext interface implementation information in the relational database 20 is as shown in FIG.
It is not limited to the modes shown in (a) to (d) (internal representation of page, internal representation of link button, correspondence between page and link button, and information indicating procedure bound to link button). Is a relational database 20
The present invention can be implemented by other table allocation methods as long as they are stored in the table).

[0047]

As described above, according to the present invention, by storing all the hypertext interface implementation information in the relational database, a relational database can be used in a computer system centering on the relational database (a computer system such as a corporate information system). The ordinary data and the hypertext interface implementation information can be centrally managed in the relational database, and the hypertext interface in such a computer system can be easily implemented.

Further, since the normal data and the hypertext interface realization information are designed as the table in the relational database in the same manner, it is not necessary to duplicate the two and hold them in different expression formats. This has the effect of facilitating data conversion between the two.

Further, since all the hypertext interface implementation information is stored in the table in the relational database, the computer system is a client-server type computer system in which the relational database exists on both the client side and the server side. When the present invention is applied to, the relational database table indicating the hypertext interface realization information can be placed in each client machine (local machine) or can be centrally managed by the server machine, and can be freely selected according to the situation. The effect of being able to do (effect of having good portability) occurs.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a hypertext interface implementation information storage system according to an exemplary embodiment of the present invention.

FIG. 2 is a diagram showing a configuration of each table in a relational database shown in FIG.

FIG. 3 is a flowchart showing a process of a hypertext interpreter in FIG.

[Explanation of symbols]

 10 display 20 relational database 21 page information table 22 page / link button correspondence table 23 link button information table 24 application information table 30 hypertext interpreter

Claims (4)

[Claims] 1. A hypertext system for implementing a hypertext interface on a display, together with a display for displaying a page for presenting to a user data in a page in which a link button is arranged, and data other than hypertext interface implementation information. A relational database that stores, for each application, hypertext interface implementation information having information indicating the internal representation of the page, the internal representation of the link button, the correspondence between the page and the link button, and the procedure bound to the link button. , Retrieves hypertext interface implementation information in the relational database based on user's designation, generates page and link button on the display, and displays on the display A hypertext interface realization information storage system comprising: a hypertext interpreter that executes a procedure bound to a link button when the link button is designated by a user. 2. All the hypertext interface realization information specified by the application name specified by the user is collectively loaded into the main memory at the time of the specification,
"Read from main memory" instead of "access to relational database" in response to user specifying link button
The hypertext interface implementation information storage system according to claim 1, further comprising a hypertext interpreter that implements a hypertext interface by coping with the above. 3. The hypertext interface implementation information table in the relational database is a page information table, a page / link button correspondence table, a link button information table, and an application information table, and the page information table is a page name and a page. Data, the page / link button correspondence table has a page name and a link button name, and the link button information table has a link button name, a link button physical position within a page, and an execution procedure, The hypertext interface according to claim 1 or 2, wherein the application information table has an application name, a page information table number, a page / link correspondence table number, a link button information table number, and a first page name. Implementation information storage method. 4. The hypertext according to claim 1, 2 or 3, wherein a database query language for describing a search expression issued by the hypertext interpreter to the relational database is SQL. Interface implementation information storage method.