JPH04335430A - Program editing device - Google Patents

Abstract

PURPOSE:To execute the program editing which can set easily a window attribute and can execute interactive editing. CONSTITUTION:An editing mode 100 is provided with a window attribute selecting means 101 for selecting an attribute of a generated window, an event corresponding attribute selecting means 102 for selecting the processing in the case of selecting the processing in the case the attribute selection of this window generates an event, a non-event corresponding attribute input means 103 for inputting a selected attribute value, in the case other selection than the processing related to generation of the event is executed, and a window display means 104 for displaying the contents executed by this non-event corresponding attribute input means 103, and the event corresponding attribute selecting means 102, and a coding mode 200 is provided with a coding means 201 for executing the coding of a program, and executes program editing of an event driving type.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event-driven program editing device comprising an event procedure activated by an event occurring within a generated window and a main procedure that calls the event procedure.

0002

2. Description of the Related Art Conventionally, event-driven programs have been used as window processing programs. FIG. 2 is a diagram schematically showing an event-driven program. The event-driven program is composed of a loop that receives events and a processing section that performs processing based on the received events. For example, this is a program that executes a process when an event occurs, such as when a keyboard is pressed (event occurrence), a beep sound is heard (processing).

[0003] In order to generate a program that includes such window processing, it is necessary to be familiar with what attributes can be set for the window to be generated. These attributes include visual attributes and event processing attributes. Visual attributes include window width, height, background color, etc., and event processing attributes include, for example, when the mouse is clicked once. processing when mouse 1 and mouse 2 are clicked at the same time, etc. In the program, coding is performed to set appropriate values for these attributes.

0004

[Problem to be Solved by the Invention] When creating a program that includes window processing in this way, it is necessary to be familiar with what attributes can be set for the generated window, and the program Among them, setting appropriate values for window attributes required a large amount of coding, which was tedious. In addition, many of these attributes are used to determine the visual aspects, so when you run the program you created, you may find that the window that you intended is not generated, or that the color scheme of the window is unbalanced. This caused the problem that there were some parts that could not be determined based on the program alone. Furthermore, there was a problem in that it was necessary to manipulate several types of tables in order to implement a certain process.

The present invention has been made in view of the above-mentioned problems, and it eliminates the complexity of setting window attributes and operating various tables when editing an event-driven program, and makes it possible to check the graphical user interface. The present invention aims to provide a window editing device that enables interactive creation and editing of window-related parts.

[0006]

[Means for Solving the Problems] FIG. 1 is a diagram showing the principle of the present invention. Editing mode 100 and coding mode 200
The editing mode 100 includes window attribute selection means 101 for selecting the attributes of the window to be generated.
and, when the attribute selection of this window selects a process when an event occurs, the event corresponding attribute selection means 102 selects the process; and the attribute selection selects a process other than the process when an event occurs. non-event compatible attribute input means 10 for inputting the attribute value to be selected
3, this non-event corresponding attribute input means 103, and a window display means 104 that displays a window based on the contents performed by the event corresponding attribute selection means 102.
The coding mode 200 occurs when the event-corresponding attribute selection means 102 selects a procedure editing item, and includes a coding means 201 for coding a program.

[0007] Furthermore, the window attribute selection means 101
consists of a component window for selecting basic attributes including event processing attributes and visual attributes, and an attribute setting menu for selecting detailed attributes of the basic attributes selected in this component window.

[0008] Furthermore, a visualization mode having a visualization area for displaying a window generated by an input event-driven program is provided.

Furthermore, the event-driven program input in the visualization mode is edited.

0010

[Operation] In the window editing mode 100, when the window attribute selection means 101 on the display selects the process to be performed when an event occurs, the selections made by the event corresponding attribute selection means 102, for example, the name of a registered procedure. and an item for editing a procedure are displayed. When a registered procedure name is selected, that procedure is set. When a procedure editing item is selected, the coding mode 200 is entered. Further, when an attribute other than processing when an event occurs, for example, an attribute such as a visual attribute such as a window size or a background color, is selected, the non-event compatible attribute input means 103
is displayed and enter the attribute value. The window whose attributes have been selected in this way is displayed in the window display means 104.
will be displayed. In the coding mode 200, the area to be coded is displayed by the coding means 201, and the program is coded using the keyboard.

Furthermore, the window attribute selection means 101 is provided with a component window for selecting basic attributes such as event processing attributes and visual attributes, and an attribute setting menu for selecting the attributes selected in this component window in more detail. Attributes can be easily selected.

Furthermore, by inputting and visualizing a created event-driven program in the visualization mode, it is possible to visualize the created program, and the graphical user interface can be verified.

[0013] Furthermore, it is possible to edit the attributes of this visualized window and to reflect the edited items in the input program.

[0014]

Embodiments Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 3 is a diagram showing the basic configuration of the interface image of this embodiment. In forming a window, it holds various attributes such as visual ones such as color, size and display position, and qualitative ones such as whether it can become a parent window or what to do when an event occurs. ing. Therefore, we will refer to the window framework defined by which attributes are retained and what values are set as default values as part windows, and we will discuss the framework decided here in more detail. An attribute setting menu is provided to define the contents.

In the window editing mode, a component window, an attribute setting menu for setting attributes for the window to be generated, and a window display area for displaying the window to be edited are displayed (step 1). In step 1, when the user selects the item of the process to be activated when an event occurs in the attribute setting menu, the event/procedure selection menu consisting of the registered procedure name and the item for editing the procedure is displayed. Display (Step 2). Here, when a registered procedure name is selected by the user, that procedure is set, and when a procedure editing item is selected by the user, the coding mode is entered. Here, the procedure editing items are:
This item is used to create and edit procedures to perform processing in order to set what processing will be performed when an event occurs in a window. To give a concrete example, when an event in which mouse 1 is clicked on a window occurs, the process of closing that window is written in a programming language. Step 1
, when the user selects an item in the attribute setting menu that requires input of an attribute value, the input is prompted (
Step 3), wait for input by the user.

In the coding mode, an area for coding the program is displayed (step 4).
. The user codes the program using the keyboard.

In the visualization mode, first an area for inputting a program name is displayed (step 5), and an input by the user is awaited. When the program name is input, the program is analyzed and windows generated in the program are visualized (step 6).

FIG. 4 is a block diagram showing the configuration of this embodiment. In FIG. 4, the attribute master 7 stores in advance what attributes the component window holds. The interface section 8 displays on the display a window editing mode, a coding mode,
Arrange windows to be displayed in visualization mode as appropriate and control user editing operations.

When a source program is input, the program analysis section 9 first creates intermediate code for use in the editing device for the main procedure. FIG. 5 is a diagram showing the relationship between a source program, a main procedure, and an event procedure. The main procedure corresponds to the loop section in FIG. 2, and the event procedure corresponds to the processing section in FIG. 2.

FIG. 6 shows a method of displaying a program used in the editing device, and is displayed using an intermediate code and a scene number that is one of the intermediate codes. A scene number is a number assigned to a program portion that describes the same window, and is set each time the contents of the window differ, and is, so to speak, an index of the window description. Regarding the windows generated in the program, labeling is performed, the component window is specified, and the attribute master 7 that has a list of component window attributes is referred to for the component window, and the individual attributes of the window are determined. Initializes the source/attribute table 21 for setting values, and creates the source/attribute table 2 from the attribute values set in the program.
Create 1. The label of a window represents the identification number (ID) of that window.

[0021] Starting from the part of the program where the event procedure is set, the source code for matching the procedure to be activated in response to the event is created for each window.
Create an event procedure table 22. A scene management table 16 is created that has a correspondence between scene numbers and corresponding window labels. Parts window, source/attribute table 2 corresponding to window/label
1. Source event procedure table 22, purpose/attribute table 19 that has information when window attributes are changed in cooperation with interface section 8, information when event procedures in window attributes are changed. A window management table 18 is created for managing the purpose/event/procedure table 20 having the following functions.

Next, each of the above-mentioned tables will be explained. FIG. 7 shows the purpose/attribute table 19 and the source/attribute table. The left column of Fig. 7 shows the type of both tables 19 and 21, shows the window width, height, border width (thickness of the line around the window), and background color, and indicates whether or not to output the window. It shows whether or not it is possible to enter the window. The ability to manipulate indicates whether movement or size can be changed on the screen, and the following three items relate to child windows. The right column is the source/attribute table 21, which shows values input from the source program, and the center column is the purpose/attribute table 19, which shows changed items among the source/attribute table 21 items.

FIG. 8 shows a purpose/event procedure table 20 and a source/event procedure table 22. The window map of the type of item shown in the left column indicates the display on the screen, the window unmap indicates the erasure of the display on the screen, the display indicates the creation of a window, and the deletion indicates the deletion of window data. The right column is the source/event procedure table 22, which represents procedures that perform the processing shown in the types in the left column. The center column shows the purpose/event procedure table 20, and proc3+ indicates the change procedure of proc3 in the source/event procedure table 22.

In the above explanation, a source table is created from a source program, and a target table is generated by changing the source table through editing work. However, when the program is run in coding mode without inputting the source program If created, only the target table is created.

FIG. 9 shows the scene management table 16. In the type in the left column, the scene number indicates the combination with the window label, and the bottom term indicates the pointer to the next combination. Note that the same scene number is assigned to each window no matter how many windows there are, but the window labels are assigned different numbers even for the same window. In other words, scene numbers are assigned to each type of window, and window labels are assigned to each window.

FIG. 10 shows the window management table 18. This table 18 is provided for each window, and includes the window label, part window, and pointers to the related source/attribute table 21, source/event procedure table 22, purpose/attribute table 19, and purpose/event procedure table 20. Are listed.

Next, intermediate code to be used within the editing device is created for a procedure that is activated when an event occurs. Descriptions other than window generation or window attribute settings are written in the intermediate code as is, and for windows of the same type, their scene numbers are written in the intermediate code. For each window, from the part that describes the operation of the attributes of windows generated outside of the own procedure,
A source/attribute operation table 25 that has a correspondence between the attribute to be operated and the value of the attribute is created, and the window label to be operated within the own procedure, the source/attribute operation table 25 for that window, and the interface section 8 cooperate to create a window label. A window operation management table 23 is created that has a correspondence with the purpose/attribute operation table 24 that is created when the attribute of is manipulated.

In the self-procedure, from the part where new window generation and window attribute settings are described, labels are attached to the generated windows in the same way as in the main procedure, and the source/attribute table 21 and the source - Create the event procedure table 22 and update the window management table 18. A scene management table 17 is created that has a correspondence between scene numbers, corresponding window labels, and flags indicating window generation or attribute manipulation. Based on the created window management table 18, source/attribute table 21, source/event procedure table 22, window operation management table 23, and source/attribute operation table 19, a source program is generated in the interface section 8. Request a window to be displayed.

FIG. 11 shows the purpose/attribute operation table 24 and the source/attribute operation table 25. This figure is the same as FIG. 7. FIG. 12 shows the window operation management table 23. The type in the left column describes the window label and pointers to the source/attribute operation table 24 and purpose/attribute operation table 25 of this window. FIG. 13 shows the scene management table 17. The model in the left column contains the scene number and
There are window labels, flags that indicate window creation and settings, and pointers.

The main procedure management section 10 uses what is coded in the coding area of the interface section 8 as intermediate code as it is, and in window editing, writes the scene number in the main procedure in the intermediate code and sends it to the window generation section 12 for processing. request. The window generation unit 12 receives the label of the window to be generated, and creates or updates a scene management table 16 that has a correspondence between scene numbers and window labels. The main procedure is created based on editing in window editing mode or coding mode, a program is given as input to the editing device, and the program is edited (updated) in window editing mode or coding mode.
will be changed if

When a procedure is coded in the coding area of the interface section 8, the event/procedure management section 11 stores the code as intermediate code, and when a window is edited, the scene in the procedure is added to the intermediate code. When the number is written and the attributes of a window generated by a procedure other than the own procedure are manipulated in the interface section 8,
If the window operation unit 13 is requested to perform a process and a component window is selected to generate a new window, the window generation unit 12 is requested to perform the process. The label of the window to be generated is received from the window generation unit 12 or the window operation unit 13, and a scene management table 17 is created or updated that has a correspondence between the scene number, window label, and flag indicating whether to generate or operate.

The window generation unit 12 initializes the purpose/attribute table 19 that has a correspondence between attributes and their values by referring to the attribute master 7 that has a list of attributes of the selected part window in the interface unit 8. A purpose/event/procedure table 20 that has a correspondence between events occurring in a window and procedures activated by the event is initialized. As attributes are set in the interface section 8, the purpose/attribute table 19, purpose/event/
The procedure table 20 is updated.

When the save button is selected in the interface unit 8, the window is labeled. Window label and source attribute table 21
and a source event procedure table 22.
A window management table 18 having a correspondence between a purpose/attribute table 19 and a purpose/event/procedure table 20 is created or updated.

The window operation unit 13 creates a purpose/attribute operation table 24 that has a correspondence between the operated attributes and their values regarding the operation of the attributes of the window being generated, and displays the window label and source/attribute operation table 24. table 2
5 and the purpose/attribute operation table 24 is created or updated.

The code generation unit 14 first generates code for the procedure. Analyze the intermediate code and write the parts other than the scene number in the target program as is,
In the part where the scene number is written, the window label is searched from the scene management table 16 using the scene number as a key, and the window label is searched from the window management table 18 using the window label as the key, and the component window and source file are searched.
Attribute table 21 and source event procedure
A table 22, a purpose/attribute table 19, and a purpose/event/procedure table 20 are obtained.

If the purpose/attribute table 19 and the purpose/event/procedure table 20 exist, then the purpose/attribute table 19 and the purpose/event/procedure table 20 exist.
If the table 20 does not exist, generate a code for attribute setting from the source attribute table 21 and source event procedure table 22, and write the code for window generation in the target program using the scene number. do.

Next, code is generated for the event procedure. Analyze the intermediate code, write the parts other than the scene number as is in the target program, and write the part where the scene number is written to the scene management table 17.
Using the scene number as a key, the window label and the flag indicating whether to generate or manipulate the window are searched, and if the window is to be generated, the code for window generation is written in the target program using the scene number in the same way as a procedure.

For window operations, source/attribute operation table 25
Then, the purpose/attribute operation table 24 is obtained. If the purpose/attribute manipulation table 24 exists, a code for attribute manipulation is generated from the purpose/attribute manipulation table 24, and if it does not exist, a code for attribute manipulation is generated from the source/attribute manipulation table 25, and is written in the target program using the scene number. .

FIGS. 14 and 15 are diagrams showing the basic interface image shown in FIG. 3 that is actually used. 16 and 17 are flowcharts of this embodiment. First, Figure 1
4. Fig. 15 will be explained. As an interface,
First, a system menu for entering window editing mode, coding mode, and program visualization mode is displayed (step 26).

In the window editing mode, there is a component window for selecting the type of window to be created, a window display area, an icon display area for displaying the window that has been edited for generation as an icon, and a display area for saving the state. A save button and a quit button for exiting the window editing mode are displayed (step 27). In step 27, when a component window or an iconized window is selected by the user, the selected window is displayed in the window display area together with an attribute setting menu for setting the attributes of the selected window (step 27). 28).

The attribute setting menu is a menu whose items are attribute names that can be set for the component window of the displayed window, and it is possible to select items with those attribute names and set attribute values. When the user selects an item for setting color attributes in the attribute setting menu in step 28, a color pattern is displayed (
Step 29), from which you can select the color to be set.

In the attribute setting menu at step 28, when the user selects an item for setting an attribute that requires character input, an input area for accepting input is displayed (step 30). The user inputs the value to be set using the keyboard.

When the user selects an item for setting window size and position attributes in the attribute setting menu in step 28, a mouse cursor is displayed (step 31). The user sets the window size and position attributes by operating the mouse.

When the user selects the event/procedure item in the attribute setting menu in step 28, an event/procedure selection menu consisting of a registered procedure name item and a procedure editing item is displayed (step 32). When a procedure name is selected by the user, that procedure is set as an event procedure attribute, and when a procedure editing item is selected, a coding mode is entered and the user can edit the procedure.

When the save button is selected by the user in step 28, an input area is displayed for labeling the window (step 33), and the user inputs a window label from the keyboard.

In the coding mode, a coding area for performing coding using the keyboard, a save button for saving the state, and a quit button for exiting the coding mode are displayed (step 34).

In the visualization mode, a save button for saving the state, a quit button for exiting the visualization mode, and an input area for inputting the program name are displayed (step 35). When the program name is input, it is analyzed and a window generated by the program is displayed in the visualization area (step 36).

Next, the flow of this embodiment will be explained with reference to FIGS. 16 and 17. First, necessary windows are displayed and the display is initialized (step 37). A main loop is then entered for processing events that occur on the display (step 38). In step 38, the user selects a coding mode (step 39);
When coding is performed (step 40), intermediate code,
Scene management tables 16 and 17, window management table 18, and window operation management table 23 are created.

In step 38, when the user selects the visualization mode (step 41) and inputs the source program (step 42), the source program is analyzed (step 43), and the source attribute table 21, the source Event procedure table 22, source
The attribute operation table 25 is created and a window generated within the source program is displayed (step 44).

In step 38, when the user selects the window editing mode (step 45) and specifies the window to be edited (step 46), the attribute setting menu is displayed (step 47), and the sub-loop is entered (step 45). 48).

In step 48, when the user selects an attribute item (step 49) and sets the value of the attribute (step 50), the purpose/attribute table 19, purpose/event/procedure table 20, purpose/attribute operation Create table 24.

At step 48, if the user selects Quit (step 51), the process returns to the main loop (step 38).

In step 48, when the user selects save (step 52) and performs labeling (step 53), the intermediate code and scene management tables 16 and 17 are saved.
, create the window management table 18 and window operation management table 23, and execute the main loop (step 38).
Return to

At step 38, if the user selects Quit (step 54), the main loop (step 38) is exited.

In step 38, when the user selects save (step 55), the created intermediate code,
Scene management tables 16, 17, window management table 18, window operation management table 23, source/attribute table 21, source/event/procedure table 22, source/attribute operation table 25, purpose/attribute table 24, purpose/event/procedure table 22, A code is generated based on the procedure table 20 and the purpose/attribute operation table 19 (step 56), and a target program is generated.

[0056]

As is clear from the above description, the present invention eliminates the complexity of setting window attributes and operating various tables by selecting window attributes in the editing mode and coding in the coding mode. Since the graphical user interface, which is important in a program that generates a window, can be grasped while editing the program, the efficiency of program creation is improved. Furthermore, by providing a visualization mode, it is possible to check and verify the created program.

[Brief explanation of drawings]

FIG. 1 is a diagram showing the principle of the present invention.

FIG. 2 is an explanatory diagram of an event-driven program.

FIG. 3 is a diagram showing the basics of an interface image.

FIG. 4 is a block diagram showing the configuration of an embodiment of the present invention.

FIG. 5 is an explanatory diagram of the configuration of a program of the present invention.

FIG. 6 is an explanatory diagram of intermediate codes and scene numbers.

FIG. 7 is a diagram showing a specific example of a purpose/attribute table and a source/attribute table.

[Figure 8] Purpose/event procedure table and source/
FIG. 3 is a diagram showing a specific example of an event procedure table.

FIG. 9 is a diagram showing a specific example of a scene management table used by the main procedure management section.

FIG. 10 is a diagram showing a specific example of a window management table.

FIG. 11 is a diagram showing a specific example of a purpose/attribute operation table and a source/attribute operation table.

FIG. 12 is a diagram showing a specific example of a window operation management table.

FIG. 13 is a diagram showing a specific example of a scene management table used by the event procedure management section.

FIG. 14 is a diagram showing an implementation interface image.

FIG. 15 shows a partial view of FIG. 14;

FIG. 16 is a diagram showing the first half of the flow of the example.

FIG. 17 is a diagram showing the second half of the flow of the example.

Claims (4)

[Claims] Claim 1: In a program editing device for editing an event-driven program consisting of an event procedure activated by an event occurring within a generated window and a main procedure that calls this event procedure, window attribute selection means (101) for selecting an attribute; event-compatible attribute selection means (102) for selecting a process when the attribute selection for this window selects a process when an event occurs; non-event compatible attribute input means (103) for inputting the attribute value to be selected when selecting a process other than processing when an event occurs; this non-event compatible attribute input means (103); Window display means (102) for displaying a window based on the content performed by (102)
4) a window editing mode (100) having
A coding mode (200) that occurs when the event corresponding attribute selection means (102) selects a procedure editing item and has a coding means (201) for coding a program, and is characterized in that the coding mode (200) is configured to edit a program. A program editing device for Claim 2: The window attribute selection means (101
) comprises a component window for selecting basic attributes including event processing attributes and visual attributes, and an attribute setting menu for selecting detailed attributes of the basic attributes selected in this component window. window editing device. 3. The window editing device according to claim 1, further comprising a visualization mode having a visualization area for displaying a window generated by an input event-driven program. 4. The window editing device according to claim 3, wherein the event-driven program input in the visualization mode is edited.