JP6531855B2 - INFORMATION PROCESSING APPARATUS, CONTROL METHOD FOR INFORMATION PROCESSING APPARATUS, AND PROGRAM - Google Patents

Description

  The present invention is a development using an automatic program generation device, and enables generation of a screen to be confirmed in a short time even if the development of each module such as business logic and database model is incomplete. It relates to technology.

  Conventionally, in order to support development of a web application, a user has a GUI layout (a part displayed as HTML at the time of program execution), a business logic, and a tool (product) for automatically generating a database model. When creating a screen to be displayed by a web application using these development support tools, it is necessary to define the definition for each tool (product) for components such as input fields and buttons. In order to make screen creation easy for developers and others, there is also a tool equipped with an editor that graphically edits the HTML displayed by the application.

  However, in the conventional system, when trying to confirm the HTML finally generated during development (definition of the application based on the rules in the program automatic generation tool), the screen (HTML) as an automatic program generation tool It was necessary to use tools that define business logic, database models, etc. separately and associate them later.

  Patent Document 1 describes a technique relating to a web application authoring tool that generates a web screen by defining an event in a field called an item such as a display item and an event in a field called a behavior together as an action execution or an error check. It is done. The authoring tool has an editorial view for defining the arrangement of fields and behaviors, and can generate HTML and script code by instantiation to generate dynamic web pages.

JP 2003-99257 A

  However, in the technique of Patent Document 1, there are cases where the state of the screen (HTML) can not be confirmed in the middle of development. That is, by developing only the screen (HTML) first, it is necessary to complete creation of a behavior that is not in an incomplete behavior or is about to be created. That is, the event associated with the item on the screen can not confirm the state of the screen (HTML) unless a certain level of operation (if not the final product) is guaranteed.

  Therefore, there is a problem that while developing in cooperation with the screen (HTML) and the behavior, it is not possible to confirm only the screen (HTML) in a stage where each cooperation is not completely taken.

  Furthermore, since the authoring tool described in Patent Document 1 creates HTML to operate dynamically on the client (web browser), business logic and data models that operate in conjunction with the application server are When considering a web application of the included scale, it is impossible to confirm the state of the screen (HTML) without generating the program for the screen (HTML), such as compilation of business logic and generation of data model. . This will cause the problem of reduced development efficiency.

An object of the present invention, by displaying the preview screen corresponding to the screen information more generated program executed by the server efficiently is to provide a technique for improving the development efficiency of applications.

The present invention is an information processing apparatus, a definition information for generating an executable program in the server, the definition information relating to screen item included in the screen information generated by the previous SL program is executed a definition storage section for storing, using the definition information stored by said definition storage unit, and a program generation means for generating a program for generating a pre-Symbol screen information stored by the previous SL definition storage means Display definition information extraction means for extracting definition information related to the display of the screen item among the definition information, and a preview screen corresponding to the screen information generated by execution of the program, by the display definition information extraction means a preview screen generating means for generating using the definition information relating to the display of the screen item to be extracted, the preview screen generator means Characterized in that to function as a preview screen display means for displaying the generated preview screen.

The present invention, by efficiently display the preview screen corresponding to the screen information more generated program executed by the server, it is possible to provide a technique for improving the development efficiency of applications.

It is a figure which shows the basic functional structure of the information processing apparatus concerning embodiment of this invention, and the calling relationship of each function. It is a block diagram which shows an example of the hardware constitutions of the information processing apparatus concerning embodiment of this invention. It is an example of the screen configuration which defines a GUI layout among the program automatic generation tools concerning the embodiment of the invention. It is an example of the screen configuration which defines an item among the program automatic generation tools concerning the embodiment of the present invention. It is a figure which shows an example of a data structure in the item list model memory | storage part which memorize | stores the information of the item list defined by the program automatic generation tool concerning embodiment of this invention. It is an example of a sequence diagram for synchronizing the definition of the GUI layout concerning the embodiment of the present invention with the definition of the item list. It is an example of the sequence diagram for synchronizing the definition of the item list concerning embodiment of this invention with the definition of GUI layout. It is an example of the figure showing the functional composition about the preview of the information processor concerning the embodiment of the present invention, and the calling relation of each function. It is an example of the figure showing the preview state of the preview HTML according to the embodiment of the present invention. It is an example of the figure showing the user screen which designates the file storage place (folder) of preview HTML concerning the embodiment of the present invention. It is an example of the figure showing the data composition of the result of having acquired the definition information required in order to generate preview HTML concerning an embodiment of the present invention from an application definition. It is an example of a flow chart which shows generation processing of preview HTML concerning an embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, a GUI layout as a premise of HTML preview generation will be described with reference to FIGS. 1 to 7.

  FIG. 1 is a diagram showing a functional configuration of an information processing apparatus 100 according to an embodiment of the present invention, and a calling relationship of each function. In FIG. 1, a user operation (101) is performed from a definition screen (a screen for defining a program in an automatic program generation tool) in a GUI (graphical user interface). Specifically, the GUI layout or the item list is defined in the GUI layout tab (FIG. 3) or the item list tab (FIG. 4) of the program automatic generation software operating in the information processing apparatus 100. FIG. 5 is a diagram of software components associated with processing upon inter-switching and requirements between components. The information defined in the GUI layout tab and the item list tab uniquely determines the definition file name of the definition screen header (“USERREQ.wprx” in the example of the screen in FIGS. 3 and 4) or the screen. Identified by information.

  When the item list tab selection request 121 is notified to the input / output definition editor controller unit 102 by the user operation (101), the input / output definition editor controller unit 102 transmits the layout model conversion request 122 to the item list model conversion unit 103. Notice.

  Since the item list model conversion unit 103 converts the GUI layout definition into the item list definition, the current GUI layout definition (a layout definition defined in the GUI layout tab and a list of definitions of layout component information) is stored in the layout model storage unit. It acquires from 107 (layout model conversion acquisition request 123). Furthermore, the item list model conversion unit 103 converts the acquired current GUI layout into an item list definition (a list of definitions of item information), and registers the conversion result in the item list model storage unit 104 (if there is any). Update item list model update request 124).

  After registering or updating the item list definition, the input / output definition editor controller unit 102 acquires the registration or update result (item list model display acquisition request 125). The input / output definition editor controller unit 102 requests the item list display unit 105 to display the acquired item list definition on the item list tab, and the item list display unit 105 displays the item list definition according to the request.

  When the layout tab selection request 141 is notified to the input / output definition editor controller unit 102 by the user operation (101), the input / output definition editor controller unit 102 transmits the item list model conversion request 142 to the GUI layout model conversion unit 106. Notice.

  The GUI layout model conversion unit 106 acquires the current item list definition from the item list model storage unit 104 in order to convert the item list definition into the GUI layout model definition (item list model conversion acquisition request 143). Furthermore, the GUI layout model conversion unit 106 converts the acquired current item list definition into a GUI layout definition, and registers it in the layout model storage unit 107 (updates, if it already exists, layout model update request 144).

  After registering or updating the GUI layout definition, the input / output definition editor controller unit 102 acquires the registration or update result (layout model display acquisition request 145). The input / output definition editor controller unit 102 requests the GUI layout controller unit 108 to generate a GUI layout component in preparation for drawing the acquired GUI layout definition on the GUI layout tab (a GUI layout generation request 146).

  The GUI layout controller unit 108 that has received the GUI layout generation request generates a GUI component or the like for drawing based on the GUI layout definition acquired from the layout model storage unit 107. First, a component (base component) to be a base for arranging a GUI component (text input box, button, etc.) on the GUI layout is generated and added to the GUI layout storage unit 109 (GUI layout & component storage unit) GUI layout addition request 147).

  The GUI layout controller unit 108 further issues a GUI component generation request 148 to the GUI component controller unit 110 for each GUI component immediately below the base component in order to generate a GUI component to be arranged in the base component.

  The GUI component controller unit 110 generates the GUI component requested by the GUI component generation request 148 based on the definition of each component of the GUI layout definition (definition converted from item information). If a GUI part defines a nested GUI part (not a part placed immediately below the base part but a child GUI part placed on the GUI part) in the GUI layout definition, the nested part To make a request to the GUI component controller unit 110 recursively (GUI component generation request 149). The generated GUI component is added to the GUI layout storage unit 109 (GUI component addition request 150).

  When the generation of the GUI component (including the base component) is completed, the GUI layout controller unit 108 issues a GUI layout drawing request 151 to the GUI layout drawing unit 111. In response to this request, the GUI layout drawing unit 111 displays the GUI layout on the GUI layout tab.

  FIG. 2 is a block diagram showing an example of a hardware configuration of the information processing apparatus 100 (automatic program generation apparatus) according to the embodiment of the present invention.

  As shown in FIG. 2, the information processing apparatus 100 includes a central processing unit (CPU) 201, a random access memory (RAM) 202, a read only memory (ROM) 203, an input controller 205, and a video controller 206 via a system bus 204. A memory controller 207, a communication I / F controller 208, and the like are connected. The CPU 201 centrally controls the devices and controllers connected to the system bus 204.

  Further, the ROM 203 or the external memory 211 may include a BIOS (Basic Input / Output System) as a control program of the CPU 201, an OS (Operating System), and a function necessary for realizing each server or each PC. Various programs are stored. Also, information necessary for practicing the present invention is stored. The external memory may be a database.

  The RAM 202 functions as a main memory, a work area, and the like of the CPU 201. The CPU 201 loads programs necessary for execution of processing from the ROM 203 or the external memory 211 to the RAM 202 and executes the loaded programs to realize various operations.

  The input controller 205 also controls input from a keyboard (KB) 209 and a pointing device such as a mouse (not shown).

  The video controller 206 controls display on a display such as the display 210. The display may be a display such as a liquid crystal display. These are used by the administrator as needed.

  The memory controller 207 is an external storage device (hard disk (HD)) for storing a boot program, various applications, font data, user files, editing files, various data, etc., a flexible disk (FD), or PCMCIA (Personal Computer). Memory Card International Association) Control access to an external memory 211 such as a Compact Flash (registered trademark) memory connected via an adapter to a card slot.

  The communication I / F controller 208 connects to and communicates with external devices via a network, and executes communication control processing in the network. For example, communication using TCP / IP (Transmission Control Protocol / Internet Protocol) is possible.

  The CPU 201 can display the image on the display 210 by executing, for example, an outline font rasterization process on a display information area in the RAM 202. Further, the CPU 201 enables user instruction by a mouse cursor (not shown) or the like on the display 210.

  Various programs to be described later for realizing the present invention are stored in the external memory 211, and are executed by the CPU 201 by being loaded into the RAM 202 as necessary. Furthermore, definition files and various information tables used at the time of execution of the above-mentioned program are also stored in the external memory 211, and a detailed description of these will be described later.

  FIG. 3 is an example of a screen configuration for defining a GUI layout in the program automatic generation tool according to the embodiment of the present invention. The GUI layout definition screen mainly includes the following areas. That is, a definition explorer area 301 in which data is stored as a folder hierarchy for each defined unit, a canvas area 302 for visually arranging and operating one GUI layout definition, and a GUI component (for example, text) arranged in the canvas area 302 It consists of a palette area 303 for selecting field 304).

  Also, in order for the developer to describe various definition information, tabs that are displayed in common on the definition screen of the program automatic generation tool are arranged. For example, the item list tab 305 and the layout tab 306 are displayed also on the item list definition screen of FIG. In the embodiment of the present invention, the GUI layout definition screen (FIG. 3) and the item list definition screen (FIG. 4) are switched and operated.

  Also, in the embodiment of the present invention, it is possible to arrange the data model 308 in the definition explorer area 301 in the canvas area 302 in the same manner as the GUI part of the palette area 303. That is, one or more data items (columns) described in the database table are selected from the data model 308 and arranged in the canvas area 302. Then, the information (column name, data type, size, etc.) of the data item (column) defined as the schema of the database is extracted, for example, if the data type is text or numeric, it is a text field or boolean In the case, it can be arranged as a check box or the like.

  The GUI layout definition screen 300 b shows a case where one text field 307 is added to the GUI layout definition screen 300 a and the name is set as “user ID”. The title, the size of the input area, etc. may be updated by clicking with the mouse in the canvas area 302, and when the GUI part is clicked, the lower left area of the GUI layout definition screen 300 (“Property It is also possible to display a list of information related to the GUI component as an attribute in “the definition area” and correct the attribute by keyboard input.

  FIG. 4 is an example of a screen configuration for defining an item list in the program automatic generation tool according to the embodiment of the present invention. In the item list definition screen, the claimed area is an item list setting area 401.

  The item list setting area 401 is in the form of a table, and the developer defines one information (e.g., text field in GUI layout, check box, button, text) and the like in one line with detailed attributes.

  The item list definition screen 400 b shows a case where one item type “input” is added to the item list definition screen 400 a and the name is set as “user ID” (definition in line 402). The definition of line 402 corresponds to the text field 307 of FIG.

  Here, the relationship between the definitions in FIG. 3 and FIG. 4 will be described. For example, when the item list tab 305 is selected while the GUI layout definition screen 300a of FIG. 3 is displayed, the display is switched to the item list definition screen 400a of FIG. It defines substantially the same information as the program being developed. In FIG. 4, after the row 402 is added as described above to make the item list definition screen 400b, when the layout tab 306 is selected, the text field 307 is added and drawn also on the layout as in the GUI layout definition screen 300b. .

  Conversely, after the text field 307 is added to the GUI layout definition screen 300a also on the layout to make the GUI layout definition screen 300b, if the item list tab 305 is selected, even on the item list as in the item list definition screen 400b. The definition of line 402 is added.

  That is, the GUI layout definition and the item list definition are synchronized using the operation of the tab (the item list tab 305 and the layout tab 306) as a trigger.

  Further, in the data configuration rows [i] storing item list definitions in FIG. 5 described later and the data configuration storing GUI layout definitions (not shown), the definition order of the respective definitions is described as rowIndex. Therefore, the definition of the item corresponding to the GUI component defined at the top in the GUI layout definition is displayed in the first line of the item list definition. As a result, the positional relationship of the definitions is also synchronized, and the relationship between the program logic and the GUI layout is not broken even if any of the definitions is changed.

  Thus, the description of FIGS. 3 and 4 is completed. In this manner, synchronization between development in the item list and development in the GUI layout (that is, definition of the item is also part definition) makes it possible to confirm the GUI layout at any timing during development, and also program logic and GUI layout Even if any of the above is edited, it is possible to improve the development efficiency by eliminating the need to correct the correspondence.

  FIG. 5 is a view showing an example of a data configuration in an item list model storage unit storing information of item lists defined by the program automatic generation tool according to the embodiment of the present invention. The described data describes five lines as an example among the lines defined in the item list setting area 401 of the item list definition screen 400 in FIG. 4. This information may be temporarily stored on the RAM 202 or may be stored in a database. Hereinafter, the image stored in the RAM 202 will be described.

  The item list definition is stored in rows [0] to rows [4]. rows [i] (each element) has an element called data as shown in FIG. 5, and a plurality of attribute values, such as “I” indicating an input column, “USERID” indicating an item ID, “user indicating an item name” ID "etc. are set.

  In addition, various attributes used for automatic program generation are defined. Also, in the "owPropertyList", the size "labelWidth" of the area for displaying the name, the area size "fieldWidth" of the text input field, etc. are specified.

  This is the end of the description of the data configuration in the item list model storage unit 104. Furthermore, although not shown, the GUI layout of FIG. 3 is also stored in the layout model storage unit 107. The data configuration of both is almost the same. In the embodiment of the present invention, since the information stored in the item list model storage unit 104 is the center, in the data configuration in the layout model storage unit 107, each element (layout component information) is a link to corresponding item information And the size of the area size in the item information (rows [i]) indicates the size when converted to HTML, but in the layout component compromise, when displaying in the canvas area 302 of the GUI layout definition screen 300 Some of the information is different, such as being converted to a suitable size. The data configuration of the item list model storage unit 104 and the layout model storage unit 107 is merely an example, and may be defined in the form of another configuration.

  FIG. 6 is an example of a sequence diagram for synchronizing the GUI layout definition with the item list definition according to the embodiment of the present invention. Each step of the sequence diagram of FIG. 6 is executed by the CPU 201 of the information processing apparatus 100.

  In S601, when the item list tab is selected by the user operation (101), a request for item list tab selection is issued from the program development tool, and the input / output definition editor controller unit 102 displays the definition screen as an item list tab (FIG. A request for switching to 4) is received (item list tab selection request 121).

  In S602, the input / output definition editor / controller unit 102 requests the item list model conversion unit 103 to convert the GUI layout definition into the item list definition (layout model conversion request 122). Here, to which definition the conversion is requested is specified by the information that uniquely determines the definition as described in FIG.

  In step S603, the item list model conversion unit 103 acquires the definition of the GUI layout from the layout model storage unit 107 (layout model conversion acquisition request 123).

  In step S604, the item list model conversion unit 103 converts the acquired GUI layout into an item list definition. As described above, in the GUI layout definition, since the size suitable for displaying in the canvas area 302 of the GUI layout definition screen 300 is held, these sizes are generated as HTML parts at the time of program automatic generation. Perform conversion processing such as conversion to an appropriate size.

  In step S605, the item list model conversion unit 103 converts the acquired current GUI layout into an item list definition (a list of item information definitions), and registers the conversion result in the item list model storage unit 104 (if there is already one) Item list model update request 124).

  In S606, the input / output definition editor controller unit 102 acquires the registered or updated item list definition from the item list model storage unit 104 (item list model display acquisition request 125).

  In S607, the input / output definition editor controller unit 102 requests the item list display unit 105 to display the acquired item list definition on the item list tab, and the item list display unit 105 displays the item list definition according to the request.

  FIG. 7 is an example of a sequence diagram for synchronizing the item list definition with the GUI layout definition according to the embodiment of the present invention. Each step of the sequence diagram of FIG. 6 is executed by the CPU 201 of the information processing apparatus 100.

  In S701, when the layout tab is selected by the user operation (101), a request for layout tab selection is issued from the program development tool, and the input / output definition editor controller unit 102 displays the definition screen in the layout definition tab (FIG. 3). Receives a request to switch to (layout tab selection request 141).

  In S702, the input / output definition editor controller unit 102 notifies the GUI layout model conversion unit 106 of the item list model conversion request 142 (item list model conversion request 142). Here, to which definition the conversion is requested is specified by the information that uniquely determines the definition as described in FIG.

  In S703, in order to convert the item list definition into a GUI layout model definition, the GUI layout model conversion unit 106 acquires the current item list definition from the item list model storage unit 104 (item list model conversion acquisition request 143).

  In S704, the GUI layout model conversion unit 106 converts the acquired current item list definition into a GUI layout definition.

  In step S705, the GUI layout model conversion unit 106 registers the converted GUI layout definition in the layout model storage unit 107 (updates the layout model if it already exists. Layout model update request 144).

  In S706, the input / output definition editor controller unit 102 acquires the registration or update result after registration or update of the GUI layout definition (layout model display acquisition request 145).

  In step S707, the input / output definition editor controller unit 102 requests the GUI layout controller unit 108 to generate a GUI layout component as a preparation for drawing the acquired GUI layout definition on the GUI layout tab (a GUI layout generation request 146).

  In step S 708, the GUI layout controller unit 108 that has received the GUI layout generation request generates a GUI component or the like for drawing based on the GUI layout definition acquired from the layout model storage unit 107. First, a component (base component) to be a base for arranging a GUI component (text input box, button, etc.) on the GUI layout is generated and added to the GUI layout storage unit 109 (GUI layout & component storage unit) GUI layout addition request 147).

  In step S709, the GUI layout controller unit 108 issues a GUI component generation request 148 to the GUI component controller unit 110 for each GUI component immediately below the base component in order to generate a GUI component to be arranged in the base component.

  In step S710, the GUI component controller unit 110 generates the GUI component requested by the GUI component generation request 148 based on the definition (the definition converted from the item information) of each component of the GUI layout definition. If a GUI part defines a nested GUI part (not a part placed immediately below the base part but a child GUI part placed on the GUI part) in the GUI layout definition, the nested part To make a request to the GUI component controller unit 110 recursively (GUI component generation request 149). The generated GUI component is added to the GUI layout storage unit 109 (GUI component addition request 150).

  In step S711, when the generation of the GUI component (including the base component) is completed, the GUI layout controller unit 108 issues a GUI layout drawing request 151 to the GUI layout drawing unit 111. In response to this request, the GUI layout drawing unit 111 displays the GUI layout on the GUI layout tab.

  As described in the sequence diagrams of FIG. 6 and FIG. 7, data (item list definition and GUI layout definition) displayed on both items is re-generated, triggered by the user's operation of switching the item list tab and the layout tab. There is no need to manually associate the definition (program logic) with the GUI layout definition (screen information for generating HTML etc.) or to create correspondence information. This has the effect of improving the productivity of the work of program definition by the program automatic generation tool.

  Next, a detailed description of preview HTML generation will be given using FIGS. 8 to 12. Preview HTML is an HTML screen for generating and confirming, as a preview, HTML that is a view corresponding to a business logic (controller) and a database model in an application.

  FIG. 8 is an example of a diagram showing a functional configuration regarding a preview of the information processing apparatus according to the embodiment of the present invention and a calling relationship of each function. Also, in FIG. 8, only the outline of each functional unit and request will be described, and the details will be described with reference to the flowchart of FIG. 12.

  First, as described in FIG. 1, the user operation (101) is performed from a definition screen (a screen for defining a program in the program automatic generation tool) in a GUI (graphical user interface).

Specifically, the operation is performed on the GUI layout tab (FIG. 3) and the item list tab (FIG. 4) in the program automatic generation software operating in the information processing apparatus 100. With regard to preview HTML generation, at the timing when the user operates the preview tab 309 in FIG. 3 (preview tab selection 831), the event of the operation is notified to the input / output definition editor controller unit 102.

  The input / output definition editor controller unit 102 acquires item list information required for processing in the application definition storage unit (input / output model acquisition 832). Specifically, information necessary for generating the preview HTML is acquired from the item list model storage unit 104. It filters the displayed information. Here, the acquired item list information will be described with reference to FIG.

  FIG. 11 is an example of a diagram showing a data configuration as a result of acquiring definition information necessary for generating preview HTML according to the embodiment of the present invention from an application definition. The data structure is almost the same as "rows" described in FIG. First, as data that defines an application under development, there are many definitions such as business logic definitions, database model definitions, and other properties of applications. Even in the case of input / output definitions, there are currently input / output definitions for which preview HTML is to be generated, and other definitions.

  The input / output definition editor controller unit 102 first selects only the necessary definition body. Specifically, for example, it is a definition including data in which the item list definition of FIG. 4 is described. In addition, the word "definition body" is used for convenience here. In practice, one definition body may be stored in one file. Alternatively, definitions for one entire application may be stored in one file, and each (for example, one item list) definition may be distinguishable by a tag. In this case, it means the content of the tag. Also, during development, the file may not be stored in a file, and data may be expanded on the RAM 202 or may be stored in a database instead of a file. Therefore, the term definition body is used here as a term of convenience for distinguishing one item list information from other definition information.

  What has acquired one item list information is a definition body implemented by a data structure having the rows 500 in FIG. 5 or equivalent information. Furthermore, in the item list definition of FIG. 4, “small number” to “data model item code” and the like are unnecessary as information of the HTML screen. These are what define linkage with a database. Therefore, delete unnecessary columns. In the case of the rows 500 in FIG. 5, for example, “−1” to “@ TEXT” and the like in the second row become unnecessary, so they are deleted. As a result of these processes, filtered Rows 1100 in FIG. 11 are obtained.

  Here, even if business logic related to screen information (view), database model, etc. are not completed, it is possible to generate preview HTML, so it is possible to check the screen at flexible timings and improve efficiency. It is possible to obtain the effect of promoting In addition, by using the information necessary for generating the preview HTML, it is possible to confirm the screen image without building the entire application, and it is possible to obtain an efficient build time.

  After acquiring the item list information, the input / output definition editor controller unit 102 sends a preview HTML generation request 833 to the preview controller unit 811.

  The word “preview template” is described briefly as “preview template”, which is a simple language that can perform mapping from item list information to a hierarchical structure of HTML tags, and is stored in the preview HTML generation unit 814 There is. The preview template parameter generation unit 812 generates preview template parameters to be passed to the preview HTML generation unit 814.

  The input / output definition editor controller 102 first generates a full path name to be stored after generating the preview HTML file. The file name is previously defined by the user in the preview HTML name storage unit 821 and acquired by preview HTML name acquisition 834.

  FIG. 10 is an example of a diagram showing a user screen for specifying a file storage location (folder) of preview HTML according to the embodiment of the present invention. Display this dialog and let the user input the folder name for storing the HTML file. The full path name of the file is determined together with the acquired file name.

Furthermore, in order to obtain information for generating the preview HTML and to generate a data configuration, a preview template parameter generation request 835 is issued to the preview template parameter generation unit 812.

  The preview template parameter generation unit 812 acquires, from the preview property storage unit 822, a preview property which is information necessary for generating preview HTML (preview property acquisition 836. Details of the property will be described later). Further, style information is acquired from the style information storage unit 823 (style information acquisition 837. Style information is information such as an HTML style sheet, and the details will be described later).

  FIG. 9 is an example of a diagram showing a preview state of preview HTML according to the embodiment of the present invention. In the preview HTML tab 900b, a property code is set to 902, each property of 903 is read according to the property code, and a preview HTML is generated. In the preview HTML tab 900a, default property code (not shown) is set. The items designated by the property 903 of the preview HTML tab 900b include, for example, "role" and (extended directory /) "language" ("display data directory" is further described in the example of Fig. 9).

  For example, "role" is a property indicating the role (post or job type) in an organization. In the application, even the screen that is originally the same, sometimes controls the items displayed by the post. Therefore, also in the generation of the preview HTML, by setting the role property, the item to be displayed is controlled according to the setting, that is, the preview HTML of the screen different depending on the role even from the same item list definition It has the effect of making it possible to generate

  There is also (Extension directory /) "Language". As for the language property, when the program automatic generation tool corresponds to a plurality of languages such as English / Japanese, it is designated which language the preview HTML screen is to be generated.

  Further, the style information acquisition unit 837 acquires a style sheet used in the preview HTML from the style information storage unit 823. The style sheet may have a portion that can be flexibly changed by the user (developer) and a fixed portion in the application (or a project for managing application development). For example, definitions such as character size, font, background color, line thickness, etc.

  As described above, information of an object (input / output field, button, etc.) for generating HTML is stored as a hierarchical data configuration reflecting the hierarchical structure of HTML or a data configuration replaceable with the hierarchical data configuration. ing. Although the explanation will be continued on the premise of the former "Hierarchical data configuration reflecting the hierarchical structure of HTML" for the sake of convenience, it has equivalent information which can be finally converted to HTML in any format. Any data configuration is acceptable. Further, although the data structure includes the arrangement and names of objects (for example, arrangement of text boxes and titles such as "user name") as information, actual values (for example, user name is "Suzuki" etc.) In the following description, for convenience, the term "preview template" will be referred to as the "preview template" (the same as the "template" described above) because the value is not included. However, in the "preview template", information indicating where to substitute a value (in the example, "Suzuki Ichiro" corresponding to the "user name" field) is included as a parameter (or variable) in the preview template It shall be.

  The item list defined for the HTML screen is stored in a format that can be converted to HTML as described above, and the actual conversion to HTML to be described later is a well-known technology in an automatic program generation tool etc. Is omitted.

  The preview template parameter generation unit 812 issues a preview data setting request 838 to the preview data setting unit 813 for substituting a sample value into the “preview template” described above. The preview data setting unit 813 acquires data from the substitution value data storage unit 824 (substitution value data acquisition 839), and creates a “preview template parameter”.

  These processing results are returned to the preview controller unit 811. The preview controller unit 811 requests the preview HTML generation unit 814 to generate preview HTML based on the "preview template parameter" (a template HTML conversion request 840). In response to the request, the 841 preview HTML generation unit maps the held preview template and preview template parameters, and generates preview HTML. Further, in response to the preview HTML display request 841, the preview HTML is displayed on the display device (the preview tab of the development tool) of the information processing apparatus 100 (the screen of FIG. 9).

  In the above description, it has been described that the “preview template parameter containing a value” is created by the substitution value data storage unit 824, but in the preview HTML tab 900a, a meaningless value such as “XXXX. Is displayed (901a). This depends on whether information for substitution is defined in the substitution value data storage unit 824.

  Specifically, even if a folder is not described in the "display data directory" of the property 903 or is described (in the example, "C: \ PreviewData"), no data is stored in the folder. The screen of the preview HTML tab 900a is displayed as a default. These default values may be hard-coded in the program or may be stored in a default value storage unit (not shown). Even if it is a default value, multiple types may be prepared according to, for example, the type of the input field (full-width characters, half-width alphanumeric characters, etc.). In this case, in each element of the item list definition body, if the definition of the input field is specified, it follows the type.

  On the other hand, if there is a value (for example, prepared as a CSV file or the like) for substitution in substitution value data storage unit 824, as in preview HTML tab 900b, a value that is easy for the user to understand (meaning for human) It is possible to display (901b).

  This completes the description of the functional configuration for generating the preview HTML in FIG. 8 and the calling relationship of each function. At the same time, the description of FIGS. 9 to 11 is also completed.

  FIG. 12 is an example of a flowchart showing generation processing of preview HTML according to the embodiment of the present invention. Each step of the flowchart of FIG. 12 is executed by the CPU 201 of the information processing apparatus 100. In addition, about the part described in description of a functional block diagram (FIG. 8), description of a specific detailed matter may be abbreviate | omitted.

  In S1201, the user operation (101) is received from a definition screen (a screen for defining a program in the program automatic generation tool) in a GUI (graphical user interface). Specifically, in the program automatic generation software operating in the information processing apparatus 100, an event in which the user selects the preview tab 309 is accepted.

In the repetition processing of S1202 to S1205, information related to the screen for the preview display request is acquired from all the definitions of the application definition information.
In S1203, it acquires from the application definition body storage unit.

  In step S1204, it is determined whether the definition body acquired in step S1203 is the definition body of the item list of the preview display request target, and if so, the process exits the repetitive processing (S1202 to S1205). Specifically, the definition body is obtained from the item list model storage unit 104, and further, the definition body of the item list definition currently being defined (under development) is obtained.

  Next, in the repeated processing of S1206 to S1209, elements are taken out one by one from the definition body of the item list acquired above (for example, rows 500 in FIG. 5), and the following processing is executed on all the elements.

  In S1207, the elements (row [i]) are extracted one by one from the definition body of the item list (for example, rows 500 in FIG. 5), and as described above, “few” to “data model items in the item list definition in FIG. Information necessary as an object of the HTML screen is extracted, such as "Item Type", "Item Code" to "Number of Digits" (see FIG. 4), except an unnecessary part as information of the HTML screen such as "Code".

  In S1208, the information extracted in S1207 is stored in filteredRows 1100 (element filteredRows [i]). Thus, in the preview HTML generation, it is a stage where business logic, database model, etc. are not completed by using only information necessary for preview HTML generation among the definition bodies defined by the program automatic generation tool. Even in this case, it is possible to generate preview HTML, and it is possible to confirm the screen at flexible timing and obtain an effect of promoting efficient development. In addition, by using the information necessary for generating the preview HTML, it is possible to confirm the screen image without building the entire application, and it is possible to obtain an efficient build time.

  In S1210, a preview template is generated, and the name of the generated preview HTML file is acquired and stored in the preview template. Here, the preview template is, as described above, the data configuration of the stage immediately before generating the HTML structure. That is, the preview template includes information that can generate actual HTML by performing mapping on the HTML tag hierarchical structure.

  In S1211, the preview property of the generated preview HTML file is acquired and stored in the preview template. Specifically, it has been described in 903 of FIG.

  In step S1212, the style information of the preview HTML is acquired. Specifically, it is style sheet information.

  The repetition process of S1213 to S1215 is performed on all elements of filteredRows 1100.

  In S1214, filtered Rows [i] (data obtained by extracting information necessary for display corresponding to one HMTL object from one element of the item list definition) is embedded in the preview template. However, the process of S1214 is executed only for filteredRows [i] which is determined to be displayed by the "role" property. As a result, a data structure substantially equivalent to preview HTML is created. At this stage, there is no value in the user data displayed on the field part.

  In S1216, specific values are entered into the field component. A specific value is acquired from the substitution value data storage unit 824. In the substitution value data storage unit 824, a value to be inserted into the input field is defined in association with, for example, the item name (or item ID) of the field, for example, by a file in the CSV format. This value is replaced with the variable in the preview template described above.

  In S1217, the list item name, type, and substitution value are converted into an HTML object, and embedded in the preview HTML file.

In S1218, the generated preview HTML file is displayed on the display device (the preview tab of the development tool) of the information processing apparatus 100 (screen of FIG. 9).
This is the end of the description of the flowchart in FIG.

  The configuration of the various data described above and the contents thereof are not limited to this, and it is needless to say that they are configured in various configurations and contents depending on the application and purpose.

  As mentioned above, although one Embodiment was shown, this invention can take the embodiment as a system, an apparatus, a method, a program, a recording medium etc., for example, and, specifically, it is comprised from a some apparatus The present invention may be applied to a single system or to an apparatus comprising a single device.

  The program according to the present invention is a sequence diagram shown in FIGS. 6 and 7 and a program capable of executing the processing method of the flowchart in FIG. 12 by a computer. The storage medium according to the present invention is the sequence diagram shown in FIGS. A program capable of executing computer processing of the processing method of the flowchart of FIG. 12 is stored. Note that the program in the present invention may be a program for each processing method of each device in the sequence diagram shown in the flowcharts of FIG. 6, FIG. 7, and FIG.

  As described above, the recording medium recording the program for realizing the functions of the above-described embodiments is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can be achieved also by reading and executing.

  In this case, the program itself read out from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying a computer program, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a DVD-ROM, a magnetic tape, a non-volatile memory card, a ROM, an EEPROM, Silicon disks, solid state drives, etc. can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiment are realized, but also an operating system (OS) or the like running on the computer is actually executed based on the instructions of the program. It goes without saying that the processing is partially or entirely performed, and the processing realizes the functions of the above-described embodiments.

  Furthermore, after the program read from the recording medium is written to the memory provided to the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is read based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiment are realized by the processing.

Further, the present invention may be applied to a system constituted by a plurality of devices or to an apparatus comprising a single device. It goes without saying that the present invention can also be applied to the case where it is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can receive the effects of the present invention. Further, by downloading and reading out a program for achieving the present invention from a server on a network, a database or the like by a communication program, the system or apparatus can receive the effects of the present invention.
In addition, the structure which combined each embodiment mentioned above and its modification is also contained in this invention altogether.

100 information processing apparatus 102 input definition editor controller unit 103 item list model conversion unit 104 item list model storage unit 105 item list display unit 106 GUI layout model conversion unit 107 layout model storage unit 108 GUI layout controller unit 109 GUI layout storage unit 110 GUI Controller unit 111 GUI layout drawing unit 811 preview controller unit 812 template generation unit 813 preview data setting unit 814 preview HTML generation unit 815 preview HTML display unit 821 preview HTML name storage unit 822 preview property storage unit 823 preview style information storage unit 824 substitution value Data storage unit

Claims (9)

An information processor,
A definition information for generating an executable program in the server, and defines storage means for storing definition information according to the screen item included in the screen information generated by the previous SL program is executed,
A program generation means for using the definition information stored, to generate a program for generating a pre-Symbol screen information by the definition storage means,
A display definition information extracting means for extracting a definition information related to the display of the screen item of definition information stored in the pre-Symbol definition storage means,
Preview screen generation means for generating a preview screen corresponding to screen information generated by execution of the program using definition information relating to display of the screen item extracted by the display definition information extraction means ;
A program for functioning as preview screen display means for displaying a preview screen generated by the preview screen generation means. The display definition information extraction means extracts a data type of definition information stored by the definition storage means,
The program according to claim 1, wherein the preview screen generation unit arranges objects based on the data type extracted by the display definition information extraction unit . The definition information stored by the definition storage means can be changed according to the input from the user,
The preview screen display means is
The program according to claim 1 or 2, wherein the preview screen is displayed using definition information changed according to an input from the user. It further functions as a value storage unit that stores values set for screen items included in the preview screen,
The preview screen display means is
The program according to any one of claims 1 to 3, wherein the preview screen including the screen item in which the value stored by the value storage means is set is displayed. The preview screen display means is
For the screen item for setting the value stored in the value storage unit based on the value stored in the value storage unit, the value corresponding to the screen item stored in the value storage unit is For screen items which are set and not set values stored in the value storage means, default values corresponding to the screen items are set, and a preview screen is displayed. The program described in. Further function as style sheet storage means for storing style sheets applied to the screen information;
The preview screen generation unit
The program according to any one of claims 1 to 5, wherein a preview screen is generated using a style sheet stored by the style sheet storage means. To further function as a preview screen controller <br/> that controls items to be displayed according to at least one of the roll or the display language of the end user viewing the preview screen displayed by the preview screen displaying means,
The value storage means stores at least one of an end user's role and a display language.
The preview screen generation unit
It is characterized in that a preview screen in which display of an item is controlled according to the preview screen control means is generated using at least one of the end user's role or display language stored by the value storage means. The program according to any one of claims 4 to 6. The information processing apparatus
A definition information for generating an executable program in the server, and definition storage step of storing the definition information relating to screen item included in the screen information generated by the previous SL program is executed,
A program generation step of generating a program for using the definition information stored by said definition storing step, to produce a pre-Symbol screen information,
A display definition information extracting step of extracting a definition information related to the display of the screen item of definition information stored in the pre-Symbol definition storing step,
A preview screen generation step of generating a preview screen corresponding to screen information generated by execution of the program using definition information relating to display of the screen item extracted by the display definition information extraction step ;
And a preview screen display step of displaying the preview screen generated by the preview screen generation step. A definition information for generating an executable program in the server, and defines storage means for storing definition information according to the screen item included in the screen information generated by the previous SL program is executed,
A program generation means for using the definition information stored, to generate a program for generating a pre-Symbol screen information by the definition storage means,
A display definition information extracting means for extracting a definition information related to the display of the screen item of definition information stored in the pre-Symbol definition storage means,
Preview screen generation means for generating a preview screen corresponding to screen information generated by execution of the program using definition information relating to display of the screen item extracted by the display definition information extraction means ;
An information processing apparatus comprising: preview screen display means for displaying the preview screen generated by the preview screen generation means.

Images