JPH11312165A - Image display system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve independence between contents constituting an image and a program body. SOLUTION: A contents data base 1 consists of a form image table, in which each image name specifying a picture corresponds to a data base name storing contents information constituting the image and an image information table in which each image name corresponding to contents information. A data base management module 3 prepares a working data base from the form image table, and at the time of receiving a contents acquiring request from the program body 2 by specifying a certain image name, retrieves a data base name from the working data base, based on the image name, retrieves corresponding contents information from the image information table of the corresponding data base and returns the retrieved contents information to the program body 2.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the operation of content, which is an element constituting a screen, in a screen display system.

[0002]

2. Description of the Related Art A KIOSK system that switches screen display by user operation and provides desired information to the user, and an automatic transaction device that transitions a screen for guiding user operation according to the operation In a screen display system such as the above, contents such as images and buttons constituting a screen conventionally exist as a group of content files on a file system even if they are incorporated in a program main body or not. I was

[0003]

As described above, conventionally, the content cannot be separated from the program main body, and it is impossible to provide only the content, or the change of the content extends to the change of the program main body. However, since the contents cannot be easily changed, there is a problem that the work of changing the contents of the screen is troublesome.

[0004]

In order to solve the above-mentioned problems, the present invention provides a database of information of contents constituting a screen, and stores a screen name for specifying a screen and contents information constituting the screen. A form screen table that associates a certain database name and a screen information table that associates a screen name with content information are provided.
A work database or a work text file is created from the form screen table, a database name is searched from the screen name in the work database or the work text file, and a content is obtained from the screen name from the screen information table of the corresponding database. A means for searching for information is provided.

[0005]

FIG. 1 is a block diagram showing a first embodiment of a screen display system according to the present invention. In the figure, reference numeral 1 denotes a content database, and information on the content is stored in the content database 1.

[0006] Reference numeral 2 denotes a program body, which does not incorporate content information into the program body 2. As described above, the content information is stored in the content database 1 and is independent of the program body 2. Reference numeral 3 denotes a database management module for coordinating the program main body 2 and the content database 1. The program body 2
By issuing a content acquisition request by designating a screen name to the database management module 3, the database management module 3
And sends the content information to the program body 2.

[0007] The content database 1 is composed of two tables, a form screen table and a screen information table. FIG. 2 is an explanatory diagram showing an example of the form screen table.
ispName, FormName indicating the form name,
It has three columns of DBName indicating the file name of the database, and holds the relationship between the screen name and the form name, and the relationship between the screen name and the stored database name.

FIG. 3 is an explanatory diagram showing an example of a screen information table. The screen information table is a DispNa indicating a screen name.
me, ObjName indicating the object name, PropName indicating the property name, DataType indicating the data type of the property, Prop indicating the value of the property
It has five columns of Value, and holds the object name, property name, property data type, and property value corresponding to the screen name.

When the content database 1 is operated, the database management module 3 uses a work database as a temporary file, and performs matching between a specified screen and a database including content information of the screen (hereinafter, target database). Aim. Here, the screen refers to an information unit forming one piece of information provided to the KIOSK user by a plurality of contents, and the screen name is a unique name given to this screen.

Hereinafter, the operation of the first embodiment will be described by taking as an example a case where contents are stored in two databases and the system is operated. FIG. 4 is a diagram showing a first database (hereinafter, referred to as DB) constituting the content database 1.
FIG. 5 is an explanatory diagram showing an example of 1), and FIG. 5 is an explanatory diagram showing an example of a second database (hereinafter, DB2) constituting the content database 1. In the first embodiment, the DB
1 and DB2. Hereinafter, opening of the database, acquisition of contents, and closing of the database will be described individually.

(1) Open program main body 2 and content database 1
When receiving the request to open B1, the database management module 3 opens the DB1 and simultaneously creates a work database. FIG. 6 is an explanatory diagram showing a procedure for creating a work database.
First, the form screen table of DB1 which received the open request is copied to the work database, and FIG.
Create the database shown in (1).

When copying, a DB is stored in the form screen table.
If the Name column value does not exist, the relevant database, here, DB1, is added as a column value, and FIG.
The data of the database shown in (1) is updated to the data shown in FIG. Subsequently, when a request to open the DB2 of the content database 1 is received from the program body 2, the database management module 3 opens the DB2 and stores the DB2 in the work database shown in FIG. , DB2 form screen table is added.

At this time, if the same screen name as the screen name included in the form screen table of DB2 is included in the work database created from the form screen table of DB1, the database opened later (in this case, DB2 ) Is overwritten by the record. In the case of the first embodiment, in the work database shown in FIG. 6B, the DispName column value is “screen 2-1”.
Is overwritten with the record of the DispName column value “screen 2-1” of DB2.

Since the DBName column value does not exist in the DB2 form screen table, the DBName column value is used as the DBName column value in the work database.
2 to create the database shown in FIG. (2) Acquisition of Content FIG. 7 is a block diagram showing the flow of processing when acquiring content.

The program body 2 issues a content information acquisition request to the database management module 3 by specifying a screen name when displaying a screen according to a user operation. When a screen name, for example, screen 2-1 is specified and a content acquisition request is received from the program body 2,
The database management module 3 executes the processing shown in FIG.
A search is made for a record in which the specified screen name matches the DispName column value of the work database shown in (3) ().

If a corresponding record exists, the target database, here DB2, is identified by referring to the DBName column value of the record (). The database management module 3 stores the target database (D
A record in which the DispName column value of the screen information table in B2) matches the specified screen name is searched ().

As a result of the search, the ObjName
The content information including the column, the PropName column, the DataType column, and the PropValue column is acquired () and returned to the program body 2. The program body 2 displays a screen using the returned content information. (3) Close When a close request is received from the program body 2, the database management module 3 closes all databases currently open, in this case, DB1 and DB2. At the same time, the database management module 3 deletes the work database.

As described above, according to the first embodiment of the present invention, the content information is separated from the program body into a database, and the screen name and the database name in which the content information constituting this screen are stored. And a screen information table in which screen names and content information are associated with each other. When the database is opened, a work database is created from the form screen table. In the search using the key, it is not necessary to search all open databases, and the target database can be specified only by searching the work database.
Then, since the content information only needs to be returned from the corresponding database, there is an effect that the execution speed of the entire system can be improved.

Next, a second embodiment of the present invention will be described. In the second embodiment described below, the configuration of the system is the same as that described in the first embodiment with reference to FIG. 1, and the content database 1 includes the form screen table described in FIG. It consists of the two screen information tables described.

In the second embodiment, when the content database 1 is operated, the database management module 3
Uses a work text file as a temporary file, and attempts to match a specified screen with a database (hereinafter, a target database) containing content information of this screen. Note that the file specifications of the work text file are in the DispNam of the form screen table.
One record including e, FormName, and DBName is described in one line, and each record is separated by a tab character.

The operation of the second embodiment will be described below by taking as an example the case where contents are stored in two databases and the system is operated. In the second embodiment, DB1 shown in FIG. 4 and DB2 shown in FIG. 5 are used. Hereinafter, opening of the database, acquisition of contents, and closing of the database will be described individually.

(1) Open From the program body 2 to the D of the content database 1
When receiving the request to open B1, the database management module 3 opens the DB1 and simultaneously creates a work text file. FIG. 8 is an explanatory diagram showing a procedure for creating a work text file. First, the database management module 3 converts each column value of the form screen table of the DB 1 that has received the open request to the work text file into the format of the work text file. And a text file shown in FIG. 8A is created.

When copying, a DB is stored in the form screen table.
If the Name column value does not exist, the relevant database, here, DB1, is added as a column value, and FIG.
The data of the text file shown in FIG.
Update to the data shown in. Subsequently, when a request to open the DB2 of the content database 1 is received from the program body 2, the database management module 3 opens the DB2 and creates a work text file shown in FIG. 8 (2) created from the form screen table of the DB1. And D
Each column value of the form screen table of B2 is added.

At this time, if the same screen name as the screen name included in the DB2 form screen table is included in the work text file created from the DB1 form screen table, the database opened later (in this case, DB2) is overwritten by the record. In the case of the second embodiment, in the work text file shown in FIG. 8B, the DispName column value is “screen 2”.
The row of “−1” is overwritten with the disp column value of the record of the “DispName” column value “screen 2-1” of the DB2.

Since the DBName column value does not exist in the form screen table of DB2, a portion corresponding to the DBName column value of DB2 in the work text file is set to "DB2", and the text file shown in FIG. I do. (2) Acquisition of Content FIG. 9 is a block diagram showing the flow of processing when acquiring content.

When displaying a screen corresponding to a user's operation, the program body 2 designates a screen name and issues a content information acquisition request to the database management module 3. When a screen name, for example, screen 2-1 is specified and a content acquisition request is received from the program body 2,
The database management module 3 executes the processing shown in FIG.
Disp of each line of the working text file shown in (3)
Search for a line where the Name column value matches the specified screen name ().

If the corresponding row exists, the DB of the row
The target database, here DB2, is identified with reference to the Name value (). The database management module 3 searches for a record in which the DispName column value of the screen information table of the target database (DB2) matches the specified screen name ().

As a result of the search, the ObjName
The content information including the column, the PropName column, the DataType column, and the PropValue column is acquired () and returned to the program body 2. The program body 2 displays a screen using the returned content information. (3) Close Upon receiving a close request from the program body 2, the database management module 3 closes all currently open databases, in this case, DB1 and DB2. At the same time, the database management module 3 deletes the work text file.

As described above, in the second embodiment of the present invention, a text file is used as a work temporary file. In general, the use of a text file has less overhead than the use of a database in file access, so that the execution speed of the entire system is further improved. Also, the text file has a smaller file size than the database file when the amount of data to be stored is the same.

Therefore, as a temporary work file,
The use of this work text file has the effect of improving processing speed and saving disk space.

[0031]

As described above, according to the present invention, information of contents constituting a screen is converted into a database, and a screen name for specifying the screen is associated with a database name storing the contents information constituting the screen. A form screen table and a screen information table in which screen names and content information are associated with each other are provided, a work database is created from the form screen table, a database name is searched from the screen name in the work database, and Since the content information was searched from the screen name in the screen information table of the database, the program body
Using the screen name as a key, only searching the work database,
The database in which the desired content is stored can be specified. Then, since the content information can be obtained from the corresponding database, the independence between the program body and the content information can be increased, and the content information can be changed without affecting the program body. Becomes

Further, since a form screen table and a screen information table are provided when the content information is made into a database, it is possible to easily change the content information or provide only the content information. Furthermore, since it is not necessary to search all databases at the time of database search, it is possible to improve the execution speed of the entire system.

If a work text file is created in place of the work database, the processing speed can be further improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a first embodiment of a screen display system according to the present invention.

FIG. 2 is an explanatory diagram showing an example of a form screen table

FIG. 3 is an explanatory diagram showing an example of a screen information table.

FIG. 4 is an explanatory diagram showing an example of a first database.

FIG. 5 is an explanatory diagram showing an example of a second database.

FIG. 6 is an explanatory diagram showing a procedure for creating a work database.

FIG. 7 is a block diagram showing the flow of processing when acquiring content.

FIG. 8 is an explanatory diagram showing a procedure for creating a work text file.

FIG. 9 is a block diagram showing the flow of processing when acquiring content.

[Explanation of symbols]

 1 Content database 2 Program body 3 Database management module

Claims (3)

[Claims] 1. A form screen table in which information of contents constituting a screen is made into a database, and a screen name for specifying a screen is associated with a database name in which contents information constituting the screen are stored; A screen display system comprising a screen information table in which information is associated. 2. The work database according to claim 1, wherein a work database is created from the form screen table, a database name is searched from the screen name in the work database, and a content is searched from the screen name in the screen information table of the corresponding database. A screen display system comprising means for searching for information. 3. The work text file according to claim 1, wherein a work text file is created from the form screen table, a database name is searched for from the screen name in the work text file, and a screen name is obtained from the screen information table of the corresponding database. A screen display system characterized by comprising means for searching for content information from a computer.