CN114968457A - Form processing method and device applied to subprogram - Google Patents
Form processing method and device applied to subprogram Download PDFInfo
- Publication number
- CN114968457A CN114968457A CN202210509993.XA CN202210509993A CN114968457A CN 114968457 A CN114968457 A CN 114968457A CN 202210509993 A CN202210509993 A CN 202210509993A CN 114968457 A CN114968457 A CN 114968457A
- Authority
- CN
- China
- Prior art keywords
- subprogram
- engine
- interface
- configuration data
- rendering
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 30
- 238000009877 rendering Methods 0.000 claims abstract description 123
- 238000012545 processing Methods 0.000 claims abstract description 63
- 230000000007 visual effect Effects 0.000 claims description 11
- 230000004044 response Effects 0.000 claims description 8
- 239000012634 fragment Substances 0.000 claims description 7
- 238000000034 method Methods 0.000 description 43
- 230000008569 process Effects 0.000 description 26
- 238000011161 development Methods 0.000 description 19
- 230000006870 function Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 230000006872 improvement Effects 0.000 description 10
- 238000004590 computer program Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 230000001960 triggered effect Effects 0.000 description 3
- 238000013480 data collection Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
Abstract
The embodiment of the specification provides a form processing method and device applied to a subprogram, wherein the form processing method applied to the subprogram comprises the following steps: under the condition that an access instruction of a form page of a subprogram is detected, triggering interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine; receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing; and displaying the form page obtained by the form rendering processing in the subprogram.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a form processing method and apparatus applied to a subprogram.
Background
With the development of internet technology and the popularization of mobile terminals, more and more services begin to extend to online scenes, application platform software capable of carrying a plurality of application subprograms appears, the situation that users install different types of application programs on the mobile terminals is avoided, the services are handled by means of the application subprograms carried in the application platform software, and meanwhile, the application subprograms can also fully utilize the sufficient user traffic of the application platform software, so that assistance is provided for the service promotion of the application subprograms.
Disclosure of Invention
One or more embodiments of the present specification provide a form processing method applied to a subroutine, including: and under the condition that an access instruction of a form page of the subprogram is detected, triggering interface calling of a form interface corresponding to the form in the form page and engine calling of a form rendering engine. And receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing. And displaying the form page obtained by the form rendering processing in the subprogram.
One or more embodiments of the present specification provide a form processing apparatus applied to a subroutine, including: the calling module is configured to trigger interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine under the condition that an access instruction of the form page of the subprogram is detected. And the form rendering module is configured to receive the form configuration data returned by the interface call and input the form configuration data into a form rendering engine returned by the engine call for form rendering processing. And the form page display module is configured to display the form page obtained by the form rendering processing in the subprogram.
One or more embodiments of the present specification provide a terminal device, including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and under the condition that an access instruction of a form page of the subprogram is detected, triggering interface calling of a form interface corresponding to the form in the form page and engine calling of a form rendering engine. And receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing. And displaying the form page obtained by the form rendering processing in the subprogram.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: and under the condition that an access instruction of a form page of the subprogram is detected, triggering interface calling of a form interface corresponding to the form in the form page and engine calling of a form rendering engine. And receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing. And displaying the form page obtained by the form rendering processing in the subprogram.
Drawings
In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;
FIG. 1 is a flowchart of a form processing method applied to a subroutine, according to one or more embodiments of the present disclosure;
fig. 2 is a schematic diagram of a form processing procedure applied to a sub program in a terminal device scenario according to one or more embodiments of the present specification;
FIG. 3 is a schematic diagram of a form processing apparatus applied to a subroutine according to one or more embodiments of the present disclosure;
fig. 4 is a schematic structural diagram of a form processing device applied to a subroutine according to one or more embodiments of the present specification.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step, shall fall within the scope of protection of this document.
The embodiment of the form processing method applied to the subprogram provided by the specification comprises the following steps:
according to the form processing method applied to the subprogram, in the process of accessing the form page of the subprogram, the form configuration data of the form in the form page is obtained by calling the corresponding form interface, the form rendering engine for performing form rendering is obtained by engine calling, then the form configuration data obtained by calling the form interface is input into the form rendering engine for performing form rendering processing to obtain the form page, and the form configuration data is obtained in the form called by the interface, so that the development difficulty and development cost of form development aiming at the subprogram are reduced, and meanwhile, the probability of faults occurring in the form using process of the subprogram is reduced, so that the subsequent maintenance work of using the form by the subprogram is reduced, and convenience is provided for developers of the subprogram while the service of the subprogram is stable.
Referring to fig. 1, the form processing method applied to a subroutine provided in this embodiment specifically includes step S102 to step S106.
Step S102, under the condition that an access instruction of a form page of the subprogram is detected, triggering interface calling of a form interface corresponding to the form in the form page and engine calling of a form rendering engine.
The sub program in this embodiment refers to a program function module or an application component loaded on an application program or a client, or a program function module or an application component loaded and installed by an application program or a client, such as a sub program (applet) in an application program. From the service perspective, the sub-program has the capability of independently providing the self-closed loop service, such as the sub-program which runs in the payment application platform and has the self-closed loop capability of service subscription and message push subscription.
The form page of the subprogram is a page with a form configured in the page of the subprogram. The form interface is an interface for acquiring form configuration data of a form in the form page, the form interface has a one-to-one correspondence with the form interface, and the form configuration data of a corresponding form can be acquired by calling the form interface, that is, if a plurality of forms exist in the form page, the form interfaces corresponding to the plurality of forms need to be respectively called to acquire the form configuration data of the plurality of forms.
The form rendering engine is a processing engine for rendering a form page for presentation according to form configuration data of a form in a process of accessing a subroutine, and the form rendering engine may be in a form of a plug-in or a form of a component (such as an NPM component); in addition, in a scenario specific to data collection by form, the form rendering engine may be integrated in an sdk (software Development kit) form to a client of an application or device specific to data collection.
In specific implementation, in the process of accessing the subprogram, detecting the access of the form page of the subprogram, triggering interface calling of a form interface corresponding to a form in the form page under the condition that an access instruction of the form page of the subprogram is detected, so as to obtain form configuration data of the form in the form page in a mode of interface calling, and triggering engine calling of a form rendering engine under the condition that the access instruction is detected, so as to obtain the form rendering engine in a mode of engine calling.
In practical application, a certain learning cost is required for performing form development on the subprogram, and development cost is also required, in order to reduce the difficulty in developing the form for the subprogram, in an optional implementation manner provided in this embodiment, the work of a developer in the form development process is reduced by providing a form component with a basic granularity, and specifically, the form interface is generated in the following manner: generating the form configuration data according to the selected form component and the configuration data input by editing the form component; storing the generated form configuration data and generating the form interface based on the form configuration data.
Optionally, the form interface is generated and then issued to the provider of the subprogram, so as to initialize the interface call of the form interface in the code segment of the subprogram.
The form component is a form element required in the form development process aiming at the subprogram, developers only need to select the corresponding form element without independently developing the form elements forming the form, and develop the selected form element in a configuration mode, so that the learning cost and the development difficulty in the form development process aiming at the subprogram are greatly reduced. The form configuration data includes the style, attributes and/or source data related to the sub-program service of the form.
In order to further reduce the learning cost and the development difficulty of performing form development on a subprogram, the embodiment assists a developer to perform form development on the subprogram by providing a visual form development environment, and optionally, the selection and the editing of the form component are performed based on a visual editing interface of a form editor; the form component is selected by the provider of the subprogram in the visual editing interface, and the configuration data is edited and input by the provider of the subprogram.
On the basis, in order to guarantee the form development quality of developers and reduce the workload of subsequent form maintenance, a preview access control can be configured in a form editor, the developers can check the page which is actually run in the subprogram of the current form development by triggering the preview access control, and when the form editor detects that the preview access control is triggered, the forms which are currently developed are rendered through a form rendering component configured by the form editor or by calling the form rendering engine, so that the developers can intuitively perceive the progress and the situation of the form development.
In addition, after the form configuration data is generated, in the process of storing the form configuration data, the form configuration data may also be stored in a server of the subprogram, so as to ensure real-time access in the process of accessing the actual subprogram, and optionally, the form configuration data is stored in the server, and the server responds to the interface call, reads the form configuration data of the form corresponding to the form interface, and returns the form configuration data to the subprogram.
In this embodiment, a form page is accessed in a subroutine, the volume of a code fragment of the subroutine is often very small in practice, and the rendering of the form page needs to rely on a specific tool (a form rendering engine), and the volume of the form rendering engine is much larger than that of the code fragment of the subroutine, so that, in order to ensure that the access of the subroutine is not affected, the form rendering engine required for performing form rendering is remotely obtained in an engine calling manner, in an optional implementation manner provided in this embodiment, the engine calling includes:
sending an engine calling request carrying a program identifier of the subprogram to a subprogram service platform; the subprogram service platform is a platform used for subscribing and issuing a form rendering engine provided for a subprogram;
and the subprogram service platform responds to the engine calling request, detects whether the subprogram carries out the engine subscription to the form rendering engine or not based on the program identification, and returns the form rendering engine to the subprogram if the subprogram carries out the engine subscription to the form rendering engine.
Optionally, the engine subscription includes: opening the access authority of the form rendering engine to the subprogram according to a subscription request submitted by a provider of the subprogram, and adding the subprogram to a subscription list of the form rendering engine; and after the engine subscription is finished, carrying out engine call initialization of the form rendering engine in the code fragment of the subprogram.
It should be noted that the interface call of the form interface corresponding to the form and the engine call of the form rendering engine may be performed in a serial manner, for example, according to the response time of the interface call and the engine call, if the response time of the interface call is longer than the response time of the engine call, the interface call is performed first, and then the engine call is performed; otherwise, if the response time of the engine call is longer than that of the interface call, the engine call is carried out firstly, and then the interface call is carried out. In addition, the interface call of the form interface corresponding to the form and the engine call of the form rendering engine can be executed in a parallel mode, for example, the interface call and the engine call are respectively performed through two processes, so that the time consumption of the call process is reduced, and the response timeliness of the form page of the access subprogram is further improved.
And step S104, receiving the form configuration data returned by the interface call, and inputting the form configuration data into the form rendering engine returned by the engine call to perform form rendering processing.
After the interface calling of the form interface corresponding to the form is triggered, receiving the form configuration data returned by the interface calling, and after the engine calling of the form rendering engine is triggered, receiving the form rendering engine returned by the engine calling, specifically, the form configuration data is returned by the server in response to the interface calling, and the form rendering engine is returned by the subprogram service platform in response to the engine calling; and on the basis of returning the form configuration data and the form rendering engine, inputting the returned form configuration data into the rendering engine for form rendering processing, specifically, in the processing process, the form processing engine analyzes the form configuration data and generates the form page based on the analysis result.
And step S106, displaying the form page obtained by the form rendering processing in the subprogram.
As described above, the form rendering engine is provided by the subroutine service platform, and the subroutine needs to make an engine subscription of the form rendering engine in advance before using the form rendering engine provided by the subroutine service platform, and can perform the form rendering processing by using the form rendering engine through the engine call in the subroutine access process when the engine subscription is completed. Optionally, the subprogram service platform is provided by an application provider of a host application of the subprogram, and the host application runs in the terminal device.
Alternatively, the subprogram service platform may be provided by a provider of a host container of the subprogram, where the host container runs on an IoT device, and the subprogram runs on the IoT device based on the host container. The service container refers to a runtime framework or runtime engine for loading and running the subprogram on the IoT device, and the IoT device can access the subprogram by installing the service container on the IoT device or configuring the service container on a device client installed on the IoT device. The service container is used as a light-weight container, so that the occupation of the operation resources of the IoT equipment is reduced, the occupation of the operation resources of the IoT equipment is reduced under the condition that the operation resources of the IoT equipment are limited, and the improvement of the operation efficiency of the IoT equipment is facilitated. The IoT (Internet of things) device, including but not limited to at least one of: the car machine terminal of vehicle installation, the external terminal equipment of vehicle, intelligent audio amplifier, unmanned machine of selling, independently the radio, interactive advertising screen, POS equipment to and intelligent household electrical appliances products such as intelligent TV, intelligent refrigerator.
In practical applications, the performance of the device in many scenarios is limited by the usage scenario and the cost of the device, this is especially true for IoT devices, in which case, to reduce the occupation of IoT device's operating resources by form rendering, the form rendering engine may also be sent to the server for storage after the completion of its engine subscription as described above, after the trigger interface call and the engine call, the server reads the stored form configuration data of the form corresponding to the form interface, and on the basis of detecting that the subprogram called by the initiating engine completes the engine subscription and the form rendering engine is stored in the server, the read form configuration data is input into the stored form rendering engine for form rendering processing, and returning the form page obtained by the form rendering processing to the subroutine to be displayed in the subroutine.
The following takes an application of the form processing method applied to the subprogram provided in this embodiment in a terminal device scenario as an example, and further describes the form processing method applied to the subprogram provided in this embodiment with reference to fig. 2.
Referring to fig. 2, a developer of a subprogram accesses a visual editing interface of a form editor in advance, selects a form component based on the visual editing interface of the form editor, edits the form component and inputs configuration data, and after the developer of the subprogram submits form editing, the form editor generates form configuration data based on the form component selected by the developer and the configuration data input by the edited form component, stores the form configuration data in a server of the subprogram, and generates a form interface based on the generated form configuration data; and the developer of the subprogram subscribes an engine of a form rendering engine aiming at the subprogram in the subprogram service platform;
after the form interface is generated, the developer of the subroutine performs development configuration of interface call initialization of the form interface in the code fragment of the subroutine, and performs development configuration of engine call initialization of the form rendering engine in the code fragment of the subroutine.
In the process that a user accesses the subprogram which is developed and configured by a developer in a host application operated by the terminal equipment, if the access to the form page of the subprogram is performed, the following operations are executed:
(1) triggering interface calling of a form interface corresponding to a form in a form page and engine calling of a form rendering engine;
(2) receiving the form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine to call the returned form rendering engine to perform form rendering processing;
(3) and displaying the form page obtained by the form rendering processing in the subprogram.
The form processing method applied to the subprogram provided by the present embodiment is further described below by taking an application of the form processing method applied to the subprogram in an IoT device scenario as an example.
A developer of the subprogram accesses a visual editing interface of the form editor in advance, selects a form component based on the visual editing interface of the form editor, edits the form component and inputs configuration data, and generates form configuration data to be stored in a server of the subprogram and generates a form interface based on the generated form configuration data after the developer of the subprogram submits the form edition and the form editor inputs the configuration data according to the form component selected by the developer and the edited form component; and the developer of the subprogram subscribes an engine of the form rendering engine aiming at the subprogram service platform;
in the process that a user accesses the subprogram which is developed and configured by a developer in a host container operated by an IoT device, if the user accesses a form page of the subprogram, the following operations are executed:
(1) triggering interface calling of a form interface corresponding to a form in a form page and engine calling of a form rendering engine;
(2) the subprogram service platform responds to the engine call to send the form rendering engine to the subprogram server, the subprogram server responds to the interface call to read form configuration data of a form corresponding to the form interface, the form configuration data is input into the form rendering engine which calls the sent form rendering engine to perform form rendering processing to obtain a form page, and the obtained form page is sent to the subprogram to be displayed in the subprogram to perform the display of the form page.
Alternatively, the first and second electrodes may be,
a developer of the subprogram accesses a visual editing interface of the form editor in advance, selects a form component based on the visual editing interface of the form editor, edits the form component and inputs configuration data, and generates form configuration data to be stored in a server of the subprogram and generates a form interface based on the generated form configuration data after the developer of the subprogram submits the form edition and the form editor inputs the configuration data according to the form component selected by the developer and the edited form component; and a subprogram developer performs engine subscription of the form rendering engine on the subprogram service platform aiming at the subprogram, and after the engine subscription is completed, the subprogram service platform sends the form rendering engine to a subprogram server for storage and records the engine subscription record of the subprogram;
in the process that a user accesses the subprogram which is developed and configured by a developer in a host application operated by an IoT device, if the user accesses a form page of the subprogram, the following operations are executed:
(1) triggering interface calling of a form interface corresponding to a form in a form page and engine calling of a form rendering engine;
(2) and the server of the subprogram responds to the interface call to read the form configuration data of the form corresponding to the form interface, responds to the engine call to detect whether the subprogram carries out engine subscription to the form rendering engine (namely, whether an engine subscription record of the subprogram exists), if so, inputs the form configuration data into the form rendering engine to carry out form rendering processing to obtain a form page, and sends the obtained form page to the subprogram to display the form page in the subprogram.
It should be added that the two implementation manners of the form processing method applied to the subprogram in the IoT device scenario provided above may also be applied to the terminal device, which is only required by referring to the two implementation manners of the form processing method applied to the subprogram in the IoT device scenario provided above, and this embodiment is not described in detail here.
An embodiment of a form processing apparatus applied to a subroutine provided in this specification is as follows:
in the foregoing embodiment, a form processing method applied to a sub program is provided, and correspondingly, a form processing apparatus applied to a sub program and running on a terminal device is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 3, a schematic diagram of a form processing apparatus applied to a subroutine according to this embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
The embodiment provides a form processing apparatus applied to a subroutine, the apparatus including:
the calling module 302 is configured to trigger interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine under the condition that an access instruction of the form page of the subprogram is detected;
the form rendering module 304 is configured to receive the form configuration data returned by the interface call, and input the form configuration data into the form rendering engine returned by the engine call to perform form rendering processing;
a form page presentation module 306 configured to present, within the subroutine, a form page obtained by the form rendering process.
An embodiment of a form processing apparatus applied to a subroutine provided in this specification is as follows:
corresponding to the above-described form processing method applied to a sub program, based on the same technical concept, one or more embodiments of the present specification further provide a terminal device, where the terminal device is configured to execute the above-described form processing method applied to a sub program, and fig. 4 is a schematic structural diagram of a form processing device applied to a sub program provided in one or more embodiments of the present specification.
The form processing device applied to the subprogram provided by the embodiment comprises:
as shown in fig. 4, the form processing device applied to the subprogram may have a relatively large difference due to different configurations or performances, and may include one or more processors 401 and a memory 402, where one or more stored applications or data may be stored in the memory 402. Wherein memory 402 may be transient or persistent. The application program stored in memory 402 may include one or more modules (not shown), each of which may include a series of computer-executable instructions that are applied in the form processing device of the subroutine. Still further, the processor 401 may be configured to communicate with the memory 402 to execute a series of computer-executable instructions in the memory 402 on a form processing device that is applied to the subroutines. The form processing apparatus applied to the subroutine may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input/output interfaces 405, one or more keyboards 406, etc.
In one particular embodiment, a form processing apparatus for a sub-program comprises a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may comprise one or more modules, and each module may comprise a series of computer-executable instructions for the form processing apparatus for the sub-program, and the one or more programs configured for execution by the one or more processors comprise computer-executable instructions for:
under the condition that an access instruction of a form page of a subprogram is detected, triggering interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine;
receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing;
and displaying the form page obtained by the form rendering processing in the subprogram.
An embodiment of a storage medium provided in this specification is as follows:
on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the form processing method applied to the subprogram described above.
The storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed by the processor, the following processes are implemented:
under the condition that an access instruction of a form page of a subprogram is detected, triggering interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine;
receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing;
and displaying the form page obtained by the form rendering processing in the subprogram.
It should be noted that the embodiment of the storage medium in this specification and the embodiment of the form processing method applied to the sub program in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described again.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical blocks. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The description has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.
Claims (12)
1. A form processing method applied to a subprogram, comprising the following steps:
under the condition that an access instruction of a form page of a subprogram is detected, triggering interface calling of a form interface corresponding to the form in the form page and engine calling of a form rendering engine;
receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing;
and displaying the form page obtained by the form rendering processing in the subprogram.
2. The form processing method applied to the subprogram according to claim 1, wherein the form interface is generated by:
generating the form configuration data according to the selected form component and the configuration data input by editing the form component;
and storing the generated form configuration data, and generating the form interface based on the form configuration data.
3. The form processing method applied to the subprogram according to claim 2, wherein the form interface is generated and then sent to the provider of the subprogram, so as to initialize the interface call of the form interface in the code fragment of the subprogram.
4. The form processing method applied to the subprogram of claim 2, wherein the form configuration data is stored in a server, and the server reads the form configuration data of the form corresponding to the form interface and returns the form configuration data to the subprogram in response to the interface call.
5. The form processing method applied to the subprogram according to claim 2, wherein the selection and editing of the form components are performed based on a visual editing interface of a form editor;
the form component is selected by the provider of the subprogram in the visual editing interface, and the configuration data is edited and input by the provider of the subprogram.
6. The form processing method applied to a subroutine according to claim 1, said engine call comprising:
sending an engine calling request carrying a program identifier of the subprogram to a subprogram service platform;
and the subprogram service platform responds to the engine calling request, detects whether the subprogram carries out the engine subscription to the form rendering engine or not based on the program identification, and returns the form rendering engine to the subprogram if the subprogram carries out the engine subscription to the form rendering engine.
7. The form processing method applied to the subroutine of claim 6, said engine subscribing comprising:
opening the access authority of the form rendering engine to the subprogram according to a subscription request submitted by a provider of the subprogram, and adding the subprogram to a subscription list of the form rendering engine; and after the engine subscription is finished, carrying out engine call initialization of the form rendering engine in the code fragment of the subprogram.
8. The form processing method applied to the subroutine program according to claim 6, wherein the subroutine service platform is provided by an application provider of a host application of the subroutine program, the host application being run on the terminal device.
9. The form processing method applied to the subprogram of claim 6, wherein the subprogram service platform is provided by a provider of a host container of the subprogram, the host container is run on an IoT device, and the subprogram is run on the IoT device based on the host container.
10. A form processing apparatus applied to a subroutine, comprising:
the calling module is configured to trigger interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine under the condition that an access instruction of the form page of the subprogram is detected;
the form rendering module is configured to receive form configuration data returned by the interface call, and input the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing;
and the form page display module is configured to display the form page obtained by the form rendering processing in the subprogram.
11. A form processing apparatus applied to a subroutine, comprising:
a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to:
under the condition that an access instruction of a form page of a subprogram is detected, triggering interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine;
receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing;
and displaying the form page obtained by the form rendering processing in the subprogram.
12. A storage medium storing computer-executable instructions that when executed by a processor implement the following:
under the condition that an access instruction of a form page of a subprogram is detected, triggering interface calling of a form interface corresponding to a form in the form page and engine calling of a form rendering engine;
receiving form configuration data returned by the interface call, and inputting the form configuration data into a form rendering engine returned by the engine call to perform form rendering processing;
and displaying the form page obtained by the form rendering processing in the subprogram.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210509993.XA CN114968457B (en) | 2022-05-11 | 2022-05-11 | Form processing method and device applied to subprogram |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210509993.XA CN114968457B (en) | 2022-05-11 | 2022-05-11 | Form processing method and device applied to subprogram |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114968457A true CN114968457A (en) | 2022-08-30 |
| CN114968457B CN114968457B (en) | 2024-05-03 |
Family
ID=82981558
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210509993.XA Active CN114968457B (en) | 2022-05-11 | 2022-05-11 | Form processing method and device applied to subprogram |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114968457B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080201453A1 (en) * | 2007-02-19 | 2008-08-21 | Ondeego, Inc. | Methods and system to create applications and distribute applications to a remote device |
| US20090319921A1 (en) * | 2008-06-18 | 2009-12-24 | Microsoft Corporation | Implementing custom user interface forms in a personal information manager |
| CN102135990A (en) * | 2011-03-11 | 2011-07-27 | 北京神舟航天软件技术有限公司 | Java server page (JSP) template-based intelligent table system capable of being defined freely and generating method |
| CN103377038A (en) * | 2012-04-11 | 2013-10-30 | 怡丰联合（北京）科技有限责任公司 | User-defined form description and form analysis method |
| US20150242503A1 (en) * | 2014-02-26 | 2015-08-27 | International Business Machines Corporation | Operating a portal environment |
| CN105069032A (en) * | 2015-07-20 | 2015-11-18 | 东南大学 | Filtering expression and rendering engine based method for automatically monitoring update of dynamic webpage |
| CN111158818A (en) * | 2019-12-24 | 2020-05-15 | 中国建设银行股份有限公司 | Page rendering method and device |
| CN112861057A (en) * | 2021-02-10 | 2021-05-28 | 北京百度网讯科技有限公司 | Page rendering method, device and equipment based on small program and storage medium |
-
2022
- 2022-05-11 CN CN202210509993.XA patent/CN114968457B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080201453A1 (en) * | 2007-02-19 | 2008-08-21 | Ondeego, Inc. | Methods and system to create applications and distribute applications to a remote device |
| US20090319921A1 (en) * | 2008-06-18 | 2009-12-24 | Microsoft Corporation | Implementing custom user interface forms in a personal information manager |
| CN102135990A (en) * | 2011-03-11 | 2011-07-27 | 北京神舟航天软件技术有限公司 | Java server page (JSP) template-based intelligent table system capable of being defined freely and generating method |
| CN103377038A (en) * | 2012-04-11 | 2013-10-30 | 怡丰联合（北京）科技有限责任公司 | User-defined form description and form analysis method |
| US20150242503A1 (en) * | 2014-02-26 | 2015-08-27 | International Business Machines Corporation | Operating a portal environment |
| CN105069032A (en) * | 2015-07-20 | 2015-11-18 | 东南大学 | Filtering expression and rendering engine based method for automatically monitoring update of dynamic webpage |
| CN111158818A (en) * | 2019-12-24 | 2020-05-15 | 中国建设银行股份有限公司 | Page rendering method and device |
| CN112861057A (en) * | 2021-02-10 | 2021-05-28 | 北京百度网讯科技有限公司 | Page rendering method, device and equipment based on small program and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 李维佳;汪洪江;: "基于ASP.NET的Web表单自动生成引擎", 计算机与网络, no. 17, 12 September 2015 (2015-09-12) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114968457B (en) | 2024-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107038042B (en) | Service execution method and device | |
| JP2019520624A (en) | Page component dynamic layout | |
| CN108924029B (en) | Method and device for sending customer service data | |
| CN107092475B (en) | Calling method and device of interactive control | |
| CN110496395B (en) | Component operation method, system and equipment for illusion engine | |
| WO2021197140A1 (en) | Generation of applet file package | |
| CN107479868B (en) | Interface loading method, device and equipment | |
| CN111400681B (en) | Data authority processing method, device and equipment | |
| CN114064024A (en) | Method, apparatus, device, storage medium, and program product for developing micro-application | |
| CN112597013A (en) | Online development and debugging method and device | |
| CN111796821A (en) | Page updating method and device | |
| CN111861454B (en) | Method and device for displaying unique identifier of digital object | |
| CN111581069A (en) | Data processing method and device | |
| CN114547569A (en) | Account login processing method and device | |
| CN114546639A (en) | Service call processing method and device | |
| CN116719457A (en) | Information display method, device and equipment | |
| CN109284222B (en) | Software unit, project testing method, device and equipment in data processing system | |
| CN113360385A (en) | Test method, device, equipment and medium | |
| WO2023216872A1 (en) | Event processing method and apparatus applied to iot device | |
| CN112035117A (en) | Page display system, method and device | |
| CN111881393A (en) | Page rendering method, device, medium and electronic equipment | |
| CN111538667A (en) | Page testing method and device | |
| CN114968457B (en) | Form processing method and device applied to subprogram | |
| CN114546843A (en) | Program debugging processing method and device | |
| CN114637568A (en) | Equipment split screen adaptation processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |