JP3647888B2 - User interface processing system - Google Patents

Description

と定義する。これは、ウィンドウ１の位置、サイズ、タイトルを定義したものである。
【００３７】
▲２▼レイアウト情報２２は、

▲３▼処理定義情報２３は、

と定義する。これは、右側に記載したように、編集部品Ｘ３の入力データを示し、当該入力データを項目１として応用プログラム５に渡す。
【００３８】
レコード定義情報３は、図示のように設計して定義する。説明すると、

と定義する。これは、レコードＡの一覧に項目１は文字、項目２は数値を定義する。そして、この項目１、２を使って応用プログラム５との間でデータの授受を行なう。
【００３９】
次に、図５を用いてウィンドウ／部品の設計例を説明する。
図５において、表示装置６の画面上にウィンドウ１、編集部品、リスト部品、ボタンを図示のように設計する。
【００４０】
・ウィンドウ１は、位置、サイズ、ＸＸ業務（タイトルを表す）などを設計する（図４の▲１▼のウィンドウ定義情報、図６参照）。
・編集部品は、ウィンドウ、位置、サイズなどを設計する（図４の▲２▼のレイアウト情報２２、図７参照）。
【００４１】
・リスト部品は、ウィンドウ、位置、サイズなどを設計する（図４の▲２▼のレイアウト情報２２、図７参照）。
・ボタンは、ウィンドウ、位置、サイズなどを設計する（図４の▲２▼のレイアウト情報２２、図７参照）。
【００４２】
以上のようなウィンドウおよび当該ウィンドウ内に配置する編集部品、リスト部品およびボタンなどを画面上で会話的に設計する。以下説明する。
図６は、本発明のウィンドウ設計説明図を示す。これは、ウィンドウ属性画面上でウィンドウ属性を会話的に入力、選択して設計するものである。
【００４３】
・▲１▼の部品名には、部品を識別するための名前を入力する。
・▲２▼の索引番号は、一意の番号を入力する。
・▲３▼のタイトルには、ウィンドウの業務を行なうタイトルとして、図５の例では、“ＸＸ業務”を入力する。
【００４４】
・▲４▼の位置は、ウィンドウを表示する左上の原点を入力する。
・▲５▼の大きさは、ウィンドウの幅と高さを入力する。
・▲６▼の初期状態は、ウィンドウを最初に表示するときの状態（標準、最小化、最大化）を選択する。
【００４５】
・▲７▼のウィンドウスタイルは、以下から任意のものを選択する。
・サイズ変更：サイズ変更の可否
・水平スクロールバー：水平方向のスクロールバーの有無
・垂直スクロールバー：垂直方向のスクロールバーの有無
・システムメニュー：システムメニューの利用の有無
・最大化ボタン：最大化ボタンを付けるの有無
・最小化ボタン：最小化ボタンを付けるの有無
以上のように、ウィンドウ属性画面を表示し、この画面上でオペレータはウィンドウの属性▲１▼から▲７▼について入力／選択して設計する。これらの設計により、図５に示すウィンドウ１の位置、サイズ、ＸＸ業務などが設計され、既述した図４の▲１▼のウィンドウ定義情報２１が設計されたこととなる。
【００４６】
図７は、本発明のレイアウト設計説明図を示す。これは、図６の設計でウィンドウを生成した後、当該ウィンドウ内に配置する部品のレイアウトの設計を行なう。
【００４７】
図７の（ａ）は、編集ウィンドウ上で部品の位置、サイズを入力する様子を示す。編集ウィンドウを図示のように表示し、この編集ウィンドウの中で、部品を配置する位置にカーソルを位置づけてクリックした状態でドラッグして当該部品のサイズを入力する。
【００４８】
図７の（ｂ）は、ボタン属性画面を示す。これは、ボタン属性画面上で部品であるボタンの属性を会話的に入力、選択して設計するものである。
・▲１▼の部品名は、部品であるボタンを識別する部品名ここでは“Ｘ１”を入力する。
【００４９】
・▲２▼の索引番号は、一意の番号を入力する。
・▲３▼の配色は、色と内部様式を入力する。これは、画面や部品の文字の色や背景色と、ハッチングパターンなどを指定する。
【００５０】
・▲４▼のテキストは、ボタンの位置に表示するテキストここでは“確定”を入力する。
・▲５▼の位置は、ボタンを表示する左上の原点を入力する。
【００５１】
・▲６▼の大きさは、ボタンの幅と高さを入力する。
・▲７▼の初期状態は、ウィンドウを最初に表示するときの状態（標準、最小化、最大化）を選択する。
【００５２】
・▲８▼の処理定義は、ＣＬＩＣＫを入力する。
以上のように、編集ウィンドウ画面を表示し、この画面上でオペレータはボタンの属性▲１▼から▲８▼について入力／選択して設計する。これらの設計により、図５に示すウィンドウ１中のボタン“確定”が設計されたこととなる（実際に実行する処理内容は図８で定義する）。
【００５３】
図８は、本発明の処理定義説明図を示す。これは、図７のボタンの設計中で定義した処理定義について実際の処理の設計を行なう。
ここでは、ボタンＸ１について、図示の下記のように処理を設計する。
【００５４】
Ｘ１．ＣＬＩＣＫ（）
・編集部品から“商品Ａ”を取り出し、項目１に代入
・送出
これは、編集部品から商品Ａを取り出し、項目１に代入して、応用プログラム５に送出する。そして、応用プログラム５はこの項目１から商品Ａを取り出して自身の内部に取り込み、業務処理を行なう。
【００５５】
以上のように、処理定義ウィンドウ画面を表示し、この画面上でオペレータはボタンの処理定義を設計する。これらの設計により、図５に示すウィンドウ１中のボタン“確定”の処理が図４の▲３▼の処理定義情報２３中の処理１に示すように設計されたこととなる。
【００５６】
図９は、本発明のレコード定義説明図を示す。これは、応用プログラム５との間でデータを授受を行なうための項目の設計を行なう。
レコード定義画面を表示し、この画面の中でレコード、例えばレコードＡを選択すると、当該レコードＡの項目の一覧が図示のよう表示される。この一覧の中に、新たに定義しようとする項目名、属性を図示のように追加入力して定義する。これにより、応用プログラム５とユーザインタフェース実行部４との間で当該項目名にデータを代入して授受することが可能となる。
【００５７】
次に、図２から図９によって画面上で会話的に設計したユーザインタフェース記述情報２およびレコード定義情報３をもとに、応用プログラム５が表示された図５のウィンドウ１上との間でデータの入出力を行なう例として、応用プログラム５がＲＥＡＤ要求を発行したときの動作を詳細に説明する。
【００５８】
図１０において、Ｓ２１は、オペレータが動作指示を行なう。この際に、ウィンドウファイル名“ファイルＡ”を指定して動作指示を行なう。
Ｓ２２は、ユーザインタフェース実行部４がＳ２１で指示された“ファイルＡ”からユーザインタフェース記述情報２を取り出し、ウィンドウを表示する。例えば図５のウィンドウ１（タイトル“ＸＸ業務）を表示する（図４の▲１▼ウィンドウ定義情報２１に従ってウィンドウ１を表示する）。
【００５９】
Ｓ２３は、レイアウト情報に従って部品を表示する。ここでは、図５に示すように、
・ボタン
・リスト部品
・編集部品
をそれぞれ表示する（図４の▲２▼レイアウト情報２２に従ってボタン、リスト部品、編集部品を表示する。
【００６０】
Ｓ２４は、Ｓ２３で図５に示すようにウィンドウ１中にボタン、リスト部品、編集部品を表示した状態で、応用プログラム５がレコードＡのＲＥＡＤ要求を発行する。
【００６１】
Ｓ２５は、オペレータがＳ２４のＲＥＡＤ要求に対応して、編集部品に入力“商品Ａ”を行なう。
Ｓ２６は、Ｓ２５で入力された編集部品“商品Ａ”を保持する。
【００６２】
Ｓ２７は、オペレータが“確定”ボタンを押下する。
Ｓ２８は、“確定”ボタンの処理“処理１”を起動する。これは、図４の▲２▼のレイアウト情報２２のＸ１の“確定”ボタンが押下されたことに対応して、処理１を起動する。
【００６３】
Ｓ２９は、Ｓ２８で起動された処理１が処理として、ここでは、保持データ“商品Ａ”をレコードＡの項目１に設定し、応用プログラム５に送る。
Ｓ３０は、通知を受けた応用プログラム５がデータをレコードＡの項目１から“商品Ａ”を得る。そして、応用プログラム５は、このＲＥＡＤ要求の発行に対応して受け取った“商品Ａ”をもとに業務処理を実行する。
【００６４】
以上によって、オペレータがウィンドウファイル名を指定したことに対応して、該当するユーザインタフェース記述情報２に従ってウィンドウおよび当該ウィンドウ内に編集部品、リスト部品、ボタンを表示する。この表示された状態で、応用プログラム５が入出力要求、ここではＲＥＡＤ要求を発行したことに対応し、表示されたウィンドウ上から入力された“商品Ａ”を保持し、ウィンドウ上のボタン“確定”が押下されたことに対応して、当該ボタン“確定”の処理１によって保持している“商品Ａ”を指定されたレコードＡの項目１に設定して応用プログラム５に渡し、応用プログラム５はレコードＡの項目１から渡された“商品Ａ”を取り込み、業務処理を行なうことが可能となる。
【００６５】
【発明の効果】
以上説明したように、本発明によれば、画面上から会話的に入力されて設計されたウィンドウ定義情報（位置、サイズなど）２１、部品やボタンなどのレイアウト情報（位置、サイズなど）２２、および処理の処理定義情報２３をユーザインタフェース記述情報２として保存、および画面上から会話的に入力されて設計された、応用プログラム５との入出力時に使う項目名をレコード定義情報３として保存し、これら保存した情報をもとにウィンドウ上に表示して応用プログラム５との間で入出力を行なう構成を採用しているため、ウィンドウシステムの詳細な知識を必要としなく、会話的にユーザインタフェース記述情報２およびレコード定義情報３を作成するができると共に、応用プログラム５とユーザインタフェースとをそれぞれ独立に設計することができ、しかも、設計後に自由にユーザインタフェース部分を変更することが容易にできる。これらにより、ユーザインタフェースを持つ応用プログラム５を短期間に開発することが可能となった。
【図面の簡単な説明】
【図１】本発明の原理構成図である。
【図２】本発明のユーザインタフェース記述情報／レコード定義情報の生成フローチャートである。
【図３】本発明の部品の設計フローチャートである。
【図４】本発明のユーザインタフェース記述情報／レコード定義情報例である。
【図５】本発明のウィンドウ／部品の設計例である。
【図６】本発明のウィンドウ設計説明図である。
【図７】本発明のレイアウト設計説明図である。
【図８】本発明の処理定義説明図である。
【図９】本発明のレコード定義説明図である。
【図１０】本発明の実行時の動作フローチャートである。
【図１１】従来技術の説明図である。
【符号の説明】
１：ユーザインタフェース生成機能
２：ユーザインタフェース記述情報
２１：ウィンドウ定義情報
２２：レイアウト情報
２３：処理定義情報
３：レコード定義情報
４：ユーザインタフェース実行部
５：応用プログラム
６：表示装置
７：ウィンドウ[0001]
[Industrial application fields]
The present invention relates to a user interface processing system that performs input / output using a screen.
[0002]
Today, computers are being used in an increasing number of fields, and the computers themselves are becoming easier to use. In particular, the user interface part of a computer is a part that comes into contact with humans, and it is easy to use, such as inputting data into the computer and selecting the computer from the main character, by selecting a graphic icon or the like with a mouse. ing. However, the burden on the program developer is increased because the user becomes easier to use. It is difficult to develop a GUI part (Graphical User Interface part) program that realizes a user interface using graphics, and it takes more man-hours to develop the GUI part than the original processing, significantly reducing the productivity of the program. Is the current situation. Therefore, there is a demand for constructing user interface processing as easily as possible and using it from an application program.
[0003]
[Prior art]
Conventionally, user interface processing has been described as part of the application program as shown in (1) of FIG. Most of the description of the user interface processing is made by using an interface provided by each window system. The description required detailed knowledge of the window system and advanced programming knowledge even if it was going to be simple.
[0004]
Recently, as shown in (2) of FIG. 11, a tool kit called “tool kit” capable of realizing a somewhat simple GUI has been realized. Still, unless you were a highly skilled programmer, you could not master it.
[0005]
Further, as shown in (3) of FIG. 11, a mechanism for generating a program for the GUI layout part called a GUI construction tool has been realized. However, a source program is generated, and subsequent programming is performed once. Once the target program is created, it cannot be replaced by the layout construction tool, which is very inconvenient for the user.
[0006]
Also, as shown in (4) of FIG. 11, when a language GUI development environment with a built-in GUI construction tool is used, GUI construction can be easily performed, but data exchange with application programs, in particular, When communication is present between the application program and the GUI environment, it is necessary to determine the interface and to program the processing of the communication part, which requires a lot of labor.
[0007]
[Problems to be solved by the invention]
As described above, in order to develop the GUI part according to (1) to (4) in FIG. 11, detailed knowledge of the window system is required, and it is also necessary to create a user interface by working on the application program. There was a problem that there was.
[0008]
In order to solve these problems, the present invention does not require detailed knowledge of the window system, interactively creates user interface description information and record definition information, and independently designs and designs application programs and user interfaces. It is intended to make changes possible.
[0009]
[Means for Solving the Problems]
FIG. 1 shows a principle configuration diagram of the present invention.
In FIG. 1, a user interface generation function 1 includes window definition information (position, size, etc.) 21 designed by interactive input from the screen, layout information (position, size, etc.) 22 such as parts and buttons, and the like. The process definition information 23 of the process is stored as the user interface description information 2, and the item name used when inputting / outputting with the application program 5 that is designed by interactive input from the screen is stored as the record definition information 3. It is something to do.
[0010]
The user interface execution unit 4 displays a window on the screen according to the window definition information 21 of the saved user interface description information 2, displays parts and buttons in this window according to the layout information 22, and displays these In response to the input / output request using the item name defined in the record definition information 3 from the application program 5, the processing definition information of the selected part or button displayed on the screen or the selected part or button is displayed. 23, data is transferred to the application program 5 by the item name, or data is displayed at the position of the corresponding item name.
[0011]
[Action]
As shown in FIG. 1, according to the present invention, window definition information (position, size, etc.) 21 designed by interactive input from the user interface generation function 1 on the screen, layout information (position, (Such as size) 22 and the process definition information 23 of the process are stored as the user interface description information 2, and the item name used when inputting / outputting with the application program 5 designed by interactive input from the screen is recorded. The definition information 3 is stored.
[0012]
The application program 5 is displayed with the user interface execution unit 4 displaying a window on the screen according to the window definition information 21 of the saved user interface description information 2 and displaying parts and buttons in the window according to the layout information 22. In response to the input / output request using the item name defined in the record definition information 3 from the component, the input of the component or button displayed on the screen / the processing definition information 23 of the selected component or button is followed. By processing, data is passed to the application program 5 by the item name, or data is displayed at the position of the corresponding item name.
[0013]
Therefore, the application program 5 and the user interface can be designed independently by creating the user interface description information 2 and the record definition information 3 interactively without requiring detailed knowledge of the window system. At the same time, the user interface portion can be easily changed after design. Thus, the application program 5 having a user interface can be developed in a short time.
[0014]
【Example】
Next, the configuration and operation of the embodiment of the present invention will be sequentially described in detail with reference to FIGS.
[0015]
FIG. 1 shows a principle configuration diagram of the present invention.
In FIG. 1, a user interface generation function 1 is for interactively designing a user interface on a screen displayed on a display device 6 and generating and storing user interface description information 2 and record definition information 3 ( (See FIGS. 2 and 3). The user interface description information 2 includes window definition information 21, layout information 22, and process definition information 23.
[0016]
The window definition information 21 defines a window to be displayed on the display device 6, and defines a window position, size, title, and the like (see FIGS. 4, 5, and 6).
[0017]
The layout information 22 is information defined by designing and defining the layout of buttons and parts arranged in the window (see FIGS. 4 and 7).
The process definition information 23 is information that defines a process activated from a component or button (see FIGS. 4 and 8).
[0018]
The record definition information 3 defines item names of records used between the application program 5 and the user interface (see FIGS. 4 and 9).
The user interface execution unit 4 analyzes (translates) the user interface description information 2 at the time of execution and executes predetermined processing, or uses the item name defined in the record definition information 3 with the application program 5 to perform data And so on (see FIG. 10).
[0019]
The application program 5 uses the item name defined in the record definition information 3 to request the user interface execution unit 5 to input data from the screen and receive the input data. Is to do.
[0020]
The display device 6 displays a window 7 and the like.
The window 7 is a window provided on the display device 6, and here is for performing various inputs / outputs using the window.
[0021]
Next, the operation when the user interface description information 2 and the record definition information 3 in the configuration of FIG. 1 are designed and registered in the order shown in FIG. 2 will be described in detail.
[0022]
In FIG. 2, in S1, the operator designs a window. Here, as the window design, the window size, position, title, etc. are input interactively or selected from the screen (detailed with reference to FIG. 6).
[0023]
In S2, the window information (size, position, title, etc.) designed by the operator interactively inputting or selecting on the screen in S1 is held.
In S3, the operator designs parts. Here, as part design, the size, position, echo, etc. of parts (parts such as editing parts, list parts, buttons) are interactively input or selected from the screen (see FIGS. 3 and 7). And will be described in detail).
[0024]
In S4, information (size, position, echo, etc.) of the parts designed by the operator interactively inputting or selecting on the screen in S3 is held.
In S5, the operator designs a record. Here, in order for the application program 5 and the user interface execution unit 4 to exchange data, the data structure of the record is defined and designed in advance, and a list of items of the record is made.
[0025]
In S6, the record definition (list of items for each record) designed by the operator interactively inputting or selecting on the screen in S5 is held.
S7 instructs registration of information held by the operator.
[0026]
In S8, user interface information 2 and record definition information 3 are generated. This way, as described on the right side,
-User interface description information 2
-Window definition information 21
Layout information 22
Process definition information 23 (designed together with the design of the part in S3, see FIGS. 7 and 8)
Record definition information 3
This means that registration has been performed.
[0027]
S9 links the record definition information 3 to the application program 5. As a result, the application program 5 can send / receive data by making an input / output request using the item name defined in the record definition information 3. Therefore, thereafter, the application program 5 uses the item names defined in the record definition information 3 to capture data from the screen, display data on the screen, and output data to the outside. In other words, the application program 5 can be created independently, and there is no need to worry about user interface description information inside the interface execution unit 4.
[0028]
Thus, the operator can interactively perform window design, part design, and record definition on the screen in order under the control of the user interface generation function 1 to create the user interface description information 2 and the record definition information 3. It becomes possible. When these designs are completed, the application program 5 can arbitrarily input / output using the item names in the record definition information 3 to describe and execute the business process independently, and execute the user interface. Since the user interface description information 2 is interpreted / translated and executed under the control of the unit 4, the user interface description information 2 is arbitrarily changed / added independently to perform function changes / additions independently. It becomes possible. Details will be sequentially described below.
[0029]
FIG. 3 shows a product design flowchart of the present invention. This is a detailed flowchart of the product design in S3 of FIG.
In FIG. 3, S11 designs an editing part. In this case, the operator interactively designs the edit part, such as the size, position, echo control, etc. as the design of the edit part on the screen.
[0030]
In step S12, a list part is designed. This is because the operator interactively designs the list parts on the screen such as the size, position, scroll bar control, etc. of the list parts.
[0031]
In step S13, a button part is designed. The operator interactively designs button parts such as size, position, process definition, etc. as button parts on the screen.
[0032]
S14 holds information designed interactively on the screen in S11, S12 and S13. Then, in S7 of FIG. 2, the layout information 22 and the process definition information 23 of the user interface description information 2 are generated.
[0033]
As described above, the operator interactively designs editing parts, list parts, buttons, and the like on the screen, and the designed information is generated as the layout information 22 and the process definition information 23 of the user interface description information 2 in FIG.
[0034]
FIG. 4 shows an example of user interface description information / record definition information according to the present invention. This is an example of the user interface description information 2 and the record definition information 3 designed interactively on the screen according to FIGS. 2 and 3.
[0035]
As user interface description information 2,
(1) Window definition information 21
(2) Layout information 22
(3) Process definition information 23
Is designed and defined as shown. This will be described below.
[0036]
(1) Window definition information 21 is

It is defined as This defines the position, size, and title of the window 1.
[0037]
(2) Layout information 22 is

(3) The process definition information 23 is

It is defined as This indicates the input data of the editing part X3 as described on the right side, and the input data is passed to the application program 5 as item 1.
[0038]
The record definition information 3 is designed and defined as shown. To explain

It is defined as In the list of records A, item 1 defines a character and item 2 defines a numerical value. Then, data is exchanged with the application program 5 using these items 1 and 2.
[0039]
Next, a window / part design example will be described with reference to FIG.
In FIG. 5, a window 1, an editing part, a list part, and a button are designed on the screen of the display device 6 as shown.
[0040]
Window 1 designs position, size, XX work (represents title), etc. (see window definition information (1) in FIG. 4, FIG. 6).
The editing parts are designed with respect to the window, position, size, etc. (see layout information 22 in (2) of FIG. 4, FIG. 7).
[0041]
The list parts are designed for window, position, size, etc. (see layout information 22 in (2) of FIG. 4, FIG. 7).
-The buttons design the window, position, size, etc. (see layout information 22 in (2) in FIG. 4, FIG. 7).
[0042]
The window as described above and edit parts, list parts, buttons, and the like arranged in the window are interactively designed on the screen. This will be described below.
FIG. 6 shows a window design explanatory diagram of the present invention. This is designed by interactively inputting and selecting window attributes on the window attribute screen.
[0043]
・ Enter a name to identify the part in the part name of (1).
・ Enter a unique number for index number (2).
In the title of (3), “XX business” is input in the example of FIG. 5 as the title for performing the business of the window.
[0044]
・ For the position of (4), input the origin at the upper left to display the window.
-For the size of (5), enter the width and height of the window.
-For the initial state of (6), select the state (standard, minimized, maximized) when the window is first displayed.
[0045]
・ Select any of the following 7 window styles.
-Size change: Whether the size can be changed-Horizontal scroll bar: Whether there is a horizontal scroll bar-Vertical scroll bar: Whether there is a vertical scroll bar-System menu: Whether the system menu is used-Maximize button: Maximize button Presence / absence / minimization button: Displaying the window attribute screen as described above, whether or not the minimization button is added. On this screen, the operator inputs / selects window attributes (1) to (7). design. With these designs, the position, size, XX work, etc. of the window 1 shown in FIG. 5 are designed, and the window definition information 21 shown in FIG.
[0046]
FIG. 7 shows a layout design explanatory diagram of the present invention. In this case, after a window is generated in the design of FIG. 6, the layout of the components arranged in the window is designed.
[0047]
FIG. 7A shows a state in which the position and size of a part are input on the editing window. An edit window is displayed as shown in the figure. In this edit window, the cursor is positioned at the position where the part is to be placed and clicked and dragged to input the size of the part.
[0048]
FIG. 7B shows a button attribute screen. This is designed by interactively inputting and selecting button attributes which are parts on the button attribute screen.
As the part name of (1), “X1” is input here, which is a part name for identifying a button as a part.
[0049]
・ Enter a unique number for index number (2).
・ Enter the color and internal style for (3) color scheme. This specifies the character color and background color of the screen and parts, and the hatching pattern.
[0050]
-For the text of (4), the text to be displayed at the position of the button.
・ For the position of (5), input the origin at the upper left to display the button.
[0051]
・ For the size of (6), enter the width and height of the button.
-The initial state of (7) selects the state (standard, minimized, maximized) when the window is first displayed.
[0052]
-CLICK is input as the process definition of (8).
As described above, the editing window screen is displayed. On this screen, the operator inputs / selects the button attributes (1) to (8) for designing. With these designs, the button “OK” in the window 1 shown in FIG. 5 is designed (the processing contents to be actually executed are defined in FIG. 8).
[0053]
FIG. 8 shows a process definition explanatory diagram of the present invention. In this case, an actual process is designed for the process definition defined in the button design of FIG.
Here, the process for the button X1 is designed as shown below.
[0054]
X1. CLICK ()
“Product A” is taken out from the editing part and assigned / sent to item 1 This takes out product A from the editing part, substitutes it into item 1, and sends it to the application program 5. Then, the application program 5 takes out the product A from this item 1 and takes it in itself to perform business processing.
[0055]
As described above, the process definition window screen is displayed, on which the operator designs the button process definition. With these designs, the processing of the button “confirm” in the window 1 shown in FIG. 5 is designed as shown in the processing 1 in the processing definition information 23 of (3) in FIG.
[0056]
FIG. 9 shows a record definition explanatory diagram of the present invention. This is to design items for exchanging data with the application program 5.
When a record definition screen is displayed and a record such as record A is selected on this screen, a list of items of the record A is displayed as shown in the figure. In this list, an item name and an attribute to be newly defined are additionally input and defined as shown. Thereby, it is possible to exchange data by assigning data to the item name between the application program 5 and the user interface execution unit 4.
[0057]
Next, based on the user interface description information 2 and the record definition information 3 designed interactively on the screen according to FIGS. 2 to 9, data is transferred to and from the window 1 of FIG. 5 in which the application program 5 is displayed. As an example of inputting / outputting, the operation when the application program 5 issues a READ request will be described in detail.
[0058]
In FIG. 10, in S21, the operator gives an operation instruction. At this time, the window file name “file A” is designated to give an operation instruction.
In S22, the user interface execution unit 4 extracts the user interface description information 2 from the “file A” instructed in S21, and displays a window. For example, window 1 (title “XX business”) in FIG. 5 is displayed (window 1 is displayed in accordance with (1) window definition information 21 in FIG. 4).
[0059]
In step S23, the component is displayed according to the layout information. Here, as shown in FIG.
Buttons, list parts, and edit parts are respectively displayed ((2) in FIG. 4) Buttons, list parts, and edit parts are displayed according to the layout information 22.
[0060]
In S24, the application program 5 issues a READ request for the record A in a state where buttons, list parts, and edit parts are displayed in the window 1 as shown in FIG. 5 in S23.
[0061]
In S25, in response to the READ request in S24, the operator inputs “product A” to the editing part.
In S26, the edited part “product A” input in S25 is held.
[0062]
In S27, the operator presses the “OK” button.
In S28, the “confirm” button process “process 1” is activated. This activates the process 1 in response to the pressing of the “confirm” button X1 in the layout information 22 of (2) in FIG.
[0063]
In S29, the process 1 started in S28 is set as the process. Here, the retained data “product A” is set in the item 1 of the record A and sent to the application program 5.
In S30, the application program 5 that has received the notification obtains “product A” from the item 1 of the record A. Then, the application program 5 executes the business process based on the “product A” received in response to the issue of the READ request.
[0064]
As described above, in response to the operator specifying the window file name, the window and the editing parts, list parts, and buttons are displayed in the window according to the corresponding user interface description information 2. In this displayed state, in response to the application program 5 issuing an input / output request, here a READ request, the “product A” input from the displayed window is held and the button “OK” on the window is confirmed. In response to the “press”, the “product A” held by the processing “1” of the button “confirm” is set in the item 1 of the designated record A and passed to the application program 5, and the application program 5 Can receive the “product A” passed from the item 1 of the record A and perform business processing.
[0065]
【The invention's effect】
As described above, according to the present invention, window definition information (position, size, etc.) 21 designed by interactive input from the screen, layout information (position, size, etc.) 22 such as parts and buttons, And the process definition information 23 of the process is stored as the user interface description information 2, and the item name used at the time of input / output with the application program 5 designed interactively from the screen is stored as the record definition information 3, Based on the stored information, it is displayed on the window and input / output to / from the application program 5 is adopted. Therefore, detailed knowledge of the window system is not required, and the user interface description is interactively performed. Information 2 and record definition information 3 can be created, and application program 5 and user interface are independent of each other. It can be designed, moreover, can easily be freely change the user interface portion after design. Thus, the application program 5 having a user interface can be developed in a short time.
[Brief description of the drawings]
FIG. 1 is a principle configuration diagram of the present invention.
FIG. 2 is a generation flowchart of user interface description information / record definition information according to the present invention.
FIG. 3 is a flow chart for designing a part according to the present invention.
FIG. 4 is an example of user interface description information / record definition information according to the present invention.
FIG. 5 is a window / part design example of the present invention.
FIG. 6 is an explanatory diagram of a window design according to the present invention.
FIG. 7 is an explanatory diagram of a layout design of the present invention.
FIG. 8 is a process definition explanatory diagram of the present invention.
FIG. 9 is an explanatory diagram of record definition according to the present invention.
FIG. 10 is an operation flowchart at the time of execution of the present invention.
FIG. 11 is an explanatory diagram of a conventional technique.
[Explanation of symbols]
1: User interface generation function 2: User interface description information 21: Window definition information 22: Layout information 23: Process definition information 3: Record definition information 4: User interface execution unit 5: Application program 6: Display device 7: Window

Claims (1)

In the user interface processing system for inputting and outputting with the screen,
Window definition information including a position and size corresponding to information for identifying a window (hereinafter referred to as a window identifier ) , and a window identifier, position, size, and processing corresponding to information for identifying a component (hereinafter referred to as a component identifier ) Process definition information including component information and data corresponding to layout information including information to be performed (hereinafter referred to as process identifier ) and information for identifying an item used in a predetermined process identified by the process identifier (hereinafter referred to as item identifier ) User interface description information storage means for storing,
Record definition information storage means for storing record definition information including a record name, an item identifier, and an attribute used when inputting / outputting with an application program;
Means for displaying a window based on the window definition information;
Means for displaying a part in the window based on the layout information;
Means for executing processing corresponding to the component based on the layout information;
A user interface processing system, comprising: means for exchanging data between an item identifier of the process definition information and an item identifier of the record definition information when executing a process corresponding to the component.

Images