CN114741079B

CN114741079B - Software development method, platform, electronic device and computer readable storage medium

Info

Publication number: CN114741079B
Application number: CN202210395807.4A
Authority: CN
Inventors: 彭威; 张栋; 何林峰; 李永琪; 周玉娟
Original assignee: Shanghai Jining Computer Technology Co ltd
Current assignee: Shanghai Jining Computer Technology Co ltd
Priority date: 2022-04-14
Filing date: 2022-04-14
Publication date: 2023-07-21
Anticipated expiration: 2042-04-14
Also published as: CN114741079A; CN117149191A

Abstract

The invention discloses a software development method, a platform, electronic equipment and a computer readable storage medium. The method is applied to a visual software development platform and comprises the following steps: acquiring configuration information of a page to be displayed configured by utilizing a visual interface, wherein the information of a form comprises a form type and a design page, the form is associated with a data query statement, and the data query statement is associated with a service form; rendering and displaying a page to be displayed according to the configuration information; when the form type is a list page, inquiring at least one group of data groups needed by a page to be displayed in a business table according to a data inquiry statement, and creating an interface associated with each data group in the page to be displayed; and rendering the data sets associated with each interface according to the design page, and displaying at least one design page in the rendered pages to be displayed. The method and the device can realize the automatic rendering of multiple groups of data to be displayed of the page to be displayed, simplify the configuration flow, and remarkably improve the development efficiency when the data volume to be displayed of the page is large.

Description

Software development method, platform, electronic device and computer readable storage medium

Technical Field

Embodiments of the present invention relate to the field of computer technologies, and in particular, to a software development method, a platform, an electronic device, and a computer readable storage medium.

Background

In the traditional way of software development, the implementation exposes sets of data in pages of software (see the list page shown in fig. 1), typically relying on a technician to manually write a large number of repeated codes. However, in recent years, the development of computer technology has been advanced, and higher requirements are also put on the convenience of software development, and the above software development manner cannot meet the requirements of people on the software development efficiency. In such a background, many software development platforms having advantages of visualization, low code, and the like are being created. The visual low-code software development platforms remarkably improve the convenience of software development.

However, these traditional visual low-code software development platforms have the development feature of "what you see is what you get". For each set of data to be displayed in the page as shown in fig. 1, a software developer is required to manually drag the controls into the display page one by using a software development platform for each set of data and even each data item in each set of data. Under the condition that the data volume required to be displayed by the page is large, software developers need to drag the control into the page by utilizing the development platform hundreds or thousands of times, and the software development efficiency is still low. In addition, if the number of data groups to be displayed on the page changes, the number of controls corresponding to the number of data groups also changes, so that a software developer is required to utilize a development platform to carry out real-time adjustment and maintenance, and the page developed by the development mode is difficult to self-adaptively and dynamically display the changed data. Therefore, in the case that the data volume to be displayed on the page of the software may be continuously updated, a software development mode of manually writing the code by a software developer is generally relied on.

Therefore, under the condition that the data volume to be displayed on the software page is large, the traditional software development mode still has the defects of insufficient development convenience, low development efficiency and the like, and the problems need to be solved.

Disclosure of Invention

The embodiment of the invention aims to provide a software development method, a platform, electronic equipment and a computer readable storage medium, which are used for simplifying configuration flow and improving software development efficiency under the condition that the data volume required to be displayed on a software page is large.

In order to achieve the above object, an embodiment of the present invention provides a software development method, applied to a visual software development platform, including: acquiring configuration information of a page to be displayed configured by utilizing a visual interface, wherein the configuration information comprises information of a service table, information of a form and a data query statement; the information of the form comprises a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a service table; rendering and displaying a page to be displayed according to the configuration information;

under the condition that the form type of the page to be displayed is a list page, rendering and displaying the page to be displayed according to the configuration information comprises the following steps: inquiring at least one group of data groups required by a page to be displayed in a service table according to the data inquiry statement, and establishing an interface corresponding to the data groups in the page to be displayed for each data group; for each interface, rendering and displaying the data set associated with the interface according to the design page, and completing rendering and displaying the page to be displayed; at least one design page is displayed in the pages to be displayed after rendering and displaying are completed.

In order to achieve the above object, an embodiment of the present invention further provides a visual software development platform, including:

the configuration module is used for acquiring configuration information of the page to be displayed configured by utilizing the visual interface, wherein the configuration information comprises information of a service table, information of the table and a data query statement; the information of the form comprises a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a service table; the rendering display module is used for rendering and displaying the page to be displayed according to the configuration information;

wherein, in the case that the form type of the page to be displayed is a list page, the rendering display module is configured to: inquiring at least one group of data groups required by a page to be displayed in a service table according to the data inquiry statement, and establishing an interface corresponding to the data groups in the page to be displayed for each data group; for each interface, rendering and displaying the data set associated with the interface according to the design page, and completing rendering and displaying the page to be displayed; at least one design page is displayed in the pages to be displayed after rendering and displaying are completed.

To achieve the above object, an embodiment of the present invention further provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software development method described above.

To achieve the above object, an embodiment of the present invention also provides a computer-readable storage medium storing a computer program, and the computer program when executed by a processor implements the above software development method.

In the process of displaying the page to be displayed, the visual software development platform provided by the embodiment of the invention firstly acquires the configuration information of the page to be displayed, which is configured by utilizing the visual interface. The configuration information comprises information of a service table, information of the table and a data query statement; wherein the information for the form includes a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a business table. According to the embodiment of the invention, the association relation is configured, so that the relation between each form and the business table in the software is established, the data required by the page can be conveniently acquired when the page to be displayed is rendered and displayed by the software, the data access quantity can be saved, and the data access speed can be improved.

And rendering and displaying the page to be displayed according to the configuration information. And for the list page with more data to be displayed, inquiring at least one group of data groups required by the page to be displayed in the service table through a data inquiry statement, and establishing interfaces associated with the data groups in the page to be displayed according to each data group. When the interfaces are created in the page to be displayed, the data groups required in the page to be displayed are obtained according to the data query statement and the service table, and then the interfaces are created according to the data groups, namely the creation of the interfaces depends on the number of the data groups, so that the number of the interfaces is always consistent with the number of the data groups, and when the data changes, the interfaces in the page to be displayed also change dynamically in a self-adaptive manner along with the change of the number of the data groups, so that the correct rendering display of the page to be displayed along with the change of the data is achieved on the basis that manual adjustment and maintenance are not needed.

Further, rendering and displaying the data sets associated with the interfaces according to the design pages aiming at each interface, and completing rendering and displaying the pages to be displayed. And rendering and displaying the interfaces according to the design pages for each interface, so that at least one design page is displayed in the pages to be displayed. According to the method and the device, each interface related in the page to be displayed is obtained according to the design page, namely, the display of each interface depends on the same design page, so that when the design page in the information of the form is configured, each interface can be rendered and displayed according to the design page only by configuring the design page once, namely, the display of the whole page to be displayed containing at least one group of data groups can be realized by simply configuring the control corresponding to the data groups, the workload of developers is obviously reduced, and the development efficiency is improved.

The process can realize the automatic rendering and displaying of multiple groups of data to be rendered, and the displaying of each interface in the page to be displayed can be completed by only carrying out a small amount of configuration in advance. Compared with the rendering mode of manually repeating dragging controls for multiple groups of data in the traditional visual software development scheme, or the rendering mode of writing codes for multiple groups of data to be rendered by technicians, the method can effectively reduce the software development difficulty, and especially can greatly improve the development efficiency under the condition of large data quantity to be displayed.

In addition, each data set comprises at least one data item; the design page comprises information of components required to be displayed in the form and a mapping relation between the components and the data items; rendering and displaying the data set associated with the interface according to the design page, wherein the rendering and displaying comprises the following steps: and filling each data item into the corresponding component of each data item according to the information of the component and the mapping relation between the component and the data item. According to the embodiment of the invention, the visual interface is utilized in advance to configure the design page for the page to be displayed, the mapping relation between each component in the design page and each data item in the data group is established, each data to be displayed on the interface is correctly filled into the corresponding component in the interface according to the preset mapping relation, and the rendering display of the interface is completed, so that the rendering display of each group of data in the list page is conveniently realized.

In addition, the page to be displayed is a page of the functional module; the visual interface comprises a module setting interface, a view setting interface and a form setting interface; the method for acquiring the configuration information of the page to be displayed configured by utilizing the visual interface comprises the following steps: obtaining module information of a function module configured by using a module setting interface, wherein the module information comprises: a service table associated with the functional module; acquiring a data query statement configured by using a view setting interface; and acquiring the form types and the design pages configured by using the form setting interface. In an embodiment of the invention, the page to be displayed is a page of a functional module, and the visual software development platform provides a plurality of visual interfaces, so that configuration information of the functional module can be conveniently configured by utilizing the visual interfaces, and further configuration information of the page to be displayed is configured.

In addition, the module information also includes an interface name; the information of the form also comprises a uniform resource locator URL automatically generated according to the interface name and the form type; rendering and displaying the page to be displayed according to the configuration information, including: and determining a rendering strategy according to the URL, and rendering and displaying the page to be displayed according to the configuration information based on the rendering strategy. In the embodiment provided by the invention, the URL for indicating the rendering strategy is automatically generated according to the form type, and the rendering strategy is generated according to the form type of the form, so that the rendering and displaying steps can be pertinently performed on each form by using different rendering strategies, and further the rendering and displaying results can meet the displaying needs of different form types.

In addition, the form setting interface includes: adding a new interface and a design interface; the method for acquiring the form types and the design pages configured by using the form setting interface comprises the following steps: acquiring a form type of a form configured by using the newly added interface; under the condition that the form type of the form is a list page, acquiring a data query statement which utilizes a newly added interface as the form association; the design interface includes a component area providing components and a design area for designing a form; wherein, in the case that the form types of the configured forms are different, formats of the components of the component areas are different; in the case where the form type of the form is a list page, the components of the component area include a field component for displaying each data item in the data group; and generating a design page according to the selected components in the component area and the arrangement mode of the selected components in the design interface. In one embodiment of the invention, the data query statement is associated with the form, so that the optional components in the component area can determine the fields for the data query statement, and the corresponding relation between the optional components and the fields can be established. When the subsequent rendering and displaying steps are carried out, the rendering and displaying of the components can be directly carried out according to the selected components by utilizing the corresponding field information. The rendering display format of the components is not needed to be considered in the form design process, so that the complexity of rendering the page to be displayed can be effectively reduced.

In addition, the components displayed in the page can be conveniently selected by utilizing the component area of the form setting interface, and the design of the form is conveniently carried out through the design area. The software development platform can further automatically generate a design page according to the selected components and the arrangement modes of the components, so that the difficulty of form design is reduced, and the convenience of form design is improved.

In addition, the visual interface also comprises a field setting interface; the field setting interface is used for managing field information in the service table; the field information includes a field type and a field source; the rendering display format of the field in the page to be displayed is determined according to the field type; the data set is obtained from the database based on the source of the field. The information of each field which can be displayed can be configured by using the field setting interface provided by the visual software development platform, so that the service table can be managed conveniently. In addition, the rendering display format of the field in the page to be displayed can be conveniently configured by setting the field type of the field in the field configuration process. And furthermore, under the condition that the field is involved in the subsequent configuration process, the rendering display format of the field does not need to be considered, and the complexity of rendering the page to be displayed can be effectively reduced.

In addition, the view setting interface includes: a view condition setting box for rights setting and a selection area providing a presentation field for selection; wherein the selection area includes: a first area for displaying candidate fields and a second area for displaying selected presentation fields; the candidate field is determined according to the service table; acquiring a data query statement configured by using a view setting interface, including: and acquiring screening conditions determined by the view condition setting frame and the selection area, and generating a data query statement according to the screening conditions. The view setting interface provided by the software development platform can be used for conveniently configuring the data query statement.

In addition, the visual interface also comprises a button setting interface; the button setting interface is used for configuring information of buttons required by the page to be displayed; the information of the button includes a button type and a button function; the rendering display format of the button in the page to be displayed is determined according to the type of the button; the button functions are determined from the form or data set bound for the button. The button information can be conveniently configured by utilizing the button setting interface provided by the visual software development platform. The rendering display format of the buttons in the page to be displayed can be conveniently configured by setting the button type of the buttons. And further, under the condition that the button is involved in the subsequent configuration process, the rendering display format of the button does not need to be considered, and the complexity of rendering the page to be displayed can be effectively reduced. In addition, the button functions of the buttons can be determined by binding the button with a form or a data group, so that the buttons can realize functions such as popup or skip among pages in software.

In addition, the module configuration interface includes: a field control, a button control, a view control, and a form control; the software development method further comprises the following steps:

in the event that the field control is detected to be operated, providing a field list page comprising: a field adding control and a field list set through a field setting interface; the field adding control triggers the provision of a field setting interface when operated, and a default field of the service table is displayed when the field list page is displayed for the first time;

in the event that the button control is detected to be operated, providing a button list page including: a button adding control and a button list set through a button setting interface; the button adding control triggers the provision of a button setting interface when operated, and a button list set through the button setting interface is empty when the button list page is displayed for the first time;

in the event that operation of the view control is detected, providing a view list page comprising: a view adding control and a view list generated through a view setting interface; the view adding control triggers the provision of a view setting interface when operated, and a view list generated through the view setting interface is empty when a view list page is displayed for the first time;

In the event that a form control is detected to be operated, providing a form list page comprising: form adding controls and form lists generated through a form setting interface; the form adding control triggers the provision of a form setting interface when operated, and a form list generated through the form setting interface is empty when a form list page is displayed for the first time. The field control, the button control, the view control and the form control are provided on the module configuration interface, so that information such as fields preconfigured on interfaces such as a field setting interface can be conveniently configured for the module in the process of configuring the module by utilizing the module configuration interface. The method simplifies the software development steps, improves the use experience of the software development platform, and effectively reduces the difficulty of software development.

Drawings

One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures do not depict a proportional limitation unless expressly stated otherwise.

FIG. 1 is a page schematic of a list page;

FIG. 2 is a flow chart of a software development method according to an embodiment of the invention;

FIG. 3 is a flow diagram of configuration information acquisition in accordance with one embodiment of the present invention;

FIG. 4 is a schematic diagram of a view setup interface in accordance with an embodiment of the invention;

FIG. 5 is a schematic diagram of an add-on interface of a form setting interface in accordance with an embodiment of the invention;

FIG. 6 is a schematic diagram of a design interface of a form setting interface in accordance with an embodiment of the present invention;

FIG. 7 is a schematic diagram of a module configuration interface in accordance with an embodiment of the invention;

FIG. 8 is a schematic diagram of a software page in accordance with an embodiment of the invention;

fig. 9 is a schematic structural diagram of a visual software development platform according to an embodiment of the present invention.

Fig. 10 is a schematic structural view of an electronic device according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art will understand that in various embodiments of the present invention, numerous technical details have been set forth in order to provide a better understanding of the present application. However, the technical solutions claimed in the present application can be implemented without these technical details and with various changes and modifications based on the following embodiments. The following divisions of the embodiments are for convenience of description, and should not be construed as limiting the specific embodiments of the present invention, and the embodiments may be mutually combined and referred to without contradiction.

An embodiment of the invention relates to a software development method applied to a visual software development platform, and a specific flow is shown in fig. 2. It can be appreciated that the visualization software development platform in this embodiment may be specifically deployed in a PC-side device or a mobile-side device such as a notebook computer or a desktop computer, which is not limited herein.

In this embodiment, the visual software development platform obtains configuration information of a page to be displayed configured by using a visual interface, where the configuration information includes information of a service table, information of a form, and a data query statement; the information of the form comprises a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a service table; rendering and displaying a page to be displayed according to the configuration information; under the condition that the form type of the page to be displayed is a list page, rendering and displaying the page to be displayed according to the configuration information comprises the following steps: inquiring at least one group of data groups required by a page to be displayed in a service table according to the data inquiry statement, and establishing an interface corresponding to the data groups in the page to be displayed for each data group; for each interface, rendering and displaying the data set associated with the interface according to the design page, and completing rendering and displaying the page to be displayed; at least one design page is displayed in the pages to be displayed after rendering and displaying are completed.

The implementation details of the service restoration method in this embodiment are specifically described below, and the following is only for facilitating understanding of the implementation details of this embodiment, and is not necessary for implementing this embodiment. The specific flow is shown in fig. 2, and may include the following steps:

step 201, obtaining configuration information of a page to be displayed configured by utilizing a visual interface, wherein the configuration information comprises information of a service table, information of the table and a data query statement; wherein the information for the form includes a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a business table.

Specifically, the visual interface may include a plurality of visual configuration interfaces provided by the visual software development platform for configuring information such as service tables and forms for the pages to be displayed. The visual interface can be used for a user of the software development platform to conveniently configure the page to be displayed in the modes of input, dragging and the like through the visual interface.

In addition, the service table involved in this step may be specifically a data table in which data required for the page to be displayed is stored in the database. The data query statement involved in this step is used to query the business table for the data required by the page to be presented. It can be understood that the service table and the data query statement are configured for the page to be displayed, namely the data to be displayed is configured for the page to be displayed.

In addition, the data query statement is configured to be associated with the service table, so that when the step of querying the data required by the page to be displayed by using the data query statement is performed, the service table can be accurately positioned, and further the data required by the correct page to be displayed can be obtained. In one example, the data query statement may be embodied as an SQL statement.

In addition, the data which is only needed to be displayed for the page to be displayed and is obtained through the data query statement, but not all data in the database or the service table, can save the data access amount and improve the data access speed. Under the application scene that the running clients are more, the configuration mode can help to promote the use experience of the software.

The information of the form represents the display effect of the page to be displayed. The information for the form includes the form type and design page. The form types may be specifically classified into a list page (refer to fig. 1) for displaying a plurality of sets of data, a detail page, an edit page, and the like. The design page represents the display effect of each interface in the page to be displayed, and specifically can comprise information such as components to be displayed, arrangement modes of the components and the like.

In addition, in the step, the form is configured to be associated with the data query statement, so that when the subsequent step of rendering the page to be displayed according to the information of the form is performed, the data query statement corresponding to the page to be displayed can be accurately positioned according to the information of the form, and further, when the step of acquiring the data required by the page to be displayed is performed, the data required by the correct page to be displayed can be correspondingly acquired.

Step 202, rendering and displaying a page to be displayed according to configuration information; the method comprises the following steps of: inquiring at least one group of data groups required by a page to be displayed in a service table according to the data inquiry statement, and establishing an interface corresponding to the data groups in the page to be displayed for each data group; for each interface, rendering and displaying the data set associated with the interface according to the design page, and completing rendering and displaying the page to be displayed; at least one design page is displayed in the pages to be displayed after rendering and displaying are completed.

In this step, for a list page that needs to display more data, at least one group of data sets needed to obtain a page to be displayed is queried first. Because the data query statement is configured to be associated with the service table, in the step, when the step of acquiring the data required by the page to be displayed is performed, the service table can be accurately positioned through the data query statement, and the data required by the page to be displayed can be conveniently queried and acquired in the service table according to the data query statement.

In addition, an interface is created for each data set that results from the query. It will be appreciated that the number of interfaces created depends on the number of data sets. That is, the number of interfaces is made consistent with the number of groups of data groups at all times. Therefore, when the data change (the data group number changes), the interface in the page to be displayed can be dynamically changed along with the data group number change in a self-adaptive manner. Therefore, the correct rendering and displaying of the page to be displayed along with the change of the data can be completed on the basis of no need of manual adjustment and maintenance.

In order to better understand the to-be-displayed page of which the form type is a list page, please refer to fig. 1 for a rendering display result of the to-be-displayed page. It should be noted that fig. 1 shows the display effect of the to-be-displayed page with the form type being a list page at the mobile terminal. Where "XXX", "YYY" and "ZZZ" are a set of data sets obtained from the query referred to in this step. It will be appreciated that "XXXX", "YYYY" and "ZZZZZ" are another set of data sets.

For each data set, the interface corresponding to the data set created in the page to be presented may refer to 101 shown in fig. 1. In the step, an interface corresponding to the data set is created in the interface to be displayed for all the data sets obtained by inquiry. For example, for the data sets "XXX", "YYY" and "ZZZ" shown in FIG. 1, an interface is created as shown at 101; for the data sets "XXXX", "YYYY" and "ZZZZZ" shown in FIG. 1, an interface is created as shown at 102.

And rendering and displaying each created interface according to the design interface. That is, the presentation of each interface depends on the same design page. Therefore, when the design page in the information of the form is configured, each interface can be rendered and displayed according to the design page only by configuring the design page once. That is, the display of the whole page to be displayed containing at least one group of data sets can be realized by simply configuring the control which is suitable for the group of data sets, so that the workload of developers can be obviously reduced, and the development efficiency is improved.

In this step, for at least one set of data sets obtained by the query, at least one corresponding interface is created in the page to be presented. Correspondingly, after rendering and displaying the interface according to the design page, displaying at least one design page in the pages to be displayed after completing rendering and displaying.

In one example, each data set includes at least one data item therein; the design page comprises information of components required to be displayed in the form and a mapping relation between the components and the data items. Rendering and displaying the data set associated with the interface according to the design page, wherein the rendering and displaying can specifically comprise: and filling each data item into the corresponding component of each data item according to the information of the component and the mapping relation between the component and the data item.

For a better explanation of the method provided in this embodiment, please continue to refer to the display effect of the page to be displayed with the form type shown in fig. 1 being a list page. The components involved in this example are shown in the words "problem feedback" and "problem description", "problem type", etc., indicated by 103 in fig. 1, and the data items are shown in the words "XXX", "yyyyy", "ZZZZZ", etc., in fig. 1.

It will be appreciated that, for the page to be displayed as shown in fig. 1, the design page includes information of the components to be displayed, that is, information of the components "problem feedback", "problem description" and "problem type". The data item "XXX" has a mapping relationship with the component "problem description" and is therefore populated into the component "problem description" in the interface 101 during the rendering presentation.

In this example, according to the mapping relationship between the pre-established components and the data items, each data item in the created data set associated with each interface can be accurately filled into the corresponding component. In addition, the information of the components required to be displayed in the form and the mapping relation between the components and the data items are only required to be configured once, so that each interface can display each data according to the information, the workload of a developer can be obviously reduced, and the development efficiency is improved.

In one example, the process of rendering the presentation according to the design page may specifically be: generating json data according to the design page, and rendering and displaying according to the json data.

It should be noted that, for the pages to be presented with different form types, the corresponding design pages may be the same, and thus the json data corresponding thereto may also be the same. In this case, different rendering strategies can be adopted to render the data to be displayed according to different types of the page forms to be displayed.

Specifically, a uniform resource locator (Uniform Resource Locator, abbreviated as "URL") for indicating a resource address corresponding to a rendering policy of a page to be presented may be generated according to a form type. And determining a rendering strategy according to the URL, and rendering and displaying the page to be displayed based on the rendering strategy. Because the rendering strategy is generated according to the form types of the pages to be displayed, the rendering and displaying steps can be performed on each page to be displayed by utilizing different rendering strategies in a targeted manner, and further rendering and displaying results can meet the displaying needs of different form types.

In this embodiment, the visual software development platform first obtains configuration information of a page to be displayed configured by using a visual interface in a process of displaying the page to be displayed. The configuration information comprises information of a service table, information of the table and a data query statement; wherein the information for the form includes a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a business table. According to the method and the device, the association relation is configured, and the relation between each form and the business table in the software is established, so that data required by the page can be conveniently obtained when the software renders and displays the page to be displayed currently, the data access quantity can be saved, and the data access speed can be improved.

Another embodiment of the invention relates to a method of software development. The present embodiment includes step 101 and step 102 in the previous embodiment, and the related technical details in the previous embodiment remain valid in the present embodiment. In order to avoid repetition, a description is omitted in this embodiment.

The main difference between this embodiment and the previous embodiment is that: the page to be displayed in the previous embodiment is a page of the functional module; the visual interface comprises a module setting interface, a view setting interface and a form setting interface; the step 101 of obtaining configuration information of a page to be displayed configured by using a visual interface includes: obtaining module information of a function module configured by using a module setting interface, wherein the module information comprises: a service table associated with the functional module; acquiring a data query statement configured by using a view setting interface; and acquiring the form types and the design pages configured by using the form setting interface.

In order to more clearly illustrate the step of acquiring the configuration information of the page to be displayed configured by the user using the visual interface in the software development method provided in this embodiment, please refer to a configuration information acquisition flowchart shown in fig. 3.

Step 301, obtaining module information of a function module configured by using a module setting interface, where the module information includes: a service table associated with the functional module.

Because the page to be displayed is the page of the functional module, the configuration of the business table of the page to be displayed can be realized by configuring the associated business table for the functional module at the module setting interface.

It will be appreciated that the information of the modules configured using the module configuration interface is stored in a database.

It should be noted that the service table may be understood to include: a data table containing attribute information (i.e., field information) of each field in the service table, and a data table containing data corresponding to each field (i.e., data that can be displayed on a page to be displayed).

In one example, configuring the business table for the functional module may be implemented by configuring an association entity for the functional module. The related entity indicates a data table related to the functional module in the database, and the configuration of the related entity for the functional module configures the related relationship between the related entity and the data table for the functional module.

It can be understood that the service table associated with the functional module is the data table indicated by the associated entity. Further, the fields initially included in the data table may be understood as default fields in the traffic table.

It should be noted that, if no management is performed on the service table in the subsequent configuration process, the default field is the service table of the functional module. Otherwise, the final data table formed after management is completed is a service table associated with the functional module.

It should be noted that, in software having a plurality of functional modules, the association relationship between different functional modules is also realized by the association relationship between the associated entities configured for each functional module. That is, if there is an association relationship between two data tables maintained in the database, there is an association relationship between two function modules corresponding to the two data tables. The association relationship between modules refers to that data interaction can be performed between modules, and the association relationship is essentially data interaction between data tables.

In one example, the acquired module information configured for the functional module further includes an interface name and a module ID. The interface name, module ID, and associated entity of each functional module are unique.

Specifically, the interface name of the function module and the associated entity are stored in the database after the configuration is completed, and the module ID of the function module may be automatically generated according to the interface name of the function module and the associated entity.

In addition, the visual interface may also include a field setting interface; the field setting interface is used for managing field information in the service table.

It should be noted that, after the association entity is configured for the functional module, each field in the data table indicated by the association entity is displayed in a list form in a field list page provided by the software development platform. It will be appreciated that these fields are default fields in the traffic table.

The field information of each field in the field list page can be managed by using the field setting interface. In addition, operations such as adding fields or deleting fields can be performed on the data table indicated by the associated entity. And after the management of the data table indicated by the associated entity is completed by utilizing the field setting interface, the formed final data table is a service table associated with the functional module.

The field information includes a field type and a field source; the rendering display format of the field in the page to be displayed is determined according to the field type; the data set is obtained from the database based on the source of the field.

It should be noted that the rendering presentation format of a field with a fixed field type in a page to be presented of a different form type may be different. It will be appreciated that the fields displayed in the form, whose rendering presentation format is determined by both the field type and the form type.

And the field source is used to indicate from which database the data corresponding to the field should be obtained.

It is understood that field configuration is performed to configure the data that can be presented by the functional module. The information of each field which can be displayed can be conveniently configured by using the field setting interface provided by the visual software development platform.

Step 302, a data query statement configured by using a view setting interface is acquired.

It can be understood that the service table and the data query statement are configured for the page to be displayed, which is essentially the data to be displayed for the page to be displayed.

It will be appreciated that the information of the views (i.e., data query statements) that are configured using the view configuration interface are stored in the database.

Configuring the data query statement for the page to be displayed may specifically include acquiring the data query statement configured by using the view setting interface, and configuring the data query statement for the page to be displayed.

List pages typically require a large amount of data to be presented, and accordingly, the amount of data that needs to be loaded when presenting a list page is also large. In the traditional data loading mode, when a large number of software users operate software at the same time, the data access amount of the server is huge, and the data access pressure of the server can be obviously increased, so that the loading speed of the software page is reduced, and the use experience of the software users is negatively influenced.

In this step, a data query statement is obtained, which is used to obtain the data required to be displayed by the list page in the service table. When the page is displayed, partial data obtained by query is displayed instead of all data in the service table. The data access amount can be effectively saved, and the data access speed is improved. Especially, under the condition that the number of running clients is large, the software use experience can be remarkably improved.

In one example, the data query statement may be embodied as an SQL statement. And each group of data groups obtained by utilizing the SQL statement query meet the SQL condition.

In one example, the view settings interface includes: a view condition setting box for rights setting and a selection area providing a presentation field for selection; wherein the selection area includes: a first area for displaying candidate fields and a second area for displaying selected presentation fields; the candidate field is determined from the traffic table. For a better understanding of the view setting interface provided in this example, please refer to a view setting interface schematic diagram shown in fig. 4.

In the view setting interface as shown in fig. 4, a view condition setting frame is shown as 401 in fig. 4. The view condition setting box is used for performing authority setting. Specifically, according to the option selected in the view condition setting box, the range of data that can be used for the currently configured view can be limited.

The selection area is shown as 402 in fig. 4, where the first area refers to 403 shown in fig. 4, and the candidate fields in the first area are generated according to the service table, that is, the fields included in the candidate fields are the fields included in the service table associated with the function module. That is, the candidate fields are fields included in the field list page. It will be appreciated that the field information of each field is set through the field setting interface.

The second area is shown with reference to 404 in fig. 4. The field presented on the page of the software is selected in the first area and the selected field is displayed in the second area.

In this example, obtaining the data query statement configured with the view setting interface may include: and acquiring screening conditions determined by the view condition setting frame and the selection area, and generating a data query statement according to the screening conditions.

It should be noted that, in the case that the service table associated with the functional module is understood as a data table of a plurality of rows and a plurality of columns, setting the view condition for the view essentially limits the data that can be used by the view to the data of several rows in the service table. That is, view conditions limit the data used by the view.

While selecting the presentation field of a view in the selection area essentially limits the data that can be used by that view to a few columns of the rows of data described above. That is, field selection of the selection area places further column restrictions on the data that the view can use.

Thus, acquiring the filtering condition determined using the view condition setting frame and the selection area and determining the data query statement is essentially a process of locating the data that can be used by the view as part of the data in the business table.

In one example, the view settings interface also includes a screenable field selection box, as shown at 405 in FIG. 4.

To implement the search or filtering functions in software, the screenable fields may be configured for the view in a screenable field selection box as shown at 405.

It should be noted that the optional fields provided in the screenable field selection box herein are typically fields in the field list that fix certain field types. It will be appreciated that the field types of these fields are set by the field setting interface.

Specifically, if a field with a field type of link is selected in the screenable field selection box, a search box as shown in 801 in fig. 8 is displayed in the page to be displayed. If a field with field type enum is selected in the screenable field selection box, a screen button as shown in 802 in fig. 8 is displayed in the page to be displayed.

It is worth noting that, after the software development platform obtains the fields selected by the screenable field selection frame, the software development platform generates a data query statement according to the screening conditions and the fields selected by the screenable field selection frame.

In another example, a setup button may also be included in the view setup interface to set up the display format of the selected presentation field. Since the field displayed in the second area is set, it is disposed beside the second area, see 406 shown in fig. 4.

If the display format of the selected display field is to be configured, the selected display field to be configured may be selected first, and then the setting button may be triggered.

After detecting that the set button is triggered, the software development platform provides a configuration interface for the selected display field for a platform user to configure the display format of the selected display field.

The configuration of the display format of the selected presentation field may specifically include setting such that a field satisfying the condition among the fields is displayed in a set color or the like. The configuration of these field display formats may serve to emphasize certain data to the software user at the software page, etc.

Step 303, the form type and design page configured by the form setting interface are obtained.

The information of the form, including the form type and design page, is used to determine how each interface in the page to be exposed is ultimately exposed in the software. It will be appreciated that in the page to be presented as shown in fig. 8, the information of the form determines the rendering presentation of the region as shown at 803.

It will be appreciated that the information of the completed form configured using the form configuration interface is stored in the database.

In one example, the form setting interface includes: newly adding an interface and a design interface. In order to better understand the form setting interface provided in this embodiment, the newly added interface refers to the schematic diagram of the newly added interface shown in fig. 5, and the design interface refers to the schematic diagram of the design interface shown in fig. 6.

In this example, acquiring the form type and the design page configured by using the form setting interface may include: acquiring a form type of a form configured by using the newly added interface; and under the condition that the form type of the form is a list page, acquiring a data query statement which utilizes the newly added interface as the form association.

In the newly added interface of the form setting interface shown in fig. 5, the name of the newly added form may be input in an input box shown in 501, and the form type of the newly added form may be selected in an input box shown in 502.

If the selected form type is a list page, a view associated with the newly added form may also be selected in the input box as shown in 503, i.e. the form associated data query statement.

It will be appreciated that the data query statements associated herein for the newly added form are configured via the view settings interface.

The list page generally needs to display a large amount of data, and under the condition of large data amount, the data query statement is bound for the form, so that the form only needs to display the queried data instead of all data in the database, the page loading speed can be improved, and the software use experience of a user is effectively improved.

The design interface includes a component area providing components and a design area for designing a form; wherein, in the case that the form types of the configured forms are different, formats of the components of the component areas are different; in the case where the form type of the form is a list page, the components of the component area include a field component for displaying each data item in the data group.

In the design interface of the form setting interface shown in fig. 6, the component area is shown as 601 in fig. 6, and the components are shown as 603 and words such as "problem description".

It should be noted that, when designing a form whose form type is a list page, each component in the component area in the design interface is determined according to the data query statement bound for it at the newly added interface. Specifically, each component in the design area is a presentation field selected in a selection area of the view setting interface in the process of configuring the data query statement.

It will be appreciated that associating data query statements for forms enables components that are selectable when the form is configured to set presentation fields selected in a selection area of the interface for the view. And the service table is associated with the data query statement, so that the selected display field in the data query statement is the field determined according to the service table. For a user of the software development platform, the corresponding relation between the components and the fields for selection can be established only by associating data query sentences for the forms and associating service tables for the data query sentences.

And because each component which can be selected in the component area corresponds to a field, and each field is configured with a field type in the field configuration process, the field type of the field corresponding to the component can be determined only by selecting the component in the configuration form process, and the rendering display format of the component on the page to be displayed can be determined. Related consideration of display formats of all components is not needed in the form configuration process, so that the complexity of designing the page to be displayed is greatly reduced, and the convenience of designing the page to be displayed can be effectively improved for a software development platform user.

It can be understood that after a form whose form type is a list page is newly added to the new interface and a data query statement is bound for the form, when entering the design interface to design the form, the software development platform obtains information of selected fields contained in the data query statement bound by the form from the database, and displays each component in a component area of the design interface based on the information of the selected fields.

In addition, because the components to be selected in the component area have a corresponding relation with the fields, after the components displayed in the form are selected and the design of the form is completed, the components can be automatically corresponding to the fields according to the selected components, and correct data can be automatically acquired when rendering and displaying are performed.

Further, a design page is generated according to the selected components in the component area and the arrangement mode of the selected components in the design interface.

In one example, the information for the form configured with the newly added interface of the form setting interface also includes a uniform resource locator URL automatically generated from the interface name of the module and the form type. The URL for the newly added form is automatically generated after the form type for the form is set and displayed in the area as shown at 504.

When a URL is generated for a form, rendering and displaying a page to be displayed according to configuration information may specifically be: and determining a rendering strategy according to the URL, and rendering and displaying the page to be displayed according to the configuration information based on the rendering strategy. For the pages to be displayed with different form types, the corresponding design pages may be the same, so that for the different pages, the step of rendering and displaying by using different rendering strategies according to the form types can enable the displayed pages to meet the display needs of the form types.

In designing a form whose form type is a list page, each component of the component area please continue to refer to each component in the component area indicated by 601 in fig. 6.

The components in the component area may be dragged into the design area as shown at 602 using a drag and drop or the like, and the form is designed in the design area. The selected components can be arranged randomly in the design area according to the requirement of page display.

The mapping relation between the components and the fields which are displayed for the design form is established by dragging the components in the component area into the design area.

In the design interface shown in FIG. 6, a design page generated from the selected components and the arrangement of the components may continue to refer to the page shown at 602.

And under the condition that the form type of the page to be displayed is a list page, displaying each group of data to be displayed of the page to be displayed according to the design page shown by 602, so that at least one design page is displayed on the page to be displayed.

In addition, the design page is generated according to the selected components and the arrangement mode of the components, and in practical implementation, the method can be realized by triggering a json button shown as 604 after the design of the form is completed, so as to generate json data for representing the design page.

It will be appreciated that the json data characterizing a design page is only relevant to the selected components and the design of the form in the design area, and thus the json data corresponding to forms of different form types may be the same. In this case, the rendering policy indicated by the URL generated according to the form type is used to render and display the forms of different form types, so that the requirements of the pages of different form types can be satisfied.

In the embodiment, the fields, the data query sentences, the forms and other parts can be tightly connected only by simply configuring the fields, the data query sentences, the forms and other parts through a visual interface, associating the data query sentences with the service tables and associating the forms with the data query sentences. In addition, since the form is associated with a data query statement and the data query statement is associated with a business table, the components and fields that are selectable during the form configuration have a correspondence.

In the process of field configuration, the field type of the field is determined, namely the display format of the field on the page to be displayed is determined. Furthermore, in the form configuration process, as the optional components correspond to the fields, the display format of each component on the page to be displayed can be determined by only selecting the components. In addition, in the process of configuring the data query statement, the content such as searching or screening can be displayed in the page to be displayed by selecting the selectable field. And in the form configuration process, the design of the form display format can be realized through selecting and arranging components.

It can be seen that, in this embodiment, each step including the configuration field, the view, and the form together determines the final rendering display effect of the page to be displayed, where the final rendering display effect of the page to be displayed is the integrated effect of the plurality of configuration steps. For a user of the software development platform, the display formats of all parts in the page to be displayed are separated into a plurality of configuration steps for configuration, so that the complexity of designing the page to be displayed can be greatly reduced, and the convenience of designing the page to be displayed is effectively improved.

In addition, in the process of displaying the page to be displayed, the visual software development platform provided by the embodiment of the invention firstly obtains the configuration information of the page to be displayed, which is configured by utilizing the visual interface. The configuration information comprises information of a service table, information of the table and a data query statement; wherein the information for the form includes a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a business table. According to the embodiment of the invention, the association relation is configured, so that the relation between each form and the business table in the software is established, the data required by the page can be conveniently acquired when the page to be displayed is rendered and displayed by the software, the data access quantity can be saved, and the data access speed can be improved.

In order to more clearly illustrate the software development method provided by the invention, another embodiment of the invention is used for illustrating a development process of a piece of software, wherein the piece of software comprises at least one functional module, and one functional module comprises a page with a form type of list page.

In this embodiment, the software development platform first provides a module list page including a plurality of function modules stored therein in advance. The user may trigger a configuration button for one of the functional modules to configure that functional module.

The software development platform provides a module setting interface when detecting that a user triggers a configuration button, so that the user configures module information for the functional module by utilizing the module setting interface.

The module information configured for the functional module here may include a service table, an interface name, and a module ID.

Configuring the service table for the functional module may be implemented by configuring the functional module with an associated entity. It should be noted that, in the subsequent configuration process, the data table indicated by the associated entity may be managed, that is, the service table associated with the functional module is updated.

The technical details of configuring the module information are described in the above embodiment, and remain valid in this embodiment. To avoid repetition, no further description is provided here.

In addition, the module configuration interface further includes: a field control, a button control, a view control, and a form control; for a better understanding of the module setting interface provided in this embodiment, please refer to a schematic diagram of the module setting interface shown in fig. 7.

Wherein the button controls in the module configuration interface are shown in the "button" word indicated at 702, and the view controls and the form controls are shown in the "view" and "form" words in fig. 7, respectively.

It should be noted that, in the module setting interface shown in fig. 7, when a user wants to configure module information for a functional module, the user may trigger the module information control shown in 701 in fig. 7, so as to input module information in the module information setting interface provided by the software development platform. After the software development platform detects that the module information control is triggered, a module information setting interface is provided, and module information is configured for the functional module according to the input information of a user on the module information setting interface.

After completing the configuration of the module information of the functional module, the software development platform user may trigger the field control to perform the configuration of the fields required by the functional module.

The software development platform provides a field list page in the case that the field control is detected to be operated, wherein the field list page comprises: a field adding control and a field list set through a field setting interface; the field adding control triggers the provision of a field setting interface when operated, and the default field of the business table is displayed when the field list page is displayed for the first time.

It should be noted that, when the field list page is displayed for the first time, the default field of the service table is displayed. That is, the fields first displayed in the field list page are generated from the associated entities of the function module. When the field list page is displayed for the first time, the software development platform acquires a data table corresponding to the associated entity of the function module from the database, and displays all fields in the data table in the field list page in a list form.

It is understood that the associated entity of the function module is a service table configured for the function module at the module information setting interface.

In addition to the default fields of the service table, which are initially displayed in the field list page, the fields in the field list page may be managed by using a field setting interface provided by the software development platform, which may specifically include performing operations such as adding, deleting, and editing.

If the user needs to newly add the field according to the requirement, the user only needs to trigger a field adding control in the field list page, and the newly added field is configured on a field setting interface provided by the software development platform.

The field setting interface is used for managing field information in the service table; the field information includes a field type and a field source; the rendering display format of the field in the page to be displayed is determined according to the field type; the data set is obtained from the database based on the source of the field. The information of each field which can be displayed can be conveniently configured by using the field setting interface provided by the visual software development platform.

The information configured for a field using the field configuration interface may include a field type and a field source.

The field type is used to determine the rendering presentation format of the field in the software page. Specifically, the field with the field type link has two rendering display formats in the page to be displayed: if the field with the field type link is selected as the screenable field in the view configuration process, the fixed display format of the field in the page to be displayed is a search box as shown in 801 in fig. 8; if a component corresponding to a field with a field type link is selected for presentation during the form design process, the fixed presentation format of the field in the software page may refer to component 103 shown in fig. 1.

It is also worth mentioning that the field of field type enum also has two rendering presentation formats in the page to be presented. If the field with field type enum is selected as the screenable field in the process of view configuration, the fixed display format of the field in the page to be displayed is a screening button as shown in 802 in fig. 8.

The fields configured and saved through the field setting interface are displayed in the field list page. Each row in the field list page includes field information for that field.

After the fields are newly added, the fields are saved again in the field list page, and all the fields of the field list page including the newly added fields can be saved in a database, and the business table associated with the function module can be updated in the database.

It is understood that field configuration is performed to configure the data that can be presented by the functional module.

After completing the configuration of the fields required for the functional module, the software development platform user may trigger the button control to configure the buttons required for the functional module.

The buttons required for the functional module are configured to enable the software to realize functions such as skip, popup, page switching and the like.

The software development platform provides a button list page in the case that the button control is detected to be operated, wherein the button list page comprises: a button adding control and a button list set through a button setting interface; the button adding control triggers the provision of a button setting interface when operated, and a button list set through the button setting interface is empty when the button list page is displayed for the first time.

It should be noted that fig. 7 shows a schematic diagram of providing a button list page for the software development platform in the case that the button control is detected to be operated.

In the event that user manipulation of the button control is detected, the software development platform provides a button list page as shown at 703, including a button add control as shown in the "New" typeface as indicated at 704, and a button list as shown at 705.

If the user needs to add the button newly according to the requirement, the user only needs to trigger the button adding control in the button list page, and the newly added button is configured on the button setting interface provided by the software development platform.

The button setting interface is used for configuring information of buttons required by the page to be displayed; the information of the button includes a button type and a button function; the rendering display format of the button in the page to be displayed is determined according to the type of the button; the button functions are determined from the form or data set bound for the button.

Information configured for a button using a button configuration interface may include button type and button function.

Wherein the button type determines the rendering presentation format of the button in the software. The button types may include a new button, an edit button, a list page button, a detail page button, and the like. For a button whose button type is a newly added button, its display format at the software page fix is preset as a plus sign in the upper right corner of the page in view of convenience of use (see 803 in fig. 8).

In addition, for the button with the button type of the list page button, the button needs to be displayed on all list pages, and the rendering display format of the button on each list page is also a preset list page button display format.

It should be noted that, since the button set as the list page button needs to be displayed on all list pages, the display information of the button can be set as list display, so that the button can be set as the list page button.

Accordingly, if the button type of a certain button is set as a detail page button, the display information of the button can be set as detail display, and the button can be displayed in all detail pages of the software according to a preset rendering display format. For the list page button and the detail page button, the list page button and the detail page button can be set to be displayed on each list page or each detail page in the process of configuring the buttons, and the buttons are not required to be bound one by one for the forms with the form types being the list pages. In addition, the rendering display format can be determined in the process of configuring the buttons, and consideration on how the buttons render and display is not needed in the subsequent configuration process, so that the complexity of rendering and displaying the page to be displayed can be effectively reduced.

If a button is displayed only in a certain form, the configuration of the display page on the button configuration interface is not required, and the button and the form may be bound when the form is configured.

In addition, determining button functions from a form or data set bound for a button refers to: for example, a form in which the button binding form type is a detail page, the button function may be determined to jump to the detail page.

It will be appreciated that reference herein is made to button-bound forms, i.e. forms configured via a form configuration interface as referred to in the previous embodiment.

Buttons configured and saved through the button setting interface are displayed in a button list page and saved in the database. Specifically, each row in the button list includes information configured for that button.

After completing the configuration of the buttons required for the functional module, the software development platform user may trigger the view control to configure the view required for the functional module.

It will be appreciated that the view required to configure the functional module is actually a definition data query statement. While the data query statement essentially serves to define the scope of the data in the business table that can be used.

It will be appreciated that the service table referred to herein is the service table that is ultimately formed after the foregoing field configuration process is completed.

The software development platform provides a view list page in the case that the view control is detected to be operated, wherein the view list page comprises: a view adding control and a view list generated through a view setting interface; the view adding control triggers the provision of a view setting interface when operated, and a view list generated through the view setting interface is empty when the view list page is displayed for the first time.

It will be appreciated that the format of the view list page is similar to the field list page shown in fig. 6 and will not be shown here to reduce repetition. The view setup interface please continue with reference to fig. 4.

When the view list page is displayed for the first time, the view list is empty, and a user only needs to trigger a view adding control when desiring to perform view configuration for the functional module, and the view is configured on a view configuration interface provided by the software development platform.

And the software development platform provides a view configuration interface and acquires a data query statement configured by a user by using the view configuration interface under the condition that the view adding control is detected to be triggered.

The technical details about the view setting interface and the data query statement in the previous embodiment are still valid in this embodiment, and are not repeated here for reducing repetition.

It should be noted that, the field type of the optional field in the optional field selection box (see 405 in fig. 4) in the view setting interface is configured as link or enum in the field setting interface. Configuring these fields at view configuration enables search or filtering functions in a software page.

The views configured and saved through the view setting interface are displayed in the view list page and saved in the database. Specifically, each row in the view list includes information configured for that view.

After completing the configuration of the view required by the functional module, the software development platform user may trigger the form control to perform the configuration of the form required by the functional module.

It will be appreciated that the form required to configure a functional module is actually a process of determining how the pages of the functional module are ultimately presented.

In the event that a form control is detected to be operated, providing a form list page comprising: form adding controls and form lists generated through a form setting interface; the form adding control triggers the provision of a form setting interface when operated, and a form list generated through the form setting interface is empty when a form list page is displayed for the first time.

It will be appreciated that the format of the form list page is similar to the field list page shown in fig. 6 and will not be shown here to reduce repetition. The view setup interface please continue with reference to fig. 5 and 6.

When the form list page is displayed for the first time, the form list is empty, and a user only needs to trigger a form adding control when the user wants to configure the form for the functional module, and the form is configured on a form configuration interface provided by the software development platform.

The software development platform provides a form configuration interface under the condition that the form adding control is triggered, and acquires information of a form configured by a user through the form configuration interface.

Specifically, the software development platform provides a new interface in the form configuration interface under the condition that the form adding control is detected to be triggered.

The user configures information such as the form type of the form in the newly added interface, and the information is a form binding view, namely a data query statement, of which the form type is a list page.

It is worth mentioning that the views bound for the form herein are views in the view list set in the view setting interface.

It will be appreciated that the data query statement is configured for the form, i.e., the data that can be used for the form configuration.

Correspondingly, the software development platform acquires form types and data query sentences configured for the form by the user through the newly added page.

And completing the configuration of the basic information of the form through the newly added interface of the form configuration interface, and displaying the submitted form in a list page of the form. Each row in the list of forms includes the underlying information for that form.

The user may select any form in the list page of forms and trigger a design button for that form to design it.

Correspondingly, after detecting that the design button is triggered, the software development platform provides a design interface of the form setting interface for a user to design the form.

In the above embodiment, the technical details about the form setting interface and the configuration form are still valid in this embodiment, and are not repeated here for reducing repetition.

It should be noted that, when designing a form whose form type is a list page, each component in the component area in the design interface is determined according to the data query statement bound for it at the newly added interface. Specifically, each component in the design area selects each component displayed in the selection area of the view setting interface in the process of configuring the data query statement.

It should be noted that, for a button that needs to be displayed only on a certain page, the component may be selected in a design area of the design interface, and a corresponding button may be bound for the component.

If the button function of the button is to jump to a detail page, the page will jump to the detail page when the list page is finally displayed if the button is detected to be triggered.

It should be noted that, in the foregoing process of performing button setting, if the list page button is set, the list page button is also included in the form whose form type is a list page.

The information of each button mentioned above is also presented in json data reflecting the page display mode together with the design information of the page such as the components and the arrangement mode thereof after the "generate json" button is triggered.

It should be noted that, for the buttons displayed on each page, the display format of the buttons on the page is set on the button setting interface, and the setting of the buttons is not involved in the form setting interface, so that the information of the buttons is not reflected in json data.

In the process of configuring module information, fields, buttons, views and forms for the functional modules, the field type can be configured to determine the rendering display format of the fields on the page, the button type can be configured to determine the rendering display format of the buttons on the page, the view setting can determine which data are displayed on the page, the contents such as searching or screening can be displayed on the page to be displayed, and the form configuration can determine the components displayed on the page to be displayed and the arrangement mode of the components. The final rendering and displaying effect of the page is the result of the comprehensive effect of the configuration steps. For a user of the software development platform, the display of the final page to be displayed can be realized by simply configuring each part of the fields, the buttons, the views and the forms.

In addition, when the page is displayed according to the form, the data query statement is bound to the form, so that data required by display can be conveniently obtained in the rendering and displaying process. The components shown in the form are determined according to the configured fields, and meanwhile, the data determined by the data query statement is also found in the service table determined after the field configuration is carried out. The button can bind the form to which the jump is made, and the button can be bound for the component in the form configuration process. The form, the view, the buttons and the fields are mutually bound, and each configuration step in the configuration process is mutually intersected, so that software development can be simply, conveniently and flexibly performed, the complexity of the software development is effectively reduced, and the flexibility and the convenience of the software development are improved.

In addition, when the software is required to be adjusted and modified by utilizing the configuration mode, the software can be modified only by adjusting the configuration information according to the requirement, so that the development efficiency of the software can be improved.

When the software is displayed, a preset page containing a plurality of functional modules can be displayed first. When the software development platform detects that a certain functional module is triggered, a service list, a button list, a view list and a form list corresponding to the functional module are acquired from a database, and then rendering and displaying of the functional module are carried out.

It should be noted that the rendering and displaying process described herein is directed to the case that the page that the functional module needs to display first is a list page.

What the software development platform first needs to render is a list page button. Specifically, the button list is traversed, and the list page button is determined in the button list. And rendering the buttons according to a preset rendering display format according to the button types configured for the buttons.

Further, the software development platform traverses the view list and generates a page to be displayed for each view. The form type of the page to be displayed is a list page, namely, the form type of the form bound with each view is a list page.

It should be noted that, in the case that the view list includes a plurality of views, the display sequence of each generated page to be displayed is determined according to the sequence of the views corresponding to the page to be displayed in the view list. Specifically, for each view arranged in the view list in the order from top to bottom, the display order of each corresponding page to be displayed is from left to right.

For each page to be displayed, configuration information configured by utilizing a visual interface is firstly obtained. The method specifically comprises the steps of inquiring data of the page to be displayed and information of the form.

It can be understood that the data query statement of the page to be presented, i.e. the data query statement characterized by its corresponding view. The form is the form that binds to the view.

Further, the data to be displayed of the page to be displayed is obtained from the service table according to the data query statement, and the rendering strategy is determined according to the URL in the information of the table. And rendering and displaying json data representing the design page and the queried data by using a rendering strategy.

The technical details concerning rendering presentation in the above embodiment still apply in this embodiment, and in order to reduce repetition, this will not be described here.

It should be noted that, the data acquired in the service table according to the data query statement is divided into multiple data groups.

In one example, the "question description" and the "question feedback" and "question type" data items corresponding thereto are a set of data sets. Wherein the three fields of "question description", "question feedback" and "question type" are fields selected in the selection area in the view configuration interface.

And rendering and displaying each data group by combining the rendering strategy with json data. And rendering and displaying results of each group of data, namely displaying each interface in the page to be displayed according to the sequence from top to bottom.

If the button is bound for the problem description component when the form is configured, and the button is used for jumping to the detail page, all the problem description components displayed in the page to be displayed are bound with the button.

In addition, after detecting that the button bound by the problem description component is triggered, the software development platform acquires the data set bound for the button and the information of the form bound for the button, and further renders the detail page displayed after the button is triggered according to the information.

The rendering presentation process described above is directed to rendering presentation of a page to be presented whose form type is a list page. In the case that the page to be first displayed in the functional module is not a list page, part of the steps in the rendering display method described above are not necessarily applicable.

In this case, the setting option of the first form may be provided in the form setting page. I.e. a certain form can be set as the form presented in the home page of the functional module.

In one example, the page first shown by the functional module is a detail page, and then the form with the form type configured as the detail page is configured as a first page table in the form configuration process.

Similarly, what the software development platform first needs to render is a detail page button. Specifically, the button list is traversed, and the detail page buttons are determined in the button list. And rendering the buttons according to a preset rendering display format according to the button types configured for the buttons.

Further, the software development platform traverses the list of forms, determines the first form, and obtains the information of the first form. And then determining a rendering strategy according to the URL in the information of the form, and rendering json data corresponding to the form in the page to be displayed.

It should be noted that, for the detail page, the data query statement is not configured for the detail page in the foregoing configuration process, and the data to be displayed is directly obtained in the service table according to json data.

It can be understood that if the first form is a new page or an edit page, the information of the first form is directly obtained without performing button rendering, and then a rendering strategy is determined according to the URL in the information of the form, and the json data corresponding to the form in the page to be displayed is rendered.

The above steps of the methods are divided, for clarity of description, and may be combined into one step or split into multiple steps when implemented, so long as they include the same logic relationship, and they are all within the protection scope of this patent; it is within the scope of this patent to add insignificant modifications to the algorithm or flow or introduce insignificant designs, but not to alter the core design of its algorithm and flow.

The embodiment of the invention also provides a visual software development platform, as shown in fig. 9, which comprises:

the configuration module 901 is configured to obtain configuration information of a page to be displayed configured by using a visual interface, wherein the configuration information comprises information of a service table, information of a form and a data query statement; the information of the form comprises a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a service table;

the rendering and displaying module 902 is configured to render and display a page to be displayed according to the configuration information;

It should be noted that, the execution bodies of the foregoing embodiments are all visualization software development platforms, and it can be understood that the technical details in the foregoing embodiments are still valid in this embodiment. To reduce repetition, no further description is provided herein.

In the process of displaying the page to be displayed, the visual software development platform provided by the embodiment firstly obtains the configuration information of the page to be displayed configured by utilizing the visual interface. The configuration information comprises information of a service table, information of the table and a data query statement; wherein the information for the form includes a form type and a design page, the form is configured to be associated with a data query statement, and the data query statement is configured to be associated with a business table. According to the method and the device, the association relation is configured, and the relation between each form and the business table in the software is established, so that data required by the page can be conveniently obtained when the software renders and displays the page to be displayed currently, the data access quantity can be saved, and the data access speed can be improved.

Embodiments of the present invention also provide an electronic device, as shown in fig. 10, comprising at least one processor 1001; and a memory 1002 communicatively coupled to the at least one processor 1001; the memory 1002 stores instructions executable by the at least one processor 1001, and the instructions are executed by the at least one processor 1001 to enable the at least one processor 1001 to perform the method for probe software development described above.

Where the memory 1002 and the processor 1001 are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the buses connecting the various circuits of the one or more processors 1001 and the memory 1002. The bus may also connect various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or may be a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 1001 is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor 1001.

The processor 1001 is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 1002 may be used to store data used by processor 1001 in performing operations.

The product may execute the software development method provided by the embodiment of the present invention, and has the corresponding functional module and beneficial effects of the execution method, and technical details not described in detail in the embodiment of the present invention may refer to the method provided by the embodiment of the present invention.

The processor is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory may be used to store data used by the processor in performing operations.

Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The steps of the software development method embodiments described above are implemented when the computer program is executed by a processor.

That is, it will be understood by those skilled in the art that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, where the program includes several instructions for causing a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps in the methods of the embodiments described herein. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific embodiments in which the invention is practiced and that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims

1. The software development method is characterized by being applied to a visual software development platform and comprising the following steps:

acquiring configuration information of a page to be displayed configured by utilizing a visual interface, wherein the configuration information comprises information of a service table, information of the table and a data query statement; wherein the information of the form includes a form type and a design page, the form configured to be associated with the data query statement, the data query statement configured to be associated with the business table;

rendering and displaying the page to be displayed according to the configuration information; the pages to be displayed of different form types are rendered and displayed by adopting different rendering strategies;

wherein, when the form type of the page to be displayed is a list page, the rendering and displaying the page to be displayed according to the configuration information includes:

inquiring at least one group of data groups required by the page to be displayed in the service table according to the data inquiry statement, and establishing interfaces corresponding to the data groups in the page to be displayed for each data group so as to keep the number of the interfaces consistent with the number of the data groups;

For each interface, rendering and displaying the data set associated with the interface according to the design page, and completing rendering and displaying the page to be displayed; at least one design page is displayed in the pages to be displayed after rendering display is completed; the design page characterizes the display effect of each interface in the page to be displayed, and comprises each component required to be displayed in the form and the arrangement mode of each component.

2. The software development method of claim 1 wherein each of said data sets includes at least one data item therein; the design page comprises information of components required to be displayed in the form and a mapping relation between the components and the data item;

rendering the data set associated with the interface according to the design page comprises the following steps:

and filling each data item into the corresponding component of each data item according to the information of the component and the mapping relation between the component and the data item.

3. The software development method according to claim 1, wherein the page to be displayed is a page of a function module; the visual interface comprises a module setting interface, a view setting interface and a form setting interface;

The obtaining the configuration information of the page to be displayed configured by utilizing the visual interface comprises the following steps:

obtaining module information of the function module configured by using the module setting interface, wherein the module information comprises: the service table associated with the functional module;

acquiring the data query statement configured by utilizing the view setting interface;

and acquiring the form type and the design page configured by using the form setting interface.

4. A software development method according to claim 3 wherein said module information further includes an interface name;

the information of the form also comprises a uniform resource locator URL automatically generated according to the interface name and the form type;

the rendering and displaying the page to be displayed according to the configuration information comprises the following steps:

and determining the rendering strategy according to the URL, and rendering and displaying the page to be displayed according to the configuration information based on the rendering strategy.

5. A software development method according to claim 3 wherein said form setting interface comprises: adding a new interface and a design interface;

the obtaining the form type and the design page configured by using a form setting interface comprises the following steps:

Acquiring the form type of the form configured by the newly added interface; under the condition that the form type of the form is a list page, acquiring the data query statement which is related to the form by utilizing the newly added interface;

the design interface includes a component area providing the component and a design area for designing the form; wherein, in the case that the form types of the configured forms are different, formats of the components of the component areas are different; in the case that the form type of the form is a list page, the components of the component area include a field component for displaying each data item in the data group;

and generating the design page according to the selected components in the component area and the arrangement mode of the selected components in the design interface.

6. A software development method according to claim 3 wherein said visual interface further comprises a field setting interface;

the field setting interface is used for managing field information in the service table; the field information comprises a field type and a field source; the rendering display format of the field in the page to be displayed is determined according to the field type; the data set is obtained from a database according to the field source.

7. A software development method according to claim 3 wherein said view setting interface comprises: a view condition setting box for rights setting and a selection area providing a presentation field for selection; wherein the selection area includes: a first area for displaying candidate fields and a second area for displaying selected presentation fields; the candidate field is determined according to the service table;

the obtaining the data query statement configured by using the view setting interface includes:

and acquiring screening conditions determined by the view condition setting frame and the selection area, and generating the data query statement according to the screening conditions.

8. The software development method according to any one of claims 3 to 7 wherein the visual interface further comprises a button setting interface;

the button setting interface is used for configuring information of buttons required by the page to be displayed; the information of the button comprises a button type and a button function; the rendering display format of the button in the page to be displayed is determined according to the button type; the button function is determined from the form or the data set bound for the button.

9. The software development method of claim 8 wherein the module setup interface comprises: a field control, a button control, a view control, and a form control; the software development method further comprises the following steps:

providing a field list page in case that the field control is detected to be operated, wherein the field list page comprises: a field adding control and a field list set through the field setting interface; the field adding control triggers the provision of the field setting interface when operated, and the default field of the service table is displayed when the field list page is displayed for the first time;

providing a button list page in the case that the button control is detected to be operated, wherein the button list page comprises: a button adding control and a button list set through the button setting interface; the button adding control triggers the provision of the button setting interface when being operated, and the button list set by the button setting interface is empty when the button list page is displayed for the first time;

providing a view list page in the event that the view control is detected to be operated, the view list page comprising: a view adding control and a view list generated through the view setting interface; the view adding control triggers the provision of the view setting interface when operated, and a view list generated through the view setting interface is empty when the view list page is displayed for the first time;

Providing a form list page in the case that the form control is detected to be operated, wherein the form list page comprises: form adding controls and form lists generated through the form setting interface; and the form adding control triggers the provision of the form setting interface when being operated, and a form list generated through the form setting interface is empty when the form list page is displayed for the first time.

10. A visualization software development platform, comprising:

the configuration module is used for acquiring configuration information of a page to be displayed configured by utilizing the visual interface, wherein the configuration information comprises information of a service table, information of a form and a data query statement; wherein the information of the form includes a form type and a design page, the form configured to be associated with the data query statement, the data query statement configured to be associated with the business table;

the rendering display module is used for rendering and displaying the page to be displayed according to the configuration information; the pages to be displayed of different form types are rendered and displayed by adopting different rendering strategies;

wherein, in the case that the form type of the page to be displayed is a list page, the rendering display module is configured to:

11. An electronic device, comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software development method of any one of claims 1 to 9.

12. A computer-readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the software development method of any one of claims 1 to 9.