JP2007122744A - Program development support device, program development support method, medium and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To develop an unitarily designed program even when utilizing a number of interfaces or components. <P>SOLUTION: The program development device 101 for developing an application program by use of a component having a plurality of interfaces, includes a component selecting module 101 for having the component selected, an interface selection module 102, 103 for having the interface selected for the selected component, and setting the selected interface in a valid or invalid state, a recording unit 4 for retaining a set record 11 of having set the interface in the valid or invalid state, and an edit module 120 for supporting the development of the program by use of the interface set in the valid state or the interface that is not set in the invalid state in accordance with the set record 11. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

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

A user of a component (for example, an ActiveX control provided by Microsoft Windows in the US) could develop a program by placing the component in a container (for example, a Microsoft Visual Basic form). Users of such components were able to use all the interfaces (for example, properties, methods, and events) exposed by each component.

  Some components have utility value in combining a plurality of components. In such a component, a combination of components can be used by setting an interface of each component for each component.

  In the group development of applications, a template with a fixed form could be created by using the template function. Such a template has been used as an initial setting of an application.

  Today, as the functionality of such components increases, the number of interfaces increases. On the other hand, component users do not use all of these interfaces.

  On the other hand, to find the target interface from a large number of interfaces, a great deal of effort such as manual reading was required.

  When a plurality of components are used in combination, for example, when a group box and option button, a toolbar and command button, a tab and property page, a property sheet, or the like is used, the combination of them may be fixed. However, even for such a typical combination, the user has to set an interface for each individual component.

  Furthermore, when developing an application in a group, the template function could be used to determine the template at the initial stage of development. However, at the stage of developing the target application from the template, all the component interfaces were available. There were also a wide variety of component combinations.

For this reason, interface usage and combination methods are not unified, and application designs often differ. Furthermore, since the usage method is not unified, the maintenance of the program is inefficient.
Japanese Patent Laid-Open No. 10-40090

The present invention has been made in view of such problems of the conventional technology. A technical problem 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 many interfaces.

  Further, the technical problem of the present invention is to provide a function for developing an application program having a unified design even when a component capable of using a large number of interfaces or a large number of combinations is used.

  Furthermore, the present invention is to improve the maintainability of the application program by such development.

  The present invention employs the following means in order to solve the above problems.

  That is, the present invention is a program development device (1, 10) that develops an application program using components having a plurality of interfaces, a component selection unit (101) for selecting a component, and a selected component An interface selection unit (102, 103) for selecting an interface and setting the selected interface to be valid or invalid, a recording unit (4) for holding a setting record (11) in which valid or invalid setting is recorded, According to the setting record (11), a component editing unit (120) that develops a program using an interface that is set as valid or an interface that is not set as invalid is provided.

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

  Preferably, the program development device (1, 10) includes a group definition unit (43) that defines a group of a plurality of users, and a group setting record designation unit (13a) that designates a setting record that can be used for the group. And may be further provided.

  The present invention is also a program development apparatus (1, 10) that develops an application program by combining components having a plurality of interfaces, and arranges a plurality of components, and an arrangement component selection unit that selects such arrangement components (111), a placement component selecting unit (112) for selecting such a placement component to be placed in the selected placement component, and a placement specification defining unit (stipulating a placement specification for placing the placement component) 112, 113), a recording unit (4) holding an arrangement specification record (11) for recording a prescribed arrangement specification, and an arrangement component to be arranged in the arrangement component according to the arrangement specification record (11) Component editor for developing programs 120) and may be equipped with a.

  Preferably, an arrangement specification record specifying unit (11) for designating one of the plurality of arrangement specification records is further provided, and the component editing unit (120) is an interface set to be valid in the designated arrangement specification record. Alternatively, the program may be developed using an arrangement specification that is not set as invalid.

  Preferably, the program development device (1, 10) includes a group definition unit that defines a group of a plurality of users, and a group arrangement specification record designation unit that designates an arrangement specification record (11) that can be used for the group. (13) may be further included.

In addition, the present invention is a method for developing an application program using components having a plurality of interfaces, the step of selecting a component (S3), and the step of selecting an interface for the selected component (S6). A step of setting the selected interface as valid or invalid (S7), a step of recording the valid or invalid setting (S8), and an interface set as valid or invalid according to the setting. Steps (S21-S28) for developing a program using a non-interface may be used.

  Further, the present invention is a method for developing an application program by combining components having a plurality of interfaces. The step of selecting a placement component (S11) for placing a plurality of components, and the selected placement component A step of selecting such a placement component to be placed (S12), a step of defining a placement specification for placing the placement component (S13), and a step of recording the prescribed placement specification (S16) According to the layout specification, the program may be developed (S21 to S28) by placing the placement component on the placement component.

  The present invention may also be a program that causes a computer to execute the above steps. Further, such a program may be recorded on a computer-readable recording medium.

  The present invention may also be a data communication signal embodied in a carrier wave having a program code portion that causes a computer to execute the above steps.

  According to the present invention, it is possible to limit the interface used in the component and the combination method of the components, facilitate the search for the interface, and improve the work efficiency. Further, according to the present invention, it is possible to unify the operations of components used in application programs. 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.

Preferred embodiments of the present invention will be described below with reference to the drawings.
<< First Embodiment >> A first embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a hardware configuration diagram of a program development apparatus 1 according to the present embodiment, FIG. 2 is a functional configuration diagram of the program development apparatus 1, and FIGS. 3 and 4 are layout tools shown in FIG. FIG. 5 is a setting operation example of a component usage method (hereinafter referred to as a style), and FIG. 6 is an example of a style definition file 11 that defines the style set in FIG. 7 and 8 are examples of layout of group components by the layout tool 10, FIG. 9 is an example of a style setting operation for the group components, and FIG. 10 defines the style set by FIG. FIG. 11 and FIG. 12 show examples of the style definition file 11, and FIG. 11 and FIG. A flow chart showing the processing, FIG. 13 is a flowchart showing the processing of the layout tool 10 in the development of programs by laying the components.
<Hardware Configuration> FIG. 1 is a hardware configuration diagram of the program development apparatus 1. The program development apparatus 1 includes a CPU 2 that executes a program, a memory 3 that stores a program that is executed by the CPU 2, data that is processed by the CPU 2, a hard disk 4 that records the program and data, a menu, an icon, and a message. And the like, 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 the network. ing.

  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 a program executed by the CPU 2 and data processed by the CPU 2.

  The hard disk 4 records programs 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 of programs developed by the user, icons, messages, and the like. For example, a CRT, a liquid crystal display, or the like is used as the display device.

  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 indicating device, a laser indicating device, a touch panel, or the like can be used.

The communication interface 8 accesses the network and communicates with other hosts on the network according to instructions from the CPU 2.
<Functional Configuration> FIG. 2 is a functional configuration diagram of the program development apparatus 1. The program development apparatus 1 is realized by the CPU 2 executing the window system 12 and the layout tool 10 linked to the window system 12.

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

  The component library 14 holds a large number of components and is open to the user. The user uses this component as a part when developing an application program.

  The layout tool 10 refers to the components in the component library 14 and creates a program by combining these components.

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

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

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

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

  An event is a type of user operation detected by the component. The event includes, for example, movement of a display on the screen (called a pointer) corresponding to the operation of the pointing device 7, entry and exit of the pointer to the display area of the component on the screen, and the pointing device 7 on the display area. Some are by pressing a button or operating the keyboard 6.

  In the present embodiment, the layout tool 10 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 and the like.

  The first feature of the present layout tool 10 is that a function for restricting what can be used is provided for a large number of interfaces of a large number of components as described above. Limiting the available interfaces will restrain the developer. As a result, operation uniformity occurs in the developed application program. Therefore, in this embodiment, such a constraint is called a style. Also, providing the 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 a component is called a group component. A component arranged by a group component is called a placement component. In the group component, there are various arrangement methods for arranging the placement target component.

  The second feature of the present layout tool 10 is that a function for limiting the arrangement method of the arrangement target components is provided for such a group component. Such a restriction is also called a style, as is the case with the above interface.

  The style defined in 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 number of components. Further, the definition contents of different styles can be saved in style definition files 11a, 11b having different names.

The layout tool 10 holds in the style instruction file 13 which style definition file 11 or the like is currently used. The layout tool 10 selects a style definition file in accordance with the instruction of the style instruction file 13 and develops a program.
<Interface Style> FIG. 3 shows an example of an operation for arranging components by the layout tool 10. In this example, one button named CmCommand1 is arranged in an editing window 120 called a main form (MainForm). The layout tool 10 can define events detected by such buttons. Such a definition is executed by "Edit event procedure" in the pull-down menu of FIG.

In the example of FIG. 3, no style is set in the layout tool 10. Therefore, when the user selects “Edit Event Procedure”, a number of events such as Click and GotFocus can be selected. In this state, all events originally provided for the button CmCommand1 can be used.

FIG. 4 is an example of an editing window 120 in which available events are limited. In the case of FIG. 4, only three types of events, Click, GotFocus, and LostFocus, are set to be usable in the style definition file. In such a case, the user can select only the available events in the edit window 120.

  FIG. 5 shows a setting operation example for setting the style as shown in FIG. When the user activates the layout tool 10 and selects control customization from a menu (not shown), a component screen 101 is displayed. Here, control customization is a function for setting a style for an interface.

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

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

  The event moved to “unused event” can be returned to the “used event list” column by the center button “<” or “<<”. In this way, when only “Click”, “GetFocus”, and “LostFocus” are left in the “event list to be used” as in the unused interface setting screen 103 and OK is pressed, the setting of such a style is confirmed.

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

FIG. 6 is a definition example (1) of the style definition file generated by the setting operation as described above. In this style definition file 11, as an event of a command button control component (indicated by CommandButton.Events), for example, a key press on the keyboard 6 (KeyDown), a key press state (KeyPress), and a key press release ( KeyUp) is not used as an event. In addition, it is specified that mouse button press (MouseDown), mouse move (MouseMove), and mouse button press release (MouseUp) are not used as events.

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

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

In this operation, the user first selects a group component (CmGroup) from the selection box 30 for selecting a component as a main form (MainForm).
). 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 CmGroup3).

  As described above, in general, when components are arranged in the group component, the user must repeat the operation for the number of components to be arranged. Also, the user can freely specify the direction of placement and the position of placement.

FIG. 8 shows an operation example of the editing window 120 when the arrangement specification is defined in the style definition file 11. Also in this operation, three components called option button controls are arranged in a group component called group control (CmGroup) as in FIG. 7 (CmGroup1, CmGroup2, and CmGroup3).

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

  FIG. 9 shows a setting operation example for setting the style as shown in FIG. When the user activates the layout tool 10 and selects customize group control 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 styles can be set. When the user selects a desired group component, for example, “GroupBox Control”, and presses the “Next” button, a placement component selection screen 112 is displayed.

The placed component selection screen 112 displays a list of components that can be placed in the group component named “GroupBox Control”. Here, when the user selects a component ("CmOptionButton Control" in FIG. 9), sets the number to 3, and presses "Next", an arrangement direction designation screen 113 is displayed.

On the arrangement direction designation screen 113, the user selects an arrangement direction. In FIG. 9, the vertical direction is selected. Thereafter, when the completion button is selected, the arrangement specification of “CmOptionButton Control” in the group component named “GroupBox Control” is fixed.

  Then, the layout tool 10 inquires about the name of the style definition file 11 or the like that stores the style. When the user inputs a style definition file name, a newly defined style is added to the style definition file 11. Thereafter, the layout tool 10 ends the customization.

FIG. 10 is a definition example (2) of the style definition file 11 generated by the setting operation as described above. In the style definition file 11, the arrangement of option buttons in a group component called a group box is defined (indicated by GroupBox.OptionButton). In this example, there are 3 option buttons (OptionButton = 3)
It is specified that the arrangement direction is the vertical direction (Alignment = Vertical).

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

For example, the style definition file 11 stores a style for developing an inventory management system. This is a program that supports raw material inventory management, product inventory management, and purchase / shipment destination management. The style definition file 11 may define a style that unifies inventory management operations and screen appearance. The members of this program development project share this style definition file 11.

  For example, the style definition file 11a defines the style of a reservation system development project such as a hotel or a trip. This is a system that executes vacant room information reference, reservation input, customer information management, and the like. In the style definition file 11, a style that unifies vacant room information reference, reservation operation, and the like may be defined.

  Further, for example, the style definition file 11b defines the style of the employee work management system development project. This is a system that provides a process for issuing notification documents such as business trips and vacations, a reference process for working status such as vacation acquisition status and overtime, and a communication function between employees such as an electronic bulletin board and email. In the style definition file 11, a style that unifies operations and the like at the time of work management may be defined.

  The user develops an application program within a range of allowed interfaces and arrangement methods. In this case, the user can use the style definition file 11 or the like properly according to the program development target. That is, the user specifies the 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 arrangement specification designated as usable in the designated style definition file 11 or the like. <Operation and Effect> FIG. 11 shows the style setting process for the interface of the component. When the user selects control customization from a menu (not shown) of the layout tool 10, the CPU 2 executes the process shown in FIG.

  First, the CPU 2 displays a list of components whose styles can be set (S1).

  In this state, the CPU 2 waits for a user operation (S2, S3). When detecting the operation of the user, the CPU 2 determines whether or not the operation is a press of a cancel button (S2).

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

  When the user operation is not pressing the OK button but pressing the customize button, the CPU 2 determines whether or not the user is selecting a component (S3). When the user is not selecting a component (N in S3), the CPU 2 returns the control to the user operation waiting state.

  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 again waits for a user operation (S5, S6). That is, here, the CPU 2 waits for the user to select an unused interface.

  When the user's operation is to cancel the selection of an unused interface, the CPU 2 returns the control to S1.

  If the user operation is an unused interface selection OK, the CPU 2 confirms the designated unused interface (S7). Here, “determined” refers to reading from the screen the designation of an unused interface set as in the unused interface setting screen 103 of FIG. Then, the CPU 2 returns the control to S1.

  FIG. 12 shows the style setting process for the group component. When the user activates the layout tool 10 and selects customization of 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 (S11).

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

  Further, when the user presses the “Next” button, the CPU 2 causes 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 is terminated.

  On the other hand, when the user presses the “return” button (see FIG. 9) on each screen for selecting the group component, selecting the component to be placed, and specifying the number of placement, the CPU 2 controls each of the previous screens. return. If the user presses the cancel button (see FIG. 9) on any screen, the CPU 2 ends the process without doing anything.

  FIG. 13 shows processing when a component is laid out and a program is developed. When the user activates the layout tool 10 and selects a component layout from a menu (not shown), the CPU 2 executes the process of FIG.

  In this process, first, the CPU 2 determines whether or not the user selects a style (S21). The selection of the style means selection of which of the plurality of style definition files 11 or the like is to be followed.

When the user selects a style, the CPU 2 stores the style definition file 1 in the display device 5.
A list such as 1 is displayed and the user is allowed to select (S22). Thereafter, the CPU 2 advances the control to S23.

  On the other hand, when the user does not select a style in S21, the CPU 2 maintains the style currently used or advances the control to S23 while the style is not selected. The current style is the style when the layout tool 10 was used last time. “Unused style” means that a style has never been used, and an unlimited number of interfaces and group components can be used.

  S23 to S27 are waiting for a user operation. When a user operation is detected, the CPU 2 first determines whether or not the group component is selected (S23).

  When the user operation is group component placement selection, the CPU 2 executes group component placement processing (S24). In this process, according to the specified style definition file 11, the user-specified placement component is placed in the user-specified group component. Thereafter, the CPU 2 returns the control to S23.

  When the user operation is not the arrangement of the group component, the CPU 2 determines whether or not the user operation is a component interface setting selection (S25).

  If the user operation is interface setting selection, the CPU 2 executes interface setting processing (S26). In this process, the CPU 2 sets a user-specified interface in a user-specified component according to a specified style definition file 11 and incorporates it in a screen (for example, MainForm). Thereafter, the CPU 2 returns the control to S23.

  When the user operation is not interface setting selection, the CPU 2 determines whether or not the user operation is a process end designation (S27).

  When the user operation is not the designation of the end of the process, the CPU 2 returns the control to S23. On the other hand, if the user operation is a selection to end the process, the CPU 2 saves the layout result (S28) and ends the layout process.

  As described above, in the program development apparatus 1 according to the present embodiment, the interfaces that can be used in the components and the component arrangement specifications can be limited in advance.

  As a result, the user does not need to be familiar with all of the vast interfaces in vast components. Since the user only needs to be familiar with the components and interfaces that are defined for use in the project in which he participates, the development efficiency is improved.

  Further, according to the program development apparatus 1, the user interface can be unified in a system development project by a plurality of members.

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

For example, a user develops an inventory management system according to the style definition file 11 in the morning. Then, the user develops a reservation system such as a hotel or a trip in the afternoon according to the style definition file 11a. According to this program development device 1, the risk of a user developing such a plurality of projects in parallel confusing user interface specifications is reduced.
<Modification> In the above embodiment, the style definition file 11 and the like are held on the hard disk 4 of the program development apparatus 1. However, the implementation of the present invention is not limited to such a configuration. For example, the style definition file 11 or the like may be held on another computer different from the program development apparatus 1. That is, in an environment where a user develops a program using a plurality of program development apparatuses 1 such as a personal computer, the style definition file may be held 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 apparatus 1 of the first embodiment, an example is shown 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, program development by components is exemplified in a network environment including 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 or the like, and is restricted by the style definition file 11 or the like designated by the system administrator. Other configurations and operations are the same as those described in the first embodiment. Therefore, the drawings in FIGS. 1 to 13 are referred to as necessary.

  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 apparatuses 1a and 1b connected via a network 50. Since the hardware configurations of the server 41 and the program development device 1a are the same as those in FIG. 1, the description thereof is omitted.

  The server 41 includes a password file 42, a group file 43, a style instruction file 13a, a plurality of style definition files 11, and the like. Since the configuration and functions of the style definition file 11 and the like are the same as those in the first embodiment, description thereof is omitted.

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

  The group file 43 records a group name in the system and a user name belonging to the group.

  A style name used for each group or each user is specified in the style instruction file 13a. Here, the style name is a name of the style definition file 11 or the like. The style instruction file 13a is set by a system administrator.

  When a 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 program development device 1a or the like. When the layout tool 10 is 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 user operation 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 users on the network can be managed centrally. Further, by placing the style definition file 11 and the like in the server 41, it is not necessary to individually define the style instruction file 13a in the program management apparatuses 1a and 1b.

Further, in the server 41 of this embodiment, in addition to specifying the style definition file 11 and the like for the user name, the style definition file 11 and the like are collectively specified for the group to which the user belongs. For this reason, it is not always necessary to set a style individually for each person. For this reason, the operation at the time of designating the style definition file 11 etc. can be simplified.
<Modification> In the first embodiment, an example has been shown in which a user freely selects a style to be used. In the second embodiment, an example is shown in which the style definition file 11 or the like is placed on the server 41 and the administrator specifies the style used by each user. A program development environment may be constructed by combining the first embodiment and the second embodiment.

  For example, the style specified in the style instruction file 13a of the server 41 is used as a default. Users can select their own style individually. The selected style is recorded in the server 41 or the program development device 1a. This user develops a program in accordance with a preferentially selected style.

On the other hand, a user who has not selected a style follows the default designation placed on the server 41. By adopting such a system, those who participate in a large number of projects can freely select the style definition file 11 etc., and those who have little experience can forcibly develop programs 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 the computer to read and execute the control program for the recording medium, the computer can function as the program development apparatus 1 described in the above embodiment.

  Here, the computer-readable recording medium refers to a recording medium in which information such as data and programs is accumulated by electrical, magnetic, optical, mechanical, or chemical action and can be read from a computer. Examples of such a recording medium that can be removed from the computer include a floppy (registered trademark) disk, a magneto-optical disk, a CD-ROM, a CD-R / W, a DVD, a DAT, an 8 mm tape, and a memory card. .

Further, there are a hard disk, a ROM (read only memory), and the like as a recording medium fixed to the computer.
<< Data communication signal embodied in carrier wave >> The above program can be stored in a hard disk or memory of a computer and distributed to other computers through a communication medium. In this case, the program is transmitted through a communication medium as a data communication signal embodied by a carrier wave. And the computer which received the distribution can be functioned as the program development apparatus 1 of the said embodiment.

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

The carrier wave is an electromagnetic wave or light for modulating the data communication signal. However, the carrier wave may be a DC signal. In this case, the data communication signal has a baseband waveform without a carrier wave. 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 having a voltage of 0 is used as a carrier wave).
<< Others >> This embodiment discloses the following invention.

(Supplementary Note 1) A program development apparatus that develops an application program using components having a plurality of interfaces, a component selection unit that selects a component, and an interface that is selected for the selected component. An interface selection unit that is set to be valid or invalid, a recording unit that holds a setting record that records the setting of valid or invalid, and an interface that is set to be valid according to the setting record, or that is not set to be invalid A program development device including a component editing unit that develops a program using an interface.

(Additional remark 2) It further has the setting record designation | designated part which designates one of the said several setting records, and the said component edit part is set to the interface set as effective in the designated setting record, or set as invalid. The program development apparatus according to appendix 1, wherein the program is developed using a non-interface.

(Additional remark 3) The program development apparatus of Additional remark 1 further provided with the group definition part which defines the group which consists of a some user, and the group setting record designation | designated part which designates the setting record which can be used with respect to the said group.

(Additional remark 4) It is a program development apparatus which develops an application program combining the component which has a some interface, the arrangement component selection part which selects such an arrangement | positioning component which arranges a some component, and the said selected arrangement | positioning A placement component selection unit for selecting such a placement component to be placed on the component, a placement specification defining unit for defining a placement specification for placing the placement component, and a placement for recording the prescribed placement specification A program development apparatus comprising: a recording unit that retains a specification record; and a component editing unit that develops a program by arranging a placement component on the placement component according to the placement specification record.

(Additional remark 5) It further has the arrangement specification record designation | designated part which designates one of the said several arrangement specification records, and the said component edit part develops a program using the arrangement specification prescribed | regulated in the designated arrangement specification record The program development apparatus according to supplementary note 4 to be executed.

(Additional remark 6) The program development apparatus of Additional remark 4 further provided with the group definition part which defines the group which consists of a some user, and the group arrangement | positioning specification record designation | designated part which designates the arrangement | positioning specification record which can be used with respect to the said group .

(Supplementary note 7) A method of developing an application program using a component having a plurality of interfaces, the step of selecting a component, the step of selecting an interface for the selected component, and enabling or disabling the selected interface A step of setting to invalid, a step of recording the valid / invalid setting, and a step of developing a program using an interface set to valid or an interface not set to invalid according to the setting. A program development method consisting of:

(Supplementary Note 8) A method for developing an application program by combining components having a plurality of interfaces, arranging a plurality of components, selecting such a placement component, and placing the component on the selected placement component Selecting the placement component, defining a placement specification for placing the placement component, recording the defined placement specification, and placing the placement component on the placement component according to the placement specification. A program development method comprising the steps of placing a placement component and developing a program.

(Supplementary Note 9) A program that allows a computer to support development of an application program using components having a plurality of interfaces, the step of selecting a component, the step of selecting an interface for the selected component, Setting the enabled or disabled interface, recording the enabled or disabled setting, and programming using an interface that is enabled or disabled according to the setting. A computer-readable recording medium having recorded thereon a program for executing the step of developing the program.

(Supplementary Note 10) A program for supporting development of an application program by combining a component having a plurality of interfaces with a computer, arranging a plurality of components, selecting such an arrangement component, and the selected arrangement According to the placement specification, the step of selecting such a placed component to be placed on a component, the step of defining a placement specification for placing the placed component, the step of recording the defined placement specification, A computer-readable recording medium storing a program for executing a step of developing a program by arranging a placement component on the placement component.

(Supplementary Note 11) A data communication signal embodied in a carrier wave having a program code portion that allows a computer to support development of an application program using components having a plurality of interfaces. Selecting an interface for the component; setting the selected interface to be enabled or disabled; recording the enabled or disabled setting; an interface set to be enabled according to the setting; or And a data communication signal having a program code portion for causing the program to be developed using an interface not set to invalid.

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

The hardware block diagram of the program development apparatus 1 which concerns on 1st Embodiment of this invention. Functional configuration diagram of program development device 1 Component layout example by the layout tool 10 (1) Component layout example by the layout tool 10 (2) Example of setting style for component Example of style definition file 11 (1) Layout example of group component by layout tool 10 (1) Layout example of group component by layout tool 10 (2) Style setting operation example for group component Example of style definition file 11 (2) Flow chart (1) showing processing of layout tool 10 at the time of style setting operation Flow chart showing processing of layout tool 10 at the time of style setting operation (2) Flow chart showing processing of layout tool 10 when developing a program The system block diagram of the program development apparatus 1 which concerns on 2nd Embodiment of this 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 Placed component selection screen 113 Arrangement direction Specification screen 120 Edit window

Claims (6)

A program development support apparatus that develops an application program by combining components having a plurality of interfaces,
A placement component selection unit that selects a placement component that places a plurality of components, a placement component selection unit that selects the placement component that is placed in the selected placement component, and
An arrangement specification defining section for defining an arrangement specification for arranging the placement target component;
A recording unit for holding an arrangement specification record for recording the prescribed arrangement specification;
A program development support apparatus comprising: a component editing unit that develops a program by placing a placement component on the placement component according to the placement specification record. An arrangement specification record designating unit for designating one of the plurality of arrangement specification records;
The program development support device according to claim 1, wherein the component editing unit develops a program using an arrangement specification defined in a designated arrangement specification record. A group definition section for defining a group of a plurality of users;
The program development support apparatus according to claim 1, further comprising: a group arrangement specification record designation unit that designates an arrangement specification record that can be used for the group. A development support method for supporting the development of an application program by combining components having a plurality of interfaces.
Selecting such placement components to place multiple components;
Selecting such a placed component to be placed on the selected placed component; defining a placement specification for placing the placed component;
Recording the defined placement specification;
A development support method for supporting the development of a program comprising the steps of placing a placement component on the placement component and developing a program according to the placement specification. A program that supports the development of an application program by combining a component having a plurality of interfaces with a computer,
Selecting such placement components to place multiple components;
Selecting such a placed component to be placed on the selected placed component;
Defining a placement specification for placing the placed component;
Recording the defined placement specification;
A computer-readable recording medium recording a program for executing a step of developing a program by arranging a placement component on the placement component in accordance with the placement specification. A program that supports the development of an application program by combining a component having a plurality of interfaces with a computer,
Selecting such placement components to place multiple components;
Selecting such a placed component to be placed on the selected placed component;
Defining a placement specification for placing the placed component;
Recording the defined placement specification;
A program causing a placement component to be placed on the placement component and developing a program according to the placement specification.

Images