JP2002123392A - Device, method, medium and program for developing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a function for developing an application program with unified design even in the utilization of a component where many interfaces can be used and many combinations are possible. SOLUTION: The program developing devices (1, 10) for developing the application program by using the component having the plural interfaces are provided with a component selection part (101) for selecting the component, interface selection parts (102, 103) for making the selected component select an interface and setting the selected interface to be effective or ineffective, a recording part (4) for holding a set record (11) with setting of effectiveness or ineffectiveness, and a component editing part (120) for developing the program by using the interface set to be effective or the interface which is not set to be ineffective.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a program development technique using components.

[0002]

2. Description of the Related Art Components (for example, Microsof
Users of the ActiveX control provided by Windows, Inc., can use its components in containers (for example, Micro
The program could be developed by placing it on the soft company's Visual Basic form. Users of such components were able to use all the interfaces (e.g., properties, methods, events) exposed by each component.

[0003] In addition, there are some components that are useful to combine a plurality of components. In such a component, a combination of components could be used by setting the interface of each component for each component.

[0004] In the development of a group of applications, a template having a predetermined form can be created by using a template function. And
Such a model has been used as an initial setting of an application.

[0005] Today, as the functionality of such components is enhanced, the number of their interfaces is also increasing. On the other hand, consumers of components do not use all of those interfaces.

Conversely, from a large number of interfaces,
Finding the desired interface required a great deal of effort, such as reading the manual carefully.

Further, when a plurality of components are used in combination, for example, when a group box and an option button, a toolbar and a command button, a tab and a property page, a property sheet, and the like are used, and when these combinations are standard, There is. However, even for such a fixed combination, the user had to set an interface for each individual component.

Further, when developing an application in a group, a template in an early stage of development can be determined by using a template function. But,
At the stage of developing the target application from the model, all component interfaces were available. In addition, there were various ways to combine components.

For this reason, the methods of using and combining the interfaces are not unified, and the design of the application is often different. In addition, the maintenance of the program was inefficient because the usage methods were not unified.

[0010]

SUMMARY OF THE INVENTION The present invention has been made in view of such problems of the prior art. A technical object of the present invention is to provide a program development environment that does not reduce work efficiency even when an application program is developed using components having a large number of interfaces.

Another technical object of the present invention is to provide a function of developing an application program having a unified design even when using components that can use a large number of interfaces and a large number of combinations. It is.

Another object of the present invention is to improve maintainability of an application program by such development.

[0013]

The present invention has the following features to attain the object mentioned above.

That is, the present invention provides a program development apparatus (1, 10) for developing an application program using components having a plurality of interfaces.
A component selection unit (101) for selecting a component, an interface selection unit (102, 103) for selecting an interface for the selected component, and setting the selected interface to valid or invalid; A recording unit (4) that holds a setting record (11) that records invalid setting, and an interface that is set to be valid or an interface that is not set to be invalid according to the setting record (11). A component editing unit (120) for developing a program.

Preferably, the program development device (1, 10) further includes a setting record designating section (13) for designating one of a plurality of setting records, and the component editing section (120) stores the designated setting record. The program may be developed using an interface that is set to be valid in the recording or an interface that is not set to be invalid.

Preferably, the program development device (1, 10) includes a group definition section (43) for defining a group of a plurality of users, and a group setting record designation for designating setting records usable for the group. Department (1
3a) may be further provided.

The present invention also provides a program development device (1, 1) for developing an application program by combining components having a plurality of interfaces.
0), a plurality of components are arranged, an arrangement component selection unit (111) for selecting such arrangement components, and an arrangement component for selecting such arrangement components to be arranged in the selected arrangement components. A component selection unit (112), an arrangement specification specifying unit (112, 113) for specifying an arrangement specification for arranging the component to be arranged, and a recording unit (11) for holding an arrangement specification record (11) for recording the specified arrangement specification 4) and
According to the arrangement specification record (11), a component editing unit (120) for arranging the arranged component on the arranged component and developing a program may be provided.

[0018] Preferably, one of the plurality of arrangement specification records is provided.
The component editing unit (120) further includes an interface that is set to be valid in the specified arrangement specification record, or an arrangement specification that is not set to be invalid in the specified arrangement specification record. May be used to develop the program.

Preferably, the program development device (1, 10) includes a group definition section for defining a group of a plurality of users, and a group placement specification for designating a placement specification record (11) usable for the group. A recording designation unit (13) may be further provided.

The present invention also relates to a method for developing an application program using a component having a plurality of interfaces, wherein a step of selecting a component (S3) and a step of selecting an interface for the selected component ( S6)
Setting the selected interface to valid or invalid (S7), recording the valid or invalid setting (S8), and setting the interface to be valid or invalid according to the setting. (S21-S28) to develop a program using an interface that has not been set.

The present invention also relates to a method for developing an application program by combining components having a plurality of interfaces. The method comprises the steps of arranging a plurality of components and selecting such an arrangement component (S11). Selecting a component to be placed to be placed on the placed component (S12), and defining a placement specification for placing the placed component (S13).
Recording the specified layout specification (S16);
A step (S21-S28) of developing a program by arranging the component to be arranged on the arrangement component in accordance with the arrangement specification may be adopted.

Further, the present invention may be a program for causing a computer to execute the above steps.
Alternatively, such a program may be recorded on a computer-readable recording medium.

Further, the present invention may be a data communication signal embodied in a carrier wave having a program code portion for causing a computer to execute the above steps.

[0024]

Preferred embodiments of the present invention will be described below with reference to the accompanying drawings. << First Embodiment >> FIGS. 1 to 1 show a first embodiment of the present invention.
3 will be described. FIG. 1 is a hardware configuration diagram of a program development device 1 according to the present embodiment. FIG. 2 is a functional configuration diagram of the program development device 1.
3 and 4 are layout examples of components by the layout tool 10 shown in FIG. 2, FIG. 5 is a setting operation example of how to use a component (hereinafter, referred to as a style), and FIG. FIGS. 7 and 8 are examples of a layout of a group component by the layout tool 10, and FIG. 9 is an example of a style setting operation for the group component. 10 is an example of a style definition file 11 that defines the style set according to FIG.
FIG. 13 is a flowchart showing processing of the layout tool 10 at the time of a style setting operation, and FIG. 13 is a flowchart showing processing of the layout tool 10 when laying out components and developing a program. <Hardware Configuration> FIG. 1 shows a hardware configuration diagram of the program development device 1. This program development device 1
Displays a CPU 2 that executes a program, a memory 3 that stores a program executed by the CPU 2 and data processed by the CPU 2, a hard disk 4 that records a program and data, and displays information such as menus, icons, and messages. And a keyboard 6 for inputting character data, a pointing device 7 for operating menus and icons on the display device 5, and a communication interface 8 for accessing a network.

The CPU 2 executes a program stored in the memory 3 and provides a function as the program development device 1.

The memory 3 stores programs executed by the CPU 2 and data processed by the CPU 2.

The hard disk 4 records a program executed by the CPU 2, data processed by the CPU 1, and the like.

The display device 5 displays information such as information input by the user, menus, icons, and messages of programs developed by the user. As a display device, for example,
A CRT, a liquid crystal display or the like is used.

The keyboard 6 is used for inputting character data. The pointing device 7 is used for operating menus and icons displayed on the display device 5. As the pointing device 7, for example, a mouse, a trackball, an electrostatic pointing device, a laser pointing device, a touch panel, or the like can be used.

The communication interface 8 accesses the network and communicates with another host on the network in accordance with a command from the CPU 2. <Functional Configuration> FIG. 2 is a functional configuration diagram of the program development device 1. This program development device 1 includes a CPU 2
Is realized by executing the window system 12 and the layout tool 10 associated with the window system 12.

The window system 12 displays information on the display device 5 and detects a user operation via the keyboard 6 and the pointing device 7. The window system 12 holds a component library 14 in the hard disk 4.

This component library 14 holds many components and is open to users. The user uses this component as a part when developing an application program.

The layout tool 10 refers to components in the component library 14 and combines them to create a program.

The user operates the screen of the layout tool 10 using the display device 5, the keyboard 6, and the pointing device 7 to develop a user interface of the program.

As the components, for example, buttons, pull-down menus, pop-up menus, lists and the like are known. In addition, each component has various functions (hereinafter, referred to as an interface) configuring a user interface.

Interfaces are classified into properties, methods, and events. The property is an attribute of the component, for example, a foreground color, a background color, a dimension, or the like.

A method is a function for operating each component. For example, there are a method of setting a value to a component from an application program, a method of reading a set value, and the like.

An event is a type of user operation detected by the component. Events include:
For example, the display on the screen (called a pointer) corresponding to the operation of the pointing device 7 is moved, the pointer enters and leaves the display area of the component on the screen, the button of the pointing device 7 is pressed on the display area, Some of them are operated by the keyboard 6 or the like.

In this embodiment, the layout tool 1
0 refers to a plurality of style definition files 11 and the like, and a style instruction file 13 that designates one of the style definition files 11 or the like.

The first feature of the layout tool 10 is as follows.
This is to provide a function to restrict the usable ones for a large number of interfaces of the large number of components as described above. Restricting the interfaces available will bind the developer. As a result, uniformity of operation occurs in the developed application program. Thus, in the present embodiment, such a constraint is called a style. In addition, providing a constraint is called style setting.

In addition to components that simply display information to the user and detect user operations, there are components that combine and arrange other components to form a new component. Such components are called group components. A component arranged by a group component is called a component to be arranged. In the group component, there are various arrangement methods for arranging the component to be arranged.

The second feature of the layout tool 10 is that
Such a group component is provided with a function of restricting the arrangement method of the component to be arranged. Such restrictions, like those for the interface, are called styles.

The style defined by the layout tool 10 as described above is stored in the style definition file 11. The style definition file 11 can define styles for one or more arbitrary components. The definition contents of different styles can be stored in style definition files 11a and 11b with different names.

The layout tool 10 holds which style definition file 11 or the like is currently used in the style instruction file 13. The layout tool 10 selects a style definition file according to the instruction of the style instruction file 13 and develops a program. <Interface Style> FIG. 3 shows an operation example of arranging components using the layout tool 10. In this example, one button named CmCommand1 is arranged in an editing window 120 called MainForm. The layout tool 10 can define an event detected by such a button. Such a definition can be found in the pull-down menu in FIG.
Edited event procedure ”.

In the example of FIG. 3, no style is set in the layout tool 10. Therefore, when the user selects "edit event procedure", a large number of events such as Click and GotFocus can be selected. In this state, Cm
All events provided for the button named Command1 are available.

FIG. 4 shows an example of an editing window 120 in which usable events are restricted. In the case of FIG. 4, in the style definition file, Click, GotFocus and LostF
Only three types of events, ocus, are available. In such a case, the user may select the edit window 120
In, only the available events can be selected.

FIG. 5 shows an example of a setting operation for setting a style as shown in FIG. The user sets the layout tool 1
0 is activated, and when a control customization is selected from a menu (not shown), a component screen 101 is displayed. Here, the control customization is a function for setting a style for the interface.

On the component screen 101, a list of interfaces for which styles can be set is displayed (in FIG. 5, the title is "list of available controls"). When the user selects a desired component, for example, “CommandButtonControl” and presses a button “customize”, an unused interface setting screen 102 is displayed.

In FIG. 5, on the unused interface setting screen 102, a list of events that can be used for a component named “CommandButton Control” is displayed. Here, when the user selects an unused event and presses the center button (">"), the event moves to the "unused event list" column. Pressing the button ">>" moves all events to the "Unused event list" column.

The event moved to the “unused event” can be returned to the “list of used events” column by pressing the center button “<” or “<<”. In this way, in the “List of events to be used” like the unused interface setting screen 103, Click, Get
Leave only Focus and LostFocus, and when OK is pressed,
The setting of such a style is determined.

The user repeats the operation described with reference to FIG. 5, sets styles for a plurality of components, and presses an OK button on the component screen 101. Then, the layout tool 10 queries the name of the style definition file for storing the style. When the user inputs a style definition file name, the newly defined style is added to the style definition file. After that, the layout tool 10 ends the customization.

FIG. 6 shows a definition example (1) of a style definition file generated by the above setting operation.
In this style definition file 11, an event (CommandB
For example, it is specified that a key press (KeyDown), a key pressed state (KeyPress), and a key press release (KeyUp) on the keyboard 6 are not used as events. In addition, it is specified that mouse button pressing (MouseDown), mouse moving (MouseMove), and mouse button releasing (MouseUp) are not used as events.

The style definition file 11 stipulates that among the methods of the component called the command button control (indicated by CommandButton.Methods), the method called Move is not used.

In the style definition file 11, the property Style is set to 2 among the properties of the component named ComboBoxControl (indicated by ComboBox.Properties). In addition, the method of the combo box control (Co
Move is not used in mboBox.Methods). <Style of Group Component> FIG. 7 shows an operation example of the editing window 120 for arranging components in a group component by the layout tool 10. FIG. 7 is an operation example of the editing window 120 in which a style is not specified for the group component.

In this operation, the user first arranges a group component called a group control (CmGroup) on a main form (MainForm) from a selection box 30 for selecting a component. Further, the user pulls out three components called option controls from the selection box 30 and vertically arranges them in the group control (CmGroup1, CmGroup2, and CmGro).
up3).

As described above, normally, when arranging components in group components, the user must repeat the operation by the number of arrangements. Also,
The user can freely specify the direction of the arrangement and the position of the arrangement.

FIG. 8 shows an operation example of the edit window 120 when the layout specification is defined in the style definition file 11. In this operation, as in FIG. 7, the group component (CmGroup)
Three components called option button controls are arranged (CmGroup1, CmGroup2, and CmGroup
3).

In the editing window 120 shown in FIG. 8, however, the layout specification of the option button controls is defined in the style definition file 11 (three vertically arranged at predetermined intervals). Therefore, when the user pulls out one option button control from the selection box 30 and arranges it in the group control, the other two are automatically arranged vertically.

FIG. 9 shows a setting operation example for setting a style as shown in FIG. The user sets the layout tool 1
0 is activated, and when customization of group control is selected from a menu (not shown), a group component selection screen 111 is displayed.

The group component selection screen 111 displays a list of group components for which a style can be set. When the user selects a desired group component, for example, “GroupBox Control” and presses a “Next” button, a component selection screen 112 is displayed.

A list of components that can be arranged in a group component named “GroupBox Control” is displayed on the arranged component selection screen 112. Here, the user selects the component to be arranged (“CmOptionButton Control” in FIG. 9) and sets the number to 3
Is set, and “Next” is pressed.
Is displayed.

On the arrangement direction designation screen 113, the user selects an arrangement direction. In FIG. 9, the vertical direction is selected. After that, when you select the complete button, “GroupB
The layout specification of “CmOptionButton Control” in the group component named “ox Control” is determined.

Then, the layout tool 10 inquires of the name of the style definition file 11 for storing the style. When the user inputs a style definition file name, a newly defined style is added to the style definition file 11. Then, the layout tool 10
Ends the customization.

FIG. 10 shows a definition example (2) of the style definition file 11 generated by the above setting operation. In the style definition file 11, the arrangement of option buttons in a group component called a group box is defined (GroupBox.OptionBut
ton). In this example, the number of option buttons is three (OptionButton = 3), and the arrangement direction is vertical (Ali
gnment = Vertical).

The arrangement of command buttons in a group component called a toolbar is defined (To
olBar.CommandButton). In this example, the number of command buttons is four (CommandButton = 4), and the arrangement direction is specified to be horizontal (Alignment = Horizontal). <Use of Style Definition> The layout tool 10 according to the present embodiment collectively stores styles set for a plurality of components in the style definition file 11.
Further, the layout tool 10 saves definition contents of different styles in files with different names.

For example, in the style definition file 11,
Save styles for inventory management system development. This is a program that supports such things as stock management of raw materials, stock management of products, and management of suppliers / shippers. In the style definition file 11, a style for unifying the operation of inventory management and the appearance of the screen may be defined. The members of the program development project share the style definition file 11.

Also, for example, the style definition file 11
In a, a style of a reservation system development project such as a hotel or travel is defined. This is a system for executing vacant room information reference, reservation input, customer information management, and the like. In the style definition file 11, a style for unifying reference to vacant room information, reservation operation, and the like may be defined.

For example, the style definition file 11
b defines the style of the employee's employment management system development project. This is a system that provides processing for issuing notification documents such as business trips and vacations, processing for referring to employment status such as the status of vacation acquisition and overtime, and communication functions between employees such as electronic bulletin boards and e-mail. The style definition file 11 may define a style for unifying operations and the like during work management.

The user develops an application program within the range of the permitted interface and arrangement method. In this case, the user can use the style definition file 11 and the like according to the target for developing the program. That is, the user specifies a name of a specific style definition file 11 or the like in an environment setting menu (not shown) of the layout tool 10.

Then, the layout tool 10 causes the program to be developed using the interface and the arrangement specification designated as usable in the designated style definition file 11 or the like. <Operation and Effect> FIG. 11 shows a style setting process for the interface of the component. When the user selects customization of a control from a menu (not shown) of the layout tool 10, the CPU 2 proceeds to FIG.
The processing shown in is executed.

First, the CPU 2 displays a list of components for which a style can be set (S1).

In this state, the CPU 2 waits for a user operation (S2, S3). When a user operation is detected, C
PU2 determines whether the operation is the pressing of the cancel button (S2).

If the user's operation is to press the OK button (Y in S2), the CPU 2 adds the current settings to the style definition file 11 (S8), and ends the style setting processing for the interface. .

When the user's operation is not pressing the OK button,
When the customization button is pressed, the CPU 2
It is determined whether the user is selecting a component (S
3). If the user is not selecting a component (S
3 and N), the CPU 2 returns the control to a state of waiting for a user operation.

If it is determined in S3 that the component is being selected when the user presses the customize button, the CPU 2 displays a list of interfaces available for the selected component (S4). In this state, the CPU 2 waits for a user operation again (S5, S6). That is, here, the CPU 2 waits for the user to select an unused interface.

If the user's operation is to cancel the selection of an unused interface, the CPU 2 executes control at S1.
Return to

If the operation of the user is OK for selecting an unused interface, the CPU 2 determines the specified unused interface (S7). Here, "confirming" means reading out the designation of an unused interface set as in the unused interface setting screen 103 in FIG. 5 from the screen. Then, the CPU 2 returns the control to S1.

FIG. 12 shows a style setting process for the group component. When the user activates the layout tool 10 and selects customization of the group control from a menu (not shown), the CPU 2 executes the processing of FIG.

First, the CPU 2 displays a list of group components and allows the user to select a list (S11).

When the user presses the button "next" (see FIG. 9), the CPU 2 displays a list of the components to be arranged in the group components and allows the user to select (S12). Further, the user is required to input the number of the arrangement.

Further, when the user presses the "next" button, the CPU 2 allows the user to specify the arrangement direction (S13).

Further, when the user presses the completion button, the set style is added to the style definition file 11 (S14), and the process ends.

On the other hand, when the user presses the button “return” (see FIG. 9) on each of the screens for selecting the group components, selecting the components to be arranged, and specifying the number of arrangements, the CPU 2 controls each of the previous operations. Screen. When the user presses the cancel button (see FIG. 9) on any screen, the CPU 2 ends the processing without doing anything.

FIG. 13 shows processing for laying out components and developing a program. When the user activates the layout tool 10 and selects a component layout from a menu (not shown), the CPU 2 proceeds to FIG.
Step 3 is executed.

In this process, first, the CPU 2 determines whether or not the user selects a style (S21). The selection of a style refers to a selection of one of a plurality of style definition files 11 and the like.

When the user selects a style, the CPU
2 displays a list of the style definition files 11 and the like on the display device 5 and allows the user to select (S22). Then, C
PU2 advances the control to S23.

On the other hand, if the user does not select a style in S21, the CPU 2 keeps the style currently used, or advances the control to S23 with the style not selected. The current style refers to the style when the layout tool 10 was used last time. Style unused refers to a state in which no style has been used yet, and the interface and group components are available without restriction.

Steps S23 to S27 are waiting for a user operation. Upon detecting a user operation, the CPU 2
First, it is determined whether or not a group component layout is selected (S23).

If the user operation is a group component arrangement selection, the CPU 2 executes a group component arrangement process (S24). In this process,
According to the specified style definition file 11, the component to be placed specified by the user is placed in the group component specified by the user. After that, the CPU 2 executes the control S
Return to 23.

If the user operation is not the placement of a group component, the CPU 2 determines whether or not the user operation is to select the interface setting of the component (S25).

If the user operation is to select an interface setting, the CPU 2 executes an interface setting process (S26). In this process, the CPU 2 sets a user-specified interface on a user-specified component according to the specified style definition file 11 and incorporates the interface into a screen (for example, MainForm). Then the CPU
2 returns the control to S23.

If the user operation is not an interface setting selection, the CPU 2 determines whether or not the user operation is a designation for terminating the process (S27).

If the user operation does not specify the end of processing,
The CPU 2 returns the control to S23. On the other hand, if the user's operation is to select the processing end, the CPU 2 saves the layout result (S28) and ends the layout processing.

As described above, in the program development device 1 of the present embodiment, interfaces usable in components and arrangement specifications of components can be restricted in advance.

As a result, the user does not need to be familiar with all of the huge interfaces in the huge components. Since the user only needs to be familiar with the components and interfaces whose use is specified in the project in which the user participates, the development efficiency is improved.

According to the program development device 1,
The user interface can be unified in a system development project with multiple members.

According to the program development device 1,
The user can freely select the style to use. Therefore, for example, a user who participates in a plurality of development projects can use different styles for each project.

For example, a certain user develops an inventory management system in the morning according to the style definition file 11. Then, in the afternoon, the user develops a reservation system such as a hotel or a trip according to the style definition file 11a. According to the present program development device 1, the risk of a user developing such a plurality of projects in parallel confusing the specifications of the user interface is reduced. <Modification> In the above embodiment, the style definition file 11 and the like are stored in the hard disk 4 of the program development device 1. However, the embodiment of the present invention is not limited to such a configuration. For example, the program development device 1
The style definition file 11 and the like may be stored on another computer different from the above. That is, in an environment where a user develops a program using a plurality of program development devices 1 such as a personal computer, the style definition file may be stored in a server on the network. << Second Embodiment >> A second embodiment of the present invention will be described with reference to FIG. In the program development device 1 of the first embodiment, an example is described in which the user selects the style definition file 11 or the like in the environment setting menu of the layout tool 10 before developing the program, and develops the program according to the style.

In the present embodiment, a program development using components is illustrated in a network environment having a server. This server has a password file for defining users and a group file for classifying users.

In this embodiment, the user cannot freely select the style definition file 11 and the like, but is restricted by the style definition file 11 and the like designated by the system administrator. Other configurations and operations are the same as those described in the first embodiment. Therefore, the drawings of FIGS. 1 to 13 are referred to as needed.

FIG. 14 shows a system configuration diagram of the program development system according to the present embodiment. This system includes a server 41 and a plurality of program development devices 1a and 1b connected via a network 50. The hardware configurations of the server 41, the program development device 1a, and the like are the same as those in FIG.

The server 41 has a password file 42, a group file 43, and a style instruction file 1 therein.
3a and a plurality of style definition files 11 and the like. The configuration and functions of the style definition file 11 and the like are the same as in the first embodiment, and a description thereof will be omitted.

[0103] The password file 42 records the combination of the user name and password of the user belonging to the system and the group name to which the user belongs.

The group file 43 records group names in the system and names of users belonging to the groups.

In the style instruction file 13a, a style name to be used for each group or each user is specified. Here, the style name is the style definition file 1
1 and so on. This style instruction file 13a
Is set by the system administrator.

When the style is specified for one user by the user name and the group name to which the user belongs, the specification for the user name may be given priority.

Each user develops a program using the layout tool 10 in his or her own program development device 1a or the like. When activated, the layout tool 10 accesses the server 41 via the network, and selects a style according to the instruction of the style instruction file 13a on the server 41. The operation of the user after the style is selected is the same as in the first embodiment.

As described above, by placing the style instruction file 13a in the server 41, the styles of the users on the network can be centrally managed. Further, by providing the style definition file 11 and the like in the server 41, it is not necessary to define the style instruction file 13a individually in the program management devices 1a and 1b.

In the server 41 of the present embodiment, in addition to the specification of the style definition file 11 and the like for the user name,
The style definition file 11 and the like are designated collectively for the group to which the user belongs. For this reason, it is not always necessary to set the style individually. For this reason,
The operation for specifying the style definition file 11 or the like can be simplified. <Modification> In the first embodiment, an example in which the style used by the user is freely selected has been described. Further, in the second embodiment, the example in which the style definition file 11 and the like are placed in the server 41 and the style used by each user is specified by the administrator has been described. The first embodiment and the second embodiment may be combined to construct a program development environment.

For example, the style specified in the style instruction file 13a of the server 41 is used as a default. The user can individually select his own style. The selected style is recorded in the server 41, the program development device 1a, or the like. This user
Develop the program according to the style you prefer.

On the other hand, a user who has not selected a style follows the default designation set in the server 41. With such a system, an experienced person who participates in a large number of projects is allowed to freely select the style definition file 11 and the like, and an inexperienced person is forcibly developed a program according to a specific style. be able to. << Computer-Readable Recording Medium >> The program of the layout tool 10 of the above embodiment can be recorded on a computer-readable recording medium. Then, by causing a computer to read and execute the control program on the recording medium, the computer can function as the program development device 1 described in the above embodiment.

Here, a computer-readable recording medium is a recording medium that stores information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read by a computer. Say. Examples of such a recording medium that can be removed from a computer include a floppy (registered trademark).
Disc, magneto-optical disc, CD-ROM, CD-R / W, DVD, DA
T, 8mm tape, memory card, etc.

A recording medium fixed to the computer includes a hard disk, a ROM (Read Only Memory) and the like. << Data communication signal embodied in a carrier wave >> The program can be stored in a hard disk or a memory of a computer and distributed to other computers via a communication medium. In this case, the program is transmitted over a communication medium as a data communication signal embodied by a carrier wave. Then, the computer receiving the distribution can be caused to function as the program development device 1 of the above embodiment.

Here, as the communication medium, a wired communication medium,
For example, it may be a metal cable including a coaxial cable and a twisted pair cable, an optical communication cable or the like, or a wireless communication medium such as satellite communication or terrestrial wireless communication.

The carrier is an electromagnetic wave or light for modulating a data communication signal. However, the carrier may be a DC signal. In this case, the data communication signal has a baseband waveform without a carrier. Therefore, the data communication signal embodied in the carrier wave may be either a modulated broadband signal or an unmodulated baseband signal (corresponding to a case where a DC signal of voltage 0 is used as the carrier wave). << Other >> This embodiment discloses the following invention.

(Supplementary Note 1) A program development device for developing an application program using components having a plurality of interfaces. A component selection unit for selecting a component, and an interface for selecting a selected component, An interface selection unit for setting an interface to be enabled or disabled, a recording unit for holding a setting record that records the setting of the enabled or disabled, an interface set to be enabled according to the setting record, or a setting to be disabled A program development device comprising: a component editing unit that develops a program using an interface that has not been implemented.

(Supplementary Note 2) The apparatus further comprises a setting record designating section for designating one of the plurality of setting records, wherein the component editing section has an interface set to be valid in the designated setting record or invalid. The program development device according to claim 1, wherein the program is developed using an interface that has not been set.

(Supplementary Note 3) The program development according to Supplementary Note 1, further comprising: a group definition unit that defines a group including a plurality of users; and a group setting record designation unit that designates a setting record usable for the group. apparatus.

(Supplementary Note 4) A program development device for developing an application program by combining components having a plurality of interfaces, and a placement component selection unit for arranging a plurality of components and selecting such a placement component; A placement component selection unit that selects such a placement component to be placed in the placed placement component, a placement specification specifying unit that specifies a placement specification for placing the placement component, and the specified placement specification. A program development apparatus, comprising: a recording unit that retains an arrangement specification record to be recorded; and a component editing unit that develops a program by arranging a component to be arranged on the arrangement component according to the arrangement specification record.

(Supplementary Note 5) One of the plurality of arrangement specification records
5. The program development device according to claim 4, further comprising an arrangement specification record designation unit for designating one of the plurality of arrangement specifications, wherein the component editing unit develops a program using the arrangement specification specified in the designated arrangement specification record.

(Supplementary Note 6) The supplementary note 4 further includes a group definition unit that defines a group including a plurality of users, and a group placement specification record designation unit that designates a placement specification record usable for the group. Program development equipment.

(Supplementary Note 7) A method for developing an application program using a component having a plurality of interfaces, wherein a step of selecting a component, a step of selecting an interface for the selected component, and a step of selecting the interface Setting an enable or disable, recording the enable or disable setting, and developing a program using an interface that is set to be valid or an interface that is not set to be invalid according to the setting. And a program development method.

(Supplementary Note 8) This is a method for developing an application program by combining components having a plurality of interfaces. The method includes the steps of arranging a plurality of components and selecting such an arrangement component; Selecting such a placed component to be placed, defining a placement specification for placing the placed component, recording the defined placement specification, and setting the placement according to the placement specification. A step of arranging the component to be arranged on the component to develop the program.

(Supplementary Note 9) A program for causing a computer to support the development of an application program using components having a plurality of interfaces. The program includes a step of selecting a component, and a step of selecting an interface for the selected component. Setting the selected interface to be enabled or disabled, recording the enabled or disabled setting, and using an interface that is set to be enabled or an interface that is not set to be disabled according to the setting. And a computer-readable recording medium on which the program for executing the program is executed.

(Supplementary Note 10) A program for causing a computer to support the development of an application program by combining components having a plurality of interfaces, in which a plurality of components are arranged, and a step of selecting such an arranged component; To be placed on the placed component, selecting such a placed component, defining the placement specification for placing the placed component, and recording the defined placement specification,
A step of arranging a component to be arranged on the arrangement component in accordance with the arrangement specification to develop a program.

(Supplementary Note 11) A data communication signal embodied in a carrier wave having a program code portion for supporting the development of an application program using components having a plurality of interfaces, the component being selected by a computer. Selecting an interface for the selected component; setting the selected interface to valid or invalid; recording the valid or invalid setting; and setting the valid according to the setting An interface or a step of developing a program using an interface not set as invalid.

(Supplementary Note 12) A data communication signal embodied in a carrier wave having a program code portion for supporting the development of an application program by combining components having a plurality of interfaces with a computer. Selecting such a placement component; selecting such a placed component to be placed on the selected placement component; defining a placement specification for placing the placed component; A data communication signal having a program code portion for executing a step of recording a prescribed arrangement specification and a step of developing a program by arranging a component to be arranged on the arrangement component according to the arrangement specification.

[0128]

As described above, according to the present invention,
The interface used by the component and the method of combining the components can be limited, the interface can be easily searched, and the work efficiency can be improved. Further, according to the present invention, it is possible to unify the operations of the components used in the application program. As a result, the present invention improves the maintainability of the application program.

The present invention is particularly effective in group development in which one person develops one system.

[Brief description of the drawings]

FIG. 1 is a hardware configuration diagram of a program development device 1 according to a first embodiment of the present invention.

FIG. 2 is a functional configuration diagram of the program development device 1.

FIG. 3 shows a component layout example (1) by a layout tool 10;

FIG. 4 shows a component layout example (2) by the layout tool 10;

[Figure 5] Example of style setting operation for component

FIG. 6 shows an example of a style definition file 11 (1).

FIG. 7 shows a layout example (1) of a group component by the layout tool 10;

FIG. 8 shows a layout example (2) of a group component by the layout tool 10;

FIG. 9 is an example of a style setting operation for a group component

FIG. 10 shows an example of a style definition file 11 (2).

FIG. 11 is a layout tool 10 at the time of a style setting operation.
(1) showing the process of (1)

FIG. 12 is a layout tool 10 during a style setting operation.
(2) showing the processing of (2)

FIG. 13 is a flowchart showing processing of the layout tool 10 when developing a program.

FIG. 14 is a system configuration diagram of a program development device 1 according to a second embodiment of the present invention.

[Explanation of symbols]

 1, 1a, 1b Program development device 2 CPU 3 Memory 4 Hard disk 10 Layout tool 11, 11a, 11b Style definition file 13, 13a Style instruction file 43 Group file 101 Component selection screen 102, 103 Unused interface setting screen 111 Group component selection Screen 112 Arranged component selection screen 113 Arrangement direction designation screen 120 Edit window

Claims (12)

[Claims] 1. A program development apparatus for developing an application program using a component having a plurality of interfaces, comprising: a component selection unit for selecting a component; and an interface for selecting an interface for the selected component. An interface selection unit that sets valid or invalid; a recording unit that retains a setting record that records the valid or invalid setting; an interface that is set to valid or invalid according to the setting record A program development device comprising a component editing unit for developing a program using an interface that does not have an interface. 2. The apparatus according to claim 1, further comprising: a setting record designating unit that designates one of the plurality of setting records, wherein the component editing unit is an interface set to be valid in the designated setting record, or
The program development device according to claim 1, wherein the program is developed using an interface that is not set to be invalid. 3. The program development device according to claim 1, further comprising: a group definition unit that defines a group including a plurality of users; and a group setting record designation unit that designates a setting record usable for the group. . 4. A program development apparatus for developing an application program by combining components having a plurality of interfaces, wherein a plurality of components are arranged, and an arrangement component selection unit for selecting such an arrangement component; A placement component selection unit that selects such placement components to be placed in the placement component; a placement specification definition unit that defines placement specifications for placing the placement components; and records the defined placement specifications. A program development device, comprising: a recording unit that retains an arrangement specification record; and a component editing unit that develops a program by arranging a component to be arranged on the arrangement component according to the arrangement specification record. 5. An arrangement specification record designating section for designating one of a plurality of arrangement specification records, wherein the component editing section executes a program using an arrangement specification defined in the designated arrangement specification record. 5. The program development device according to claim 4, which is developed. 6. The program according to claim 4, further comprising: a group definition unit that defines a group including a plurality of users; and a group placement specification record designation unit that designates a placement specification record usable for the group. Development equipment. 7. A method for developing an application program using a component having a plurality of interfaces, comprising the steps of: selecting a component; selecting an interface for the selected component; and enabling the selected interface. Or setting to invalid, recording the valid or invalid setting, and developing a program using an interface that is set to be valid or an interface that is not set to be invalid according to the setting. And a program development method. 8. A method of developing an application program by combining components having a plurality of interfaces, arranging a plurality of components, selecting such an arrangement component, and arranging the selected arrangement component. Selecting such a placed component; defining an arrangement specification for arranging the placed component; recording the defined arrangement specification; and Developing a program by arranging the components to be arranged. 9. A program for causing a computer to support the development of an application program using components having a plurality of interfaces, wherein the step of selecting a component, the step of selecting an interface for the selected component, Setting the enabled / disabled interface, recording the enabled / disabled setting, and using an interface that is set as enabled or an interface that is not set as disabled according to the setting. And a computer-readable recording medium recording a program for executing the steps of developing the program. 10. A program for causing a computer to support the development of an application program by combining components having a plurality of interfaces, arranging a plurality of components, selecting such an arrangement component, and Selecting such placed components to be placed in the placement component; defining placement specifications for placing the placed components; recording the defined placement specifications; and And a step of causing a component to be placed to be placed on the placement component to develop a program. 11. A program for causing a computer to support the development of an application program using components having a plurality of interfaces, the steps of: selecting a component; selecting an interface for the selected component; Setting the enabled / disabled interface, recording the enabled / disabled setting, and using an interface that is set to be enabled or an interface that is not set to be disabled according to the setting. A program that executes the steps of developing a program. 12. A program for causing a computer to support the development of an application program by combining components having a plurality of interfaces, arranging a plurality of components, selecting such an arrangement component, and Selecting such placed components to be placed on the placement component; defining placement specifications for placing the placed components; recording the defined placement specifications; and Causing the placed component to be placed on the placed component to develop a program.