JPH10222356A - Application generating device and application generating method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To quickly develop a software application without writing a program source code while easily grasping what kind of change occurs in a user interface screen in the result of an internal processing by simultaneously displaying layout information of a graphical user interface screen, event generating parts and their kinds and the parts of controlled system. SOLUTION: When a symbol expressing an even is selected in an editor (step 1701), the kinds of the event permitted to the parts which are connected to the symbol are read (step 1702) and they are displayed in a menu (step 1703). When menu selection is completed (step 1704), the connected parts and event information are registered in a table (step 1705). After that, the kind of the selected event is displayed in the symbol as a character string.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an application creating apparatus and an application creating method capable of developing a software application having, for example, a graphical user interface without writing source code.

[0002]

2. Description of the Related Art When creating a software application having a graphical user interface at present, it is possible to create a user interface screen with almost no source code by using a tool having a graphical editing function. It has become. In such a tool, the description of the internal processing is such that the creator describes the source code as a callback function for a user event or a system event occurring in a component arranged on the user interface screen. At this time, it was not possible for the developer to edit and refer to the definition of the screen and the definition of the internal processing in a centralized manner.

Also, when developing a software application over a plurality of screens, the developer creates a single screen, and during the development of the screen, the developer determines which screen to transition to after the screen. That is, the user has made a selection to edit the screen by explicitly specifying the name of the screen. At this time, the developer had to memorize the names of the adjacent screens.

Further, even when a graphical development environment is adopted, registration of information such as variables to be referred to at a plurality of locations has conventionally been dealt with by starting a text editor and creating a header file or the like. In this case, the developer had to create a file for defining information to be shared such as variables.

[0005]

According to the above-described program development method, a user event generated in a component such as a button arranged on a user interface screen,
Or control flow by system event,
Furthermore, it has been impossible to graphically and centrally refer to and edit the flow of data controlled by the control. As a result, it is necessary to create and store the names of parts such as buttons on the screen that are displayed in the program, and the variable names that store information related to the parts. In addition to that, unskilled people have to learn many writing styles of programming languages to describe what internal processing is performed according to the user's operation on the user interface, There are problems that it takes a lot of time until the productivity is improved, and that the controlled object cannot be confirmed on the editor.

Also, when defining a screen transition, it was impossible to list the order of the screens. Therefore, in order for the developer to recognize the order of the screen transitions and to specify the screen clearly, Many screens under development have to be searched.

Further, even if a graphical development environment is provided, if information is to be shared on a plurality of screens, a text editor is displayed in addition to the graphical editor because the information is described in a file to be registered using a text editor. At the same time, the visibility on the screen is reduced, and at the same time, the unskilled person has a problem that the registration itself becomes a burden.

As described above, although the conventional method is called a graphical development environment, it has many problems for unskilled workers and low productivity of software applications.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and has a screen layout and control flow of a software application having a graphical user interface. An object of the present invention is to provide an application creating apparatus and an application creating method that enable even an unskilled person to efficiently develop a GUI application by consolidating operations on symbols displayed above.

[0010]

According to the first aspect of the present invention, a GUI component (display component) is provided.
Means for storing in advance a symbol and a plurality of events for the GUI component, means for arranging the symbol for the GUI component on the screen, and means for displaying a plurality of events for the GUI component on the screen on which the symbol for the GUI component is arranged And means for selecting one event from the displayed plurality of events.

According to the second aspect of the present invention, a means for storing in advance a symbol and a plurality of events for a GUI part and a symbol and a plurality of events for data, a means for arranging a symbol for the GUI part on a screen, and the GUI Means for displaying a plurality of events for the GUI part on a screen on which symbols for the parts are arranged; means for selecting one event from a plurality of events for the displayed GUI part; Means for arranging symbols for the data, means for associating an event of the selected GUI component with a symbol for the arranged data on the same screen, and Means for displaying a plurality of events corresponding to the displayed data; From among a plurality of events for one
Means for selecting one of the events.

According to a third aspect of the present invention, in the application creating apparatus according to the first or second aspect, on the screen, a plurality of windows in which symbols are respectively arranged and transition information between the windows are displayed as directed line segments. And a means for displaying a symbol arranged in the window on at least one window on the screen. In the invention according to claim 4, 1
Means for displaying a plurality of windows in which symbols are arranged on one screen, and means for registering data sharable among the plurality of windows and displaying a box for storing symbols which can be taken out on the screen And means for associating a predetermined symbol in the window with a symbol stored in the box on the screen.

[0013] In the present invention, a step of storing a symbol and a plurality of events for a GUI part in advance, a step of arranging a symbol for the GUI part on a screen, and a screen on which a symbol for the GUI part is arranged An application creation method is provided, comprising: displaying a plurality of events for the GUI component; and selecting one event from the displayed plurality of events.

According to the present invention, a step of storing in advance a symbol and a plurality of events for a GUI part and a symbol and a plurality of events for data, a step of arranging a symbol for the GUI part on a screen, and Displaying a plurality of events for the GUI component on a screen on which symbols for the component are arranged; selecting one event from the plurality of events for the displayed GUI component; Arranging a symbol for the data, and associating an event of the selected GUI component with a symbol for the arranged data on the same screen; and arranging the symbol on the same screen. Displaying a plurality of events for the displayed data; From among a plurality of events for one
Selecting one of the events.

According to the present invention, a step of displaying a plurality of windows on which symbols are arranged on one screen, and registering data sharable among the plurality of windows on the screen. And displaying a box storing symbols that can be taken out, and associating a predetermined symbol in the window with a symbol stored in the box on the screen. Is provided.

According to the present invention, the layout information of the graphical user interface screen, the event occurrence parts, their types, and the parts to be controlled are simultaneously displayed, and it is easy to determine what changes occur in the user interface screen as a result of the internal processing. It is possible to quickly develop a software application while keeping track of it and without writing a program source code.

Further, according to the present invention, the order relation of the screens of the graphical user interface is stored and displayed, and the transition to the editing of the adjacent screen is facilitated.

Furthermore, registration and calling of information shared in a plurality of windows can be performed by mouse operation on a symbol, and can be performed easily and intuitively during editing.

[0019]

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

FIG. 1 is a diagram showing the configuration of a graphical user interface development apparatus and method for realizing the present invention.

The control unit 11 analyzes operation information input using the input means 10 such as a mouse or a keyboard. At the time of arranging the parts, the information of the symbol is read from the symbol definition information file 12, the arranged part information is written into the local data storage 16, and a display signal is sent to the display 13. The result is displayed on the display 17. At the time of data storage, the control unit 11 reads the placed component information from the local data 16 and sends the placed component information together with the source code information generation command to the generation unit 14 to generate the source code information file 15.

The definition of the screen transition information and the reflection of the result on the editing operation will be described.

First, a procedure for declaring a screen to be created will be described with reference to FIG. FIG. 3 shows a screen example in that case. In FIG. 3, reference numeral 30 denotes an editor screen according to one embodiment. When a symbol representing a screen is selected from the tool palette 31 (step 201), a frame is displayed at the position indicated by the mouse cursor (step 202). By dropping them on the editor screen 30, the symbols are arranged like symbols 32, 33, 34, and 35, respectively. When such an arrangement is completed (Step 20)
3) Display these symbols, assign IDs to these symbols, and register them in the table (local data storage unit 16) (step 204). Next, FIG.
The procedure for defining the screen transition information using will be described. FIG. 5 shows a screen example in that case. Tool palette 3
A directed segment, which is a symbol representing a screen transition, is selected from 0 (step 401), the start point is designated by the mouse cursor in the already arranged symbol screen (step 402), and the end point is designated by the mouse cursor. This is done within the arranged symbol screen (step 403).
In this case, a directed line segment 53 is drawn from the transition source screen 51 to the transition destination screen 52. As a result, the screen transition relation is set as an attribute of the directed line segment in the table (local data storage unit 16)
(Step 404).

The procedure for shifting to screen editing will be described with reference to FIG. 7 and 8 show screen examples in that case. Screen 70 to be edited among the arranged symbol screens
Is designated by the mouse cursor and double-clicked (step 601), screen layout information is read from the table (local data storage unit 16) (step 602), and the layout screen (editing screen) 80 is displayed. At the same time (step 603), the connection relation of the screens is read (step 604), and the icons of adjacent screens (symbols representing adjacent screens) 82, 83, 84
Is displayed (step 605).

The procedure for shifting to the editing of the adjacent screen will be described with reference to FIG. FIG. 10 and FIG. 11 show screen examples in that case. When the symbol 100 representing the adjacent screen displayed on the editor is pointed by the mouse cursor and double-clicked (step 901), the specified screen layout information is read from the table (local data storage 16) (step 901). 902), the layout screen (adjacent screen) 110 is displayed (step 903), the connection relation of the screen is read (step 904), and the icon 111 of the adjacent screen is displayed (step 905). Next, a procedure for displaying and editing the screen layout and internal processing in an original manner will be described.

First, the procedure for editing the screen layout will be described with reference to FIGS. FIG. 13 shows a screen example in that case. When a GUI component to be arranged is selected from the tool palette 131, the ID of the GUI component of the selected tool palette is set to the symbol definition information file 12
(Step 1201), and reads the default size of the selected GUI component (Step 1202).
Display a frame at the position indicated by the mouse cursor (Step 1)
203). When the arrangement operation on the editor screen 130 is completed (step 1204), the editor screen 13
It is arranged on the symbol 132 representing the edit target screen displayed on the screen 0 and registered in the table (local data storage 16) (step 1205). G placed
The UI component is displayed as a symbol 133.

After this operation, when an operation of selecting a change of the edit mode from the menu 134 is performed (step 14).
01) or when an operation such as switching the tool palette 131 to an internal processing component is performed, the symbol information defining the internal processing is read from the table, the offset is corrected (step 1402), and the symbol defining the internal processing is displayed on the screen. Draw on the top (step 1403).

The procedure for arranging symbols representing events will be described with reference to FIG. FIG. 16 shows a screen example in that case. In this screen, 161 is a cursor of a pointing device such as a mouse, and 162 is a screen to be edited. Now, a button press event of the button 166 arranged on the editor 160 is defined. That is, when a symbol representing an event is selected on the tool palette (step 1501), the default size of the selected component is read from the table (step 1502), and a frame 164 is displayed at the position indicated by the mouse cursor (step 1502). Step 1503). When the arrangement operation on the editor screen 160 is completed (step 1504), the symbol 164 representing the event is arranged on the symbol 162 representing the screen to be edited displayed on the editor screen 160 (step 1505). Thereafter, the button 166 and the symbol 164 representing the event are connected by a line segment 165, and when this is completed (step 1506), the relationship between the button 166 and the symbol 164 representing the event is registered in a table (step 15).
07).

The procedure for selecting the type of event will be described with reference to FIG. FIG. 18 shows a screen example in that case. As shown in the screen of FIG. 18, when the symbol 180 representing the arranged event is designated and selected, a menu 181 is displayed.
The types of events that can be specified are displayed, and any of them can be specified and selected. That is, when a symbol 180 representing an event is selected on the editor (step 1701), the type of event permitted for the component connected to the symbol is read (step 1701).
2) Display them on the menu 181 (step 1)
703). When the selection of the menu is completed (step 1704), information on the connected component and the event is registered in the table (step 1705). The type of the event selected after that is the character string 18 in the symbol 180.
It is displayed as 2.

FIG. 19 shows an example of information storage when an information storage instruction is given. In this example, the definition information is expressed in a format of lisp language. “Eventdef” is a reserved word that indicates the definition of an event.
This shows that an event called ButtonPress occurs in the part called tton1.

Next, a procedure for arranging symbols for defining an operation will be described with reference to FIG. FIG. 21 shows a screen example in that case. In this example, the operation of opening another screen by pressing a button is defined. A directed segment (control flow), which is a symbol representing an operation, is selected from the tool palette 210 (step 2001), and a symbol 21 representing an event is selected.
When the directed line segment 213 is drawn from the “1” to the screen 212 to be opened (steps 2002 and 2003), the order in which the processing is performed is displayed by a symbol 214 (step 2004), and the connection information is stored in a table. It is registered (step 2005).

Next, the procedure for selecting the type of operation will be described. FIG. 22 shows a screen example in that case. When the operation on the valid line segment is completed (step 2006), the menu 220 is selected and designated by the directed line segment representing the previous operation.
The type of operation that can be specified is displayed in (Step 200).
7) by making a selection (step 200)
8) The type of operation is determined and registered in the table (step 2009).

FIG. 23 shows an example of information storage when an information storage command is given. “Method” is a reserved word representing the definition of the operation, and “arg” is a reserved word representing the definition of the attribute of the operation. When an event called ButtonPress occurs in a part called pushbutton1 on the screen called sheet 22a, the operation called "operate" fires first, and the content is
This indicates that an open command is sent to the sheet 22c.

The procedure for defining data will be described with reference to FIG. FIG. 25 shows a screen example in that case. When a symbol representing data is selected from the tool palette 250 (step 2401), a frame is displayed at the position indicated by the mouse pointer (step 2402). When the placement operation is completed (step 2403), the symbol 151 representing the data is displayed.
153 is displayed (step 2404), and the information is registered in the table (step 2405).

The procedure for defining the data flow will be described with reference to FIG. When a data flow is selected from the tool palette 250 (step 2601), the start point indicated by the mouse pointer is a component or a variable (step 2602), and the end point is a component or a variable (step 260).
3) The valid line segment is displayed (step 2604), and the connection information is registered in the table (step 260).
5). Thus, for example, the symbol 15 representing data
1 and 153 are connected by a directed line segment 153 representing the flow of data.

The procedure for defining a trigger for a data flow will be described with reference to FIG. In this example, button 27
By pressing 0, a data flow represented by a directed segment 271 occurs. In order to define this, a directed segment 273 representing an operation is drawn from a symbol 272 representing an event to a directed segment 271 representing a data flow.

The procedure for selecting the type of operation will be described with reference to FIG. The type of operation that can be specified is displayed in the menu 280 by selecting and specifying the directed segment representing the previous operation,
The type of operation is determined by the selection.

FIG. 29 shows an example of information storage when an information storage instruction is given. pushbu on the screen called sheet 22a
When an event called ButtonPress occurs in the part called tton1, the operation called Operate is fired first, and the contents are copied from data1 to data2.
Is sent.

Next, a procedure for sharing information between a plurality of screens will be described.

First, a procedure for declaring information to be shared between a plurality of screens will be described with reference to FIG. FIG. 31 shows a screen example in that case. A symbol 311 representing an area for storing information to be shared is selected from the tool palette 310 (steps 3001 and 3002) and arranged on the editor (steps 3003 and 3004). There, the information 312 to be shared is dragged or dropped onto the area 311 (step 3005). Thereafter, the information to be shared is displayed as the symbol 313 in the area 311 and registered as shared information in the database of the editor (step 3006).

A procedure for extracting information declared to be shared among a plurality of screens will be described with reference to FIG. FIG. 33 shows a screen example in that case. In editing the screen 330 different from that in FIG. 31 (steps 3201 to 205), the symbol 33 of the information to be used from the area 331 for storing the shared information
2 is selected and dragged or dropped on the editor (step 3206). The shared information to be used later is displayed as a symbol 333 on the editor, and the screen 3
The information is registered in the database as information used in 30 (step 3207).

In the example shown in FIG. 27, the operation is executed with the data flow between the screens or within the screen as a trigger. However, as shown in FIG. 34, the arrival of data from the server or the like is used as the trigger. In this case, if the GUI components 341 to 344 relating to the server are prepared in advance, they can be displayed and edited in the same manner as in the case shown in FIG. 27 and the like. In addition to the server, a timer or the like can be used as a trigger. In this case, if related GUI components are prepared in advance, they can be originally displayed and edited.

[0043]

According to the present invention, in the development of software having a graphical user interface, screen transition definitions, editing screen changes, internal processing definitions, and shared information among a plurality of screens are graphically defined on an editor. Can be registered, so that even an unskilled person can easily and quickly develop a software application having a graphical user interface.

[Brief description of the drawings]

FIG. 1 is a configuration of a graphical user interface development device according to an embodiment of the present invention.

FIG. 2 is a flowchart relating to screen layout in the screen configuration definition.

FIG. 3 shows a layout of a screen to be created.

FIG. 4 is a flowchart relating to definition of screen transition.

FIG. 5 is a definition of a transition relationship between screens.

FIG. 6 is a flowchart regarding transition from a screen configuration definition to a screen layout definition.

FIG. 7 shows selection of an edit target screen.

FIG. 8 is a display of an edit target screen.

FIG. 9 is a flowchart regarding transition to an adjacent screen.

FIG. 10 shows selection of an adjacent screen to be edited.

FIG. 11 is a display of an adjacent screen to be edited.

FIG. 12 is a flowchart relating to the arrangement of GUI parts.

FIG. 13 is a layout of GUI parts.

FIG. 14 is a flowchart relating to centrally displaying and editing an event and a screen layout.

FIG. 15 is a flowchart regarding the arrangement of symbols representing events.

FIG. 16 shows an arrangement of symbols in an event definition.

FIG. 17 is a flowchart regarding selection of an event type.

FIG. 18 shows selection of an event type in the definition of an event.

FIG. 19 is definition information when an event is defined.

FIG. 20 is a flowchart relating to the definition of an operation.

FIG. 21 shows an arrangement of symbols in a control flow definition.

FIG. 22 shows selection of a method type in a control flow definition.

FIG. 23 shows definition information when a control flow is defined.

FIG. 24 is a flowchart relating to definition of data.

FIG. 25 shows the arrangement of symbols in the definition of a data flow.

FIG. 26 is a flowchart relating to definition of a data flow.

FIG. 27 shows the arrangement of symbols in a data flow trigger definition.

FIG. 28 shows selection of a method type in definition of a trigger of a data flow.

FIG. 29 shows definition information when a data flow is defined.

FIG. 30 is a flowchart relating to declaration of information shared between screens.

FIG. 31 Transfer of data shared between screens.

FIG. 32 is a flowchart regarding use of information shared between screens.

FIG. 33 is a view of data shared between screens.

FIG. 34 is a view showing another example regarding the definition of data.

[Explanation of symbols]

 Reference Signs List 10 input means 11 control unit 12 symbol definition information file 13 display unit 14 generation unit 15 source code information file 16 local data 17 display

Claims (7)

[Claims] 1. A means for arranging a symbol for a display component on a screen, and:
An application creating apparatus, comprising: means for displaying a plurality of events for the display component; and means for selecting one event from the plurality of displayed events. 2. A means for arranging a symbol for a display component on a screen, and:
Means for displaying a plurality of events for the display component; means for selecting one event from a plurality of events for the displayed display component; means for arranging symbols for the data on the same screen Means for associating an event of the selected display component with a symbol for the arranged data on the same screen; and means for displaying a plurality of events for the arranged data on the same screen. Means for selecting one event from a plurality of events for the displayed data. 3. The application creating apparatus according to claim 1, wherein on the screen, transition information between a plurality of windows in which symbols are arranged is displayed by a line segment, and at least on the screen, Means for displaying a symbol arranged in one window with respect to one window. 4. A means for displaying a plurality of windows in which symbols are respectively arranged on the same screen, and storing, on the screen, data which can be shared between the plurality of windows and which can be taken out. An application creating apparatus, comprising: means for displaying a box to be displayed; and means for associating a predetermined symbol of the window with a symbol stored in the box on the screen. 5. A symbol for a display component is arranged on a screen, and a plurality of events for the display component are displayed on a screen on which the symbol for the display component is arranged.
An application creating method, wherein one event is selected from the plurality of displayed events. 6. A step of arranging a symbol for a display component on a screen, and:
Displaying a plurality of events for the display component; selecting one event from the plurality of events for the displayed display component; and arranging a symbol for the data on the same screen. (C) associating an event of the selected display component with a symbol for the arranged data on the same screen; and displaying a plurality of events for the arranged data on the same screen. Selecting one event from a plurality of events for the displayed data. 7. A step of displaying a plurality of windows in which symbols are respectively arranged on the same screen, and registering data that can be shared among the plurality of windows and storing symbols that can be taken out on the screen. Displaying a box to be displayed, and associating a predetermined symbol in the window with a symbol stored in the box on the screen.