JP2000010769A - Method and device for user interface design - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily design the image of a GUI(graphical user interface) operation picture by GUI operation and to dynamically incorporate general-purpose software parts, which are arranged on the GUI operation picture, in a device. SOLUTION: Index information related to attributes, events, and messages which software component have is read, and read index information is stored in a storage means 114, and an event list of the software component in a link source is generated based on index information stored in the storage means 114, and an event selected based on this event list is set as an event of software component of the link source, and a message list of the software component in a link destination is generated based on index information stored in the storage means 114, and a message selected based on this message list is set as a message of the software component of the link destination which corresponds to the event set to the software component of the link source.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a screen design and operation design for a system that receives an input from a user and uses an operation screen in which parts are laid out as a user interface (UI). The present invention relates to a user interface design apparatus and method suitable for performing an operation check by simulation.

[0002]

2. Description of the Related Art There are many tools for realizing an operation screen design by laying out parts and an operation design by GUI operation and executing the design as designed.

For example, if VisualBasic (a registered product of Microsoft Corporation in the United States) is used, programming of Windows (a registered product of Microsoft Corporation in the United States) can be easily performed using a GUI operation.

[0004]

However, while a visual programming tool such as VisualBasic can construct a user interface for performing a complicated operation, most of the operation design is performed by writing a program code. You need to learn.

In the user interface design apparatus described in Japanese Patent Application Laid-Open No. H10-21062, attributes are set in advance for components handled in the apparatus, and the attributes are selectively combined to describe a program. . However, this attribute must be stored in the device in advance, and it has been impossible to dynamically load general-purpose software components into the device.

Accordingly, the present invention has been made in consideration of the above circumstances, and its object is not only to design an image of a GUI operation screen (user interface operation screen) but also to design an operation of a GUI (graphical user interface) operation (event It is an object of the present invention to provide a user interface design apparatus and method which can be easily (without having to write a program) by an operation of associating a message with a message.

Another object of the present invention is to provide a user interface design apparatus and method capable of dynamically incorporating general-purpose software components to be arranged on a GUI operation screen into the apparatus.

[0008]

The user interface designing apparatus of the present invention arranges various software components (for example, OCX) at arbitrary positions on a card representing an operation screen of a user interface, and The operation is designed by associating the event of the link source and the message of the link destination with the software component as a link source and another software component or card as a link destination, and simulating the designed user interface. User interface design equipment
Reading means for reading index information (property information, event information, message information, and argument information) on attributes, events, and messages of the software component (reading OCX information from the registry 113);
A storage unit (table 114) for storing the index information read by the reading unit, and an event list (see FIG. 15) of the link source software component based on the index information stored in the storage unit. 1; first setting means (a link setting dialogue or the like) for setting an event selected based on the event list as an event of the link source software component; and index information stored in the storage means. Second creating means for creating a message list (see FIG. 16) of the software component of the link destination based on the message list, and associating the message selected based on the message list with the event set in the software component of the link source. Second set as the message of the linked software component With setting means (link setting dialogue etc.), image design and operation design of the GUI operation screen (user interface operation screen) can be easily performed by GUI (graphical user interface) operation without the need to write programs. )It can be carried out.

Further, general-purpose software components to be arranged on the GUI operation screen can be dynamically incorporated in the apparatus.

[0010] The software component selectable as an argument of a message set in the software component of the link destination based on the index information stored in the storage means (for example, the software component arranged on the card). List of attributes of software components that are not available (Figure 2)
0, see FIG. 21) and third setting means (for setting the attribute of the software component selected based on the list as an argument of the message of the linked software component). By providing an argument list dialog, an argument setting dialog, and the like, link setting can be easily performed even when using an attribute (property) of a software component as an argument of a message.

In a preferred embodiment, when there are a plurality of link source software components, the first creating means generates an event based on index information of an event which the plurality of software components have in common and which is stored in the storage means. By creating a list, a plurality of links from a plurality of link sources can be easily set by one operation.

In a preferred embodiment, when there are a plurality of linked software components, the second creating means is configured to send a message based on index information of a message which is stored in the storage means and which the plurality of software components have in common. By creating a list, a plurality of links to a plurality of link destinations can be easily set by one operation.

In a fifth aspect, a list of attributes of the software component selectable as an argument of a message set for the software component of the link destination is created based on the index information stored in the storage means. And third setting means for setting the attribute of the software component selected based on the list as an argument of the message of the software component of the link destination, wherein the third setting means When there are a plurality of link source software components, based on the index information of the attribute which the plurality of link source software components have in common stored in the storage means (for example, the plurality of link source software components) In the index information of the attribute that the parts have in common, the “type” of the attribute is the same as the “type” of the selected message. By creating a) list by extracting, it is possible to easily set a plurality of links to a plurality of destination in one operation. Also, when using the attribute (property) of a software component as an argument of a plurality of link destination messages, link setting can be easily performed.

Claim 6: In the user interface design method of the present invention, various software components are arranged at arbitrary positions on a card representing an operation screen of a user interface,
An operation is designed by associating an event of the link source with a message of the link destination, using any of the software components as a link source, and linking an event of the link source with a message of the link destination with another software component or card as a link destination. In a user interface design method for performing a simulation, reading index information on attributes, events, and messages of the software component, storing the read index information in a storage unit, and storing the read index information in the index information stored in the storage unit. An event list of the software component of the link source is created based on the event list, an event selected based on the event list is set as an event of the software component of the link source, and the link destination is set based on the index information stored in the storage unit. of By creating a message list of the software component and setting a message selected based on the message list as a message of the link destination software component corresponding to the event set in the link source software component, the GUI operation is performed. Screen (user interface operation screen) image design and operation design are easy with GUI (graphical user interface) operation (no need to write programs)
It can be carried out.

Further, general-purpose software components arranged on the GUI operation screen can be dynamically incorporated into the apparatus.

In the above-mentioned user interface design method, it is preferable that the list of attributes of the software component selectable as an argument of the message of the software component of the link destination based on the index information stored in the storage means. Is created, and the attribute (property) of the software component is used as an argument of the message by setting the attribute of the software component selected based on the list as the argument of the message of the software component at the link destination. Can easily set the link.

In a preferred embodiment, when there are a plurality of link-source software components, an event list is created based on index information of an event which is stored in the storage means and which is shared by the plurality of software components. A plurality of links from a plurality of link sources can be easily set in a single operation.

In a ninth aspect, when there are a plurality of linked software components, a message list is created based on the index information of the messages stored in the storage means and shared by the plurality of software components.
A plurality of links to a plurality of link destinations can be easily set in a single operation.

In a preferred embodiment, when there are a plurality of link-source software components, the link-destination software component is stored based on index information of an attribute common to the plurality of link-source software components stored in the storage means. Creates a list of software component attributes that can be selected as an argument of a message to be set for the component, and sets the attribute of the software component selected based on this list as an argument of the message of the software component at the link destination By doing so, it is possible to easily set a plurality of links to a plurality of link destinations by one operation. Also, when using the attribute (property) of a software component as an argument of a plurality of link destination messages, link setting can be easily performed.

[0020]

Embodiments of the present invention will be described below with reference to the drawings.

(1) Configuration of User Interface Design Apparatus First, the configuration of the user interface design apparatus will be described.

As shown in FIG. 2, the user interface (UI) designing apparatus according to the present embodiment mainly includes a speaker used for outputting voice and sound, and a CR.
An output device 101 including a display device such as a T display or a liquid crystal display, and an input device (hereinafter, referred to as a design-time data input device) 102 including input means such as a keyboard and a mouse and used for inputting data and the like at the time of design. A user interface design mechanism (hereinafter, referred to as a UI design mechanism) 103 for interactively interacting with a designer or a user at the time of design and simulation;
An input device (hereinafter referred to as a simulation input device) 10 comprising input means such as a touch panel (for touch input), a microphone (for voice input), a mouse, and a keyboard, and used for inputting information during simulation.
4, a database (DB) 105 for storing and managing designed screen information, operation information, data materials, and the like; an area for temporarily storing designed screen information, operation information, data materials, and the like; Memory 10 for providing areas and the like
6. Here, the design-time data input device 102 and the simulation-time input device 104 are physically the same input device.

The user interface design apparatus according to the present embodiment includes, for example, a touch panel, a microphone,
Input means such as a mouse and a keyboard; output means such as a speaker and a display (display device); a large-capacity storage device such as a floppy disk device and a hard disk device; a main memory; Is realized.

In particular, the function of the UI design mechanism 103, which is the center of the user interface design apparatus of FIG. 2, is realized by using a storage medium, such as a floppy disk, on which a program for executing the function by the personal computer is recorded. The recording medium is mounted on a floppy disk device in the personal computer, and the program recorded on the floppy disk is read and executed by the personal computer (CPU therein).

For example, as shown in FIG. 1, a program for executing a function of the UI design mechanism 103 recorded on a recording medium is executed on a computer 10, and the computer 10 has a keyboard 11 as an input means and a keyboard 11. A mouse 12 and a display 13 as output means are connected.

The UI design mechanism 103 includes an editing unit 107 for managing screens and operations at the time of design, and a UI
And a prototype execution unit 108 which manages the simulation at the time of confirming the operation of I. The configurations of the editing unit 107 and the prototype execution unit 108 will be described later.

(2) Outline of UI Design Mechanism 103 Next, an outline of the UI design mechanism 103 will be described with reference to a screen image example in FIG.

The UI design mechanism 103 shown in FIG. 2 is a tool for designing the UI screen use and operation specifications using a GUI. UI
The design of the screen by the design mechanism 103 is performed on a screen displayed on the display 13 as the output device 101, as shown in FIG. That is, a card 202 is created on the card layout manager window (CLMW) 201 as a screen object (object in object orientation) representing a UI operation screen,
The screen design is performed by arranging the software components 202 on the card.

As the software component, an arbitrary one is selected from the toolbar 204 and arranged. In the present embodiment, as this software component, for example, Win32
(Registered product of Microsoft Corporation, US) API (Application Program)
OCX (OLE) used on the
(Object Linking and Embed
ding) custom control).

Each OCX has globally unique identification information indicating the type of software component called CLSID. In addition to the CLSID, the OCX file (substance file) includes, as described later,
Index information (event information, message information, property information, argument information) such as attributes, events, and messages of the OCX, methods, and the like are described.

The server that supplies the OCX is the server 1 shown in FIG.
Twelve. The OCX that the user wants to use with the GUI design device needs to be installed in the computer 10 in advance (before starting the UI design device and starting the design). That is, a floppy disk or CD-ROM is stored in a storage device such as a hard disk in the computer 10 of FIG.
When you install OCX using ROM etc.,
The OCX file is written in a predetermined storage area of the computer 10. The storage area in which the OCX file is written is called a server 112. At this time, it is necessary to register the CLSID of the installed OCX in the OS (operation system). In this case, for example, a registry of Windows (registered product of Microsoft Corporation, USA) is used.

When the OCX is installed, the registry 113 stores the CLSID of the OCX and the name of the OCX (for example, a component name such as “button” or “calculation result display box”). Pointer information to the storage area where the OCX file is stored
OCX information) is registered.

In this case, the installation of the OCX (creation of the server 112 and registration in the registry 113) is automatically executed by an installer corresponding to Windows.

At the time of design by the UI design mechanism 103, the map viewer 205 may be displayed together with the CLMW 201. This map viewer 205 is a window for listing and displaying created cards.
On the map viewer 205, a card icon 206 which is a reduced image of a created card is displayed. If the number of created cards is large, only the card icons corresponding to some of the cards are displayed in the map viewer 205.
The card icons displayed above and corresponding to the remaining cards are displayed by scrolling up and down or left and right on the map viewer 205. When a link is provided from a software component (hereinafter, also referred to as a component object) arranged on the card to another card, a link and an arrow (link) indicating the direction are provided between the corresponding card icons. Line) is displayed.

(3) Types of Managers Next, types of managers (management means) included in the editing unit 107 and the prototype execution unit 108 in FIG. 2 will be described.

First, the editing unit 107 shown in FIG.
Is composed of a card layout manager (CLM) 109 for generating and managing the card 202, reading software components from the server 112, and arranging the software component on the card 202.

When the CLM 109 is activated, the card 20
2 and software components laid out on the card 202, and link setting for operation processing performed in response to an event from the user (such as clicking a button or performing voice input). Further, it has a function as a so-called container that reads out software components (that is, OCX) from the server 112 and registers them in the card 202.

On the other hand, the prototype execution unit 108 in FIG.
Is composed of a prototype manager (PTM) 111. The PTM 111 sets C according to an instruction from the user.
It is started by the LM 109. When the PTM 111 is activated, the software component that has received the event from the user sends a message to the set link destination by using the message transmission function. By repeating this message transmission, an operation simulation can be performed as designed for the link.

(4) Card layout manager (CL
M) Container Function FIG. 5 shows that the CLM 109
CX index information (events of the OCX,
5 is a flowchart illustrating a processing operation for acquiring information on a message, a method, and an attribute (property), which are hereinafter referred to as event information, message information, method information, and property information.

When the application of the GUI design device is started (step S1), the CLM 109 acquires the OCX information from the registry 113 of the computer 10 (step S2), and as shown in FIG.
Create and arrange icons for each OCX (step S
3).

The file (icon file) for restoring the OCX icon is, for example, a file created in advance corresponding to the CLSID, and
The icon may be created by reading the icon file corresponding to the CLSID read from the third file. Or,
The icon file of each OCX is stored in the server 112
Stored in correspondence with the CLSID of the CX, the registry 11
The icon may be read out from the server 112 based on the pointer information to the icon file corresponding to the CLSID read out from the server ID 3 to create the icon.

Next, the CLM 109 checks the registry 113
OCX information read from (pointer information included in)
, The server 112 is accessed, and for each OCX, event information, message information,
The property information and the argument information are read out, and the table 11
4 is created (step S4).

For the table 114 created here, for example, one table is allocated to each OCX as shown in FIG. That is, in one table, property information, event information, message information, and argument information of the OCX are written in association with the CLSID (and component name) of each OCX.

FIG. 7 shows an example of the property information stored in the table 114. The property information includes a CLSID which is globally unique identification information of the OCX having the property, and a member ID which is unique identification information in the OCX for identifying each property when the OCX has a plurality of properties.
For example, if the OCX is a button, a property name indicating "data", "display character color", "background color", or the like representing a display character, a text, or the like of the button, and whether the property is an integer type Property type information indicating character type or the like is stored. One property (name) corresponds to one property information.

Since one OCX usually has a plurality of properties, this property information is created in the number of properties and stored in the table 114.

FIG. 8 shows an example of the event information stored in the table 114. The event information includes CLSID, which is globally unique identification information of the OCX having the event, and an OID for identifying each event when the OCX has a plurality of events.
A member ID, which is unique identification information in the CX, and, for example, if the OCX is a button, an event name such as “button down”, “button up”, “click”, etc.
A list of arguments (for example, a list of argument names) sent when the event occurs is stored. 1
One event (name) corresponds to one event information.

Since a plurality of events usually exist in one OCX, this event information is created by the number of events and stored in the table 114.

FIG. 9 shows an example of message information stored in the table 114. The message is a function that can call the OCX. The message information contains the OC with the message
CLSID which is globally unique identification information of X
When the OCX has a plurality of messages, a member ID which is unique identification information in the OCX for identifying each message, a message name such as "display" or "delete", and a message A list of arguments required at the time of the call (for example, a list of argument names) and return value information of the message are stored. One message (name) corresponds to one message information.

Since a plurality of messages usually exist in one OCX, this message information is created in the number of messages and stored in the table 114.

FIG. 10 shows an example of the argument information referred to from the argument list of the event information and the message information. The argument information includes an argument ID as argument identification information, an argument name such as “number” or “character color”, and, for example, when the argument name is “number”, an argument type indicating whether it is an integer type or a real number type. Has been saved.

Here, property information, event information, message information, and the like configured as shown in FIGS.
It is assumed that the CLM 109 reads argument information that has been written in each OCX file in advance, and creates a table 114 as shown in FIG.

(5) Description of Design Operation Next, the UI design apparatus (the UI design mechanism 103 in FIG. 2) of FIG.
The design operation will be described. This design operation is executed by the editing unit 107 in the UI design mechanism 103 in accordance with an instruction from the designer. The state during the design is called a design mode. On the UI design apparatus according to the present embodiment, it is necessary to perform two operations of designing a screen image (appearance of a screen) in which components are arranged and designing an operation scenario as described below.

Here, the calculator GU shown in FIG.
The case where I is created will be described as an example.

(5-1) Screen Image Design When the designer starts up the UI design mechanism 103 in FIG.
The CLM 109 in the editing unit 107 of the UI design mechanism 103 is activated. When the CLM 109 is activated, the information (designed screen information, operation information, data material, and the like) stored in the DB 105 is read into the memory 106, and as shown in the flowchart of FIG. The OCX information is read from the registry 113.

As shown in FIG. 3, a card layout manager menu (CLMM) 200, a card layout manager window (CLMW) 201, and a toolbar 204 are displayed on the display of the output device 101 on a screen. On the other hand, the CLMM 200 includes, for example, a “card”
Items such as “card display”, “edit”, “information setting”, “link”, and “prototype execution” are prepared.

The OCX icon is displayed on the toolbar 204 as shown in FIG.

In the screen display state of FIG. 2, the designer operates the design-time data input device 102 (for example, a mouse), and
When the cursor is moved to the item of “card” in the MM (card layout manager menu) 200 and the mouse is clicked to select “card”, the “card” is selected.
Are displayed by the CLM 109. In the “card” submenu, for example, “new card”, “call card parts”, and “end” are prepared. Then, when the designer moves the cursor to “new card” and selects it, a new card is generated by the CLM 109 and displayed on the CLMW 201. The generated card information (screen object) is stored in the memory 1
06.

To design a screen (UI operation screen), a desired card 202 may be displayed, and a desired component object may be arranged there.

Here, in order to display a desired card,
First, the designer moves the cursor to the item of “card display” in the CLMM 200 and clicks on it, and the “card display”
Display the submenu corresponding to. In this submenu, for example, items “next card” and “previous card” are prepared. Meanwhile, the created card (information of)
Are stored and managed in the creation order (here, logical order) in the DB 105, and are read into the memory 106 at this stage as described above.

Therefore, when the designer selects the “next card”, the card created one card after the currently displayed card is
When the “previous card” is selected, the card created immediately before the currently displayed card is stored in the memory 106 by the CLM 109.
And is displayed on the CLMW 201.

A card 703 displayed on the CLMW 700 in FIG. 11 is a card read from the memory 106 in this way or a newly created card. Although FIG. 11 shows a state in which various card components (software components) are arranged on the card 702, it is assumed that they have not been arranged at this stage.

The designer selects a software component to be placed on the card 702 displayed as described above from the icons displayed on the toolbar 204 in FIG.

First, the designer selects, from the toolbar 204, a dedicated OCX for calculation, which is a calculation result display box 701, and specifies a desired arrangement position on the card 703. Then, the CLM 109 obtains the pointer information corresponding to the identification information of the selected OCX from the registry 113, accesses the server 112, and executes the processing based on the file for restoring the OCX image read from the server 112. An image is created and arranged at a designated position on the card 703 as shown in FIG.

Next, a button 702 is clicked on the toolbar 204.
Is selected, and a desired arrangement position on the card 703 is designated. Then, the CLM 109 obtains the pointer information corresponding to the identification information of the selected OCX from the registry 113, accesses the server 112, and executes the processing based on the file for restoring the OCX image read from the server 112. An image is created and arranged at a designated position on the card 703 as shown in FIG.

Next, the properties of the software components arranged on the card 703 are set. For example, card 7
It is assumed that the button 702 arranged on 03 is an OCX having two property names of “data” and “character color” (that is, having at least two property information corresponding to the two property names). The designer
When this button 702 is clicked on with a mouse as design time data input device 102, a property setting dialog box (setting screen) as shown in FIG. 12 is displayed.

In FIG. 12, the information that can be extracted from the property information of the button 702, that is, the property name and the property type, have already been displayed in the respective display boxes 801, 802, and 80 when this dialog is displayed.
It is desirable that the information is displayed at 4,805. The designer may input a desired text into the setting value input edit box 803 of the property name “data”. In this case, for example, if “1” is input, the button 70
The data displayed in 2 is “1”. In addition, a setting value input edit box 804 for the property name “character color”
The user can input a desired character color. In this case, for example,
If “black” is input, the character color “1” displayed on the button 702 is black.

By repeating the above, a screen image of the calculator as shown in FIG. 11 can be created.

(5-2) Design of Operation Scenario When the designer finishes designing the screen image, he or she designs the operation scenario. The design of the operation scenario in the present embodiment is performed by setting a link between software components (OCX) by, for example, operating a mouse. Here, "When an event occurs in one OCX, the other OCX
The message is called. " The link includes a link from the software component to the card in addition to the link from the software component to the software component. The latter case will be described later.

The setting of the link between the software components means, for example, in the case of FIG. 11, that the link is set from the button 702 to the calculation result display box 701 so that the button 702 is set.
Is pressed, the data displayed on the button 702 (that is, the attribute value of the button 702) “1” is substituted in the calculation result display box 701.

Next, with reference to a flowchart shown in FIG. 13, a link setting processing operation from the button 702 to the calculation result display box 701 will be described as an example.

The designer first selects the button 70 as a link source.
2 is selected, and "link" is selected from the card layout manager menu (CLMM) 200 of FIG. Next, a calculation result display box 701 to be a link destination is selected (step S11). Then, the CLM 109 displays a link setting dialog 900 as shown in FIG. 14 (Step S12).

In FIG. 14, the link setting dialog 9
00, the part name “button 1” of the button 702 and the part name “calculation result display box” of the calculation result display box 701 are already displayed in the display edit boxes 902 and 904 of the link source and the link destination, respectively. ing. Since the component name is registered in the registry 113 in correspondence with the identification information CLSID of the OCX, the component name may be read and displayed in the link source and link destination edit boxes 902 and 904.

First, the designer inputs a desired link name (anything that can be grasped by the designer) into the link name setting edit box 901. For example, here, “numeric substitution” is input (step S13).

Next, the event of the OCX which is the link source is selected. At this time, the event selection area 90 is selected.
Click the button indicated by the downward arrow on the right side of No.3. Then, an event selection list as shown in FIG. 15 is displayed (step S14).

The event selection list is stored in the table 114 as shown in FIG.
Read the event information registered corresponding to D,
This is displayed as a pull-down menu listing event names that can be selected for the OCX created by extracting the event names of each event information. The event name is
This is a general name of an operation that can be performed on the OCX. The button 702 has, for example, four pieces of event information. As shown in FIG. 15, the event names are "button down", "button up", "click", and "move".

The designer may select a desired event name from the event selection list shown in FIG. 15 (step S1).
5). Then, in the event selection area 903, the name of the selected event, for example, “button down” is displayed.

Next, an OCX message as a link destination is selected. At this time, a button indicated by a downward arrow on the right side of the message selection area 905 is clicked. Then, a message selection list as shown in FIG. 16 is displayed (step S16).

The message selection list is stored in the table 114 as shown in FIG.
The message information registered corresponding to the ID is read, and the message name of each message information is extracted and displayed as a pull-down menu displaying a list of selectable message names for the OCX. The message name is the OCX of the linked OCX.
Are general names of instruction commands that can be accepted. There are five message information items in the calculation result display box 701, for example, and as shown in FIG. 16, the message names are "number input", "addition", "subtraction", "multiplication", and "division".

The designer may select a desired message name from the message selection list shown in FIG. 16 (step S).
17). Then, in the message selection area 905, the name of the selected message, for example, “numeric input” is displayed. At this time, the CLM 109 determines whether there is an argument (argument list) from the selected message information stored in the table 114, and determines whether the message when calling a link destination requires an argument. For example, the argument setting button 906 becomes valid (for example, the argument setting button 906 changes from a non-display state to a display state). By pressing this button, a dialog for setting an argument of the message is displayed (step S18). After inputting necessary items in this dialog and setting arguments (step S19), the user finally presses an OK button 907 to complete link setting (step S2).
0). That is, a link having attributes such as a link name, a link source, a link destination, an event, and a message input in the link setting dialog shown in FIG. 14 is set.

The CLM 109 stores the set link information in the memory 106 and hides the link setting dialog.

Next, the procedure of the argument setting process in step S19 in FIG. 13 will be described with reference to the flowchart shown in FIG.

When the designer presses the argument setting button 906 of the link setting dialog of FIG. 14, an argument list dialog 1100 as shown in FIG. 18 is displayed (step S31).

As shown in FIG. 18, the argument list dialog 1100 displays the name of the previously selected message and an argument selection area 1101 for displaying a list of arguments of the message so as to be selectable. ing.

The list of arguments displayed in the argument selection area 1101 is created by the CLM 109 with reference to the argument list included in the message information of the previously selected message. For example, the argument name in the argument list Are listed.

Here, since the message “numeric input” in the calculation result display box 701, which is the OCX of the link destination, has one argument “numeric” from the message information, the argument selection area in FIG. In 1101, only the argument of “number” is displayed. Of course, when there are a plurality of arguments, all of them are displayed in the argument selection area 1101.

The designer selects the argument selection area 1101 in FIG.
Clicks the desired argument name, and furthermore, the setting button 11
When 02 is pressed (step S32), an argument setting dialog 1103 as shown in FIG. 19 is displayed (step S33).

The argument setting dialog 1103 is a dialog for determining what value should be set for the argument selected in the argument list dialog 1100.

As shown in FIG. 19, the argument setting dialog 1103 includes an argument name display edit box 110
4. In each of the argument type display edit boxes 1105, the argument name and the argument type read from the argument information in the table 114 by the CLM 109 are displayed. Here, it can be seen that an integer type (int) value is set in the argument “number”.

When setting a value for the argument, the designer selects whether to send a fixed value as an argument or to send an OCX property name as an argument value using the setting value switching radio button 1106 (step S34). . When sending a fixed value as an argument, the setting value input edit box 1107
A desired value (for example, “0”) is input to step S3.
5).

If the property (value) of the OCX is to be sent as an argument, a software component (OCX) property name is selected (steps S36 to S37).

First, a button indicated by a downward arrow on the right side of the component name selection area 1108 is clicked.
Then, a component name selection list as shown in FIG. 20 is displayed.

The component name selection list shown in FIG. 20 includes, as components whose properties can be used as arguments, “link source” and all component names (for example, FIG. 11) arranged on the card currently being designed. Is displayed as a pull-down menu displaying a list of all the OCX component names arranged on the card 703.

The designer may click and select a desired component name (for example, “link source”) from the component name selection list in FIG. Then, in the component name selection area 1108, the selected component name, for example, “link source” is displayed.

Next, in order to select a property name of the selected software component (OCX), a button indicated by a downward arrow on the right side of the property name selection area 1109 is clicked. Then, a property name selection list as shown in FIG. 21 is displayed.

The property name selection list shown in FIG.
The CLM 109 reads the property information of the selected software component from the table 114, and among the property names of the selected component, extracts the property name of the same type as the type displayed in the argument type display edit box 1105. It is displayed as a pull-down menu that is extracted and displayed as a list. For example, when “link source” is selected from the component name selection list, the OCX of the link source is selected.
Is a button 702, and the property names of the button 702 are "data" and "character color", but only "data" of the same type as the type displayed in the argument type display edit box 1105 is included. Is displayed in the property name selection list.

The designer may click and select a desired property name (for example, “data”) from the property name selection list in FIG. Then, in the property name selection area 1109, the selected property name, for example, “data” is displayed.

Finally, by pressing an OK button 1101, the setting of the arguments is completed.

The link setting from the software component (OCX) to the software component (OCX) has been described above. When a link is set from the software component to the card, for example, the button 702 is linked to another card. The case will be briefly described. That is, the designer first selects the link source button 702, and selects “link” from the card layout manager menu (CLMM) 200 in FIG. Next, the card to be linked to is displayed on the map viewer 20 as shown in FIG.
Select from 5. Then, the CLM 109 displays a link setting dialog as shown in FIG. The selection of the link source event is the same as described above. The difference from the link setting dialog displayed when setting the link between the software components described above is that when selecting the message of the link destination card, the CLM 109 creates the message without referring to the table 114. The selected message selection list is displayed. Therefore, a setting method that depends on the function of the CLM 109 can be considered when setting an argument required for the message. Since the specific setting method is not the gist of the present invention, the description is omitted.

(5-3) Many-to-many link setting FIG. 22 conceptually shows a link setting when a plurality of link sources and a plurality of link destinations are selected. For example, two links are set. If there is a source (part names “button 1” and “button 2”) and two link destinations (part names “button 3” and “button 4”), a single link setting operation causes a total of four
One link can be set. In this case, the event received by the link source, the message sent to the link destination, and the argument are common to all links. The same applies to a case where one of the link source and the link destination is plural (one-to-many, many-to-one).

Next, the procedure for setting such a many-to-many link will be described with reference to the flowcharts of FIGS. 13 and 17 only for differences from the above-described one-to-one link setting.

In step S11, the designer clicks and selects a plurality of software components (for example, component names "button 1" and "button 2") as link sources, and then selects a card layout manager menu shown in FIG. (CL
MM) 200 and select “Link”. Next, a plurality of software components to be linked (for example, component names “button 3” and “button 4”) are clicked and selected. In the link setting dialog displayed at this time, as shown in FIG. 23, in the link source display edit box 902, a plurality of selected software component names (that is, "button 1") are set as link source component names. And “Button 2”) are displayed, and the link destination display edit box 9 is displayed.
04 displays the selected software component names (ie, “Button 3” and “Button 4”) as the link destination component names.

In the event selection list displayed in step S14, when a plurality of link sources are selected, only the event names shared by the selected plurality of link source components are displayed. That is, the CLM 109 reads “button 1” from the table 114 as shown in FIG.
An event selection list is created by extracting only the event names common to the two components from the event information registered corresponding to the respective identification information CLSID of “Button 2”.

In the message selection list displayed in step S16, when a plurality of link destinations are selected, only the message names which the selected plurality of link destination parts have in common are displayed. That is, the CLM 109
From the table 114 as shown in FIG. 6, only the message name common to two parts of the message information registered corresponding to the respective identification information CLSID of “button 3” and “button 4” To create a message selection list.

When setting the argument, if the property name of the software component is used as the argument value in step S36 of FIG. 17, the “link source” is set in the component name selection area 1108 of the argument setting dialog of FIG. When the property name is selected, the property name selection list displayed when the property name is selected in the property name selection area 1109 is a property of the same type as the type displayed in the argument type display edit box 1105, and Only the property names that the link source of has in common are displayed. That is, CLM1
09 is displayed in the argument type display edit box 1105 among the property information registered corresponding to the respective identification information CLSIDs of “button 1” and “button 2” from the table 114 as shown in FIG. A property name selection list is created by extracting only property names that are the same type as the existing type and that are common to the two parts.

(6) Description of Prototype Execution Operation Finally, the UI design apparatus shown in FIG.
The prototype execution operation 3) will be described. This prototype execution operation is performed by the UI according to the instructions from the designer.
This is executed by the prototype execution unit 108 in the design mechanism 103. The state where the prototype is being executed is called a prototype execution mode.

In the prototype execution mode, the data processing designed by the editing unit 107 is all handled by the prototype execution unit 108. In the design mode (while the editing unit 107 is running), the CLM 109 in the editing unit 107 manages data as described above. In the prototype execution mode, the PTM (prototype manager) 111 in the prototype execution unit 108 Manages data recorded in the memory 106.

To switch from the design mode to the prototype execution mode, the designer operates the design-time data input device 102 (middle mouse) to operate the CLM shown in FIG.
The cursor may be moved to the item “execute prototype” in M200, clicked, and the “execute prototype” may be selected. In this case, the CLM 109 is a PTM 111
Start As a result, the PTM 111 sets the prototype manager menu (PTMM) 12 as shown in FIG.
01 is displayed on the display of the output device 101. The PTMM 1201 is displayed while the PTM 111 is running. The PTMM 1201 has items of “prototype execution”, “prototype suspension”, and “prototype end”.

In the prototype execution mode, when the designer operates the simulation input device 104 (middle mouse) and selects “prototype execution” from the PTMM 1201, the PTM 111 communicates with the hardware device in the simulation input device 104. And an event is given to the corresponding object via the PTM 111 according to the data input from the hardware device. As a result, a prototype (simulation) is executed.

Here, when any event is input, such as when a software component on the screen is clicked,
The message set in the link with the corresponding component as the link source is passed to the linked software component or card.

On the other hand, when “prototype suspension” is selected from the PTMM 1201, the PTM 111 switches to a state in which it does not accept an input from a hardware device, and suspends the prototype execution. When “execute prototype” is selected again in this state, the PTM 111 is released from a state in which an input from a hardware device is not accepted. Thus, the prototype is executed again.

Next, when “prototype end” is selected from the PTMM 1201, the PTM 111
9 is notified of the end, and the mode is changed to the design mode again.

[0112]

As described above, according to the present invention,
The image design and operation design of the GUI operation screen (user interface operation screen) can be easily performed by GUI (graphical user interface) operation (without having to write a program).

Further, general-purpose software components to be arranged on the GUI operation screen can be dynamically incorporated in the apparatus.

[Brief description of the drawings]

FIG. 1 is an exemplary view showing an example of a computer system as a user interface design device according to an embodiment of the present invention.

FIG. 2 is a schematic configuration diagram of a user interface design device.

FIG. 3 shows a card layout manager menu (CLM) displayed when the UI design mechanism of FIG. 2 is started.
M), a diagram showing an example of a screen image including a card layout window (CLMW) and a toolbar.

FIG. 4 is a diagram showing a display example of a map viewer.

FIG. 5 is a diagram illustrating an OCX index information (information about an event, a message, a method, and an attribute (property) possessed by the OCX;
Below, event information, message information, method information,
9 is a flowchart illustrating a processing operation of acquiring property information.

FIG. 6 is a diagram showing a storage example of index information in a table 114.

FIG. 7 is a diagram showing a configuration example of property information.

FIG. 8 is a diagram showing a configuration example of event information.

FIG. 9 is a diagram showing a configuration example of message information.

FIG. 10 is a diagram showing a configuration example of argument information.

FIG. 11 shows a specific example of a screen image being designed (GU of a calculator).
The figure which showed I).

FIG. 12 illustrates a software component (OC) to be arranged on a card.
The figure which showed an example of the property setting dialog displayed for setting the attribute (property) of X).

FIG. 13 is a flowchart for explaining a link setting processing procedure;

FIG. 14 is a diagram showing an example of a link setting dialog displayed when setting a link.

FIG. 15 is a diagram showing an example of an event selection list displayed when setting an event of a link source software component.

FIG. 16 is a diagram showing an example of a message selection list displayed when setting a message of a linked software component.

FIG. 17 is a flowchart for explaining a processing procedure when setting an argument of a message;

FIG. 18 is a diagram illustrating an example of an argument list dialog displayed when an argument of a message is set.

FIG. 19 is a view showing an example of an argument setting dialog displayed when an argument of a message is set.

FIG. 20 is a diagram illustrating an example of a component selection list displayed when selecting a software component when setting an attribute (property) of the software component to an argument value.

FIG. 21 is a diagram illustrating an example of a property selection list displayed when an attribute (property) is selected when an attribute (property) of a software component is set to an argument value.

FIG. 22 is a diagram conceptually showing link setting when a plurality of link sources and a plurality of link destinations are selected.

FIG. 23 is a view showing an example of a link setting dialog displayed when performing link setting when a plurality of link sources and a plurality of link destinations are selected.

FIG. 24 is a view showing an example of a prototype manager menu (PTMM) displayed in the prototype execution mode.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 101 ... Output device 102 ... Design time data input device 103 ... User interface design mechanism (UI design mechanism) 104 ... Input device 105 ... Database (DB) 106 ... Memory 107 ... Editing part 108 ... Prototype execution part 109 ... Card layout manager (CLM) 111 ... Prototype manager (PTM) 112 ... Server 113 ... Registry 114 ... Table 204 ... Tool bar

Claims (10)

[Claims] 1. Various software components are arranged at arbitrary positions on a card representing an operation screen of a user interface, and any of the software components is set as a link source, and another software component or card is set as a link destination. In a user interface design apparatus that designs an operation by associating the link source event with the link destination message and simulates the designed user interface, the attribute of the software component and the index information on the event and the message A reading unit that reads index information, a storage unit that stores the index information read by the reading unit, and, based on the index information stored in the storage unit,
First creating means for creating an event list of the software component of the link source; first setting means of setting an event selected based on the event list as an event of the software component of the link source; Second creating means for creating a message list of the software component of the link destination based on the index information stored in the means; and an event set in the software component of the link source based on the message selected based on the message list. And a second setting means for setting as a message of the software component of the link destination to be associated with the user interface design device. 2. A third creation method for creating a list of attributes of the software component selectable as an argument of a message set in the software component of the link destination based on the index information stored in the storage unit. 2. The apparatus according to claim 1, further comprising: a setting unit configured to set an attribute of the software component selected based on the list as an argument of a message of the software component of the link destination. User interface design equipment. 3. When there are a plurality of link-source software components, the first creating means creates an event list based on index information of an event which is stored in the storage means and which is shared by the plurality of software components. 2. The user interface design apparatus according to claim 1, wherein the user interface is created. 4. When there are a plurality of linked software components, the second creating means creates a message list based on index information of a message which is stored in the storage means and which the plurality of software components have in common. 2. The user interface design apparatus according to claim 1, wherein the user interface is created. 5. A third creation for creating a list of attributes of the software component selectable as an argument of a message set in the software component of the link destination based on the index information stored in the storage unit. Means, and third setting means for setting an attribute of the software component selected based on the list as an argument of a message of the software component of the link destination, wherein the third creating means comprises: 2. A list according to claim 1, wherein, when there are a plurality of link-source software components, a list is created based on index information of an attribute common to the plurality of link-source software components stored in the storage unit. User interface design apparatus according to the above. 6. Various software components are arranged at arbitrary positions on a card representing an operation screen of a user interface, and any of the software components is set as a link source, and another software component or card is set as a link destination. In a user interface design method for designing an operation by associating the link source event with the link destination message and simulating the designed user interface, the attribute of the software component and the index information on the event and the message And storing the read index information in the storage means, and creating an event list of the link source software component based on the index information stored in the storage means,
An event selected based on the event list is set as an event of the link source software component, and a message list of the link destination software component is created based on the index information stored in the storage means. A user interface design method, wherein a message selected based on the above is set as a message of the link destination software component that is associated with an event set in the link source software component. 7. A list of attributes of the software component selectable as an argument of a message of a software component of a link destination is created based on the index information stored in the storage unit, and a list of attributes of the software component is selected based on the list. 7. The user interface design method according to claim 6, wherein the attribute of the software component is set as an argument of a message of the software component of the link destination. 8. When there are a plurality of link-source software components, an event list is created based on index information of an event which is stored in the storage means and which is shared by the plurality of software components. Item 7. The user interface design method according to Item 6. 9. When there are a plurality of linked software components, a message list is created based on index information of a message stored in the storage means and shared by the plurality of software components. Item 7. The user interface design method according to Item 6. 10. When there are a plurality of link-source software components, the plurality of link-source software components are assigned to the link-destination software components on the basis of index information of attributes which the plurality of link-source software components have in common. Create a list of software component attributes that can be selected as an argument of the message to be set, and set the attribute of the software component selected based on this list as an argument of the message of the linked software component 7. The user interface design method according to claim 6, wherein: