CN114968457B - Form processing method and device applied to subprogram - Google Patents
Form processing method and device applied to subprogram Download PDFInfo
- Publication number
- CN114968457B CN114968457B CN202210509993.XA CN202210509993A CN114968457B CN 114968457 B CN114968457 B CN 114968457B CN 202210509993 A CN202210509993 A CN 202210509993A CN 114968457 B CN114968457 B CN 114968457B
- Authority
- CN
- China
- Prior art keywords
- engine
- subprogram
- call
- interface
- subroutine
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the specification provides a form processing method and a form processing device applied to a subroutine, wherein the form processing method applied to the subroutine comprises the following steps: triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine under the condition that an access instruction of the form page of a subprogram is detected; 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 subroutine.
Description
Technical Field
The present document relates to the field of data processing technologies, and in particular, to a form processing method and apparatus applied to a subroutine.
Background
With the development of internet technology and the popularization of mobile terminals, more and more services start to extend to online scenes, application platform software capable of carrying a plurality of application subroutines appears, and the situation that a user installs different types of application programs on the mobile terminal is avoided, and the application subroutines carried in the application platform software are used for realizing service handling, and meanwhile, the application subroutines can fully utilize sufficient user flow of the application platform software, so that assistance is provided for service promotion of the application subroutines.
Disclosure of Invention
One or more embodiments of the present specification provide a form processing method applied to a subroutine, including: and triggering the interface call of the form interface corresponding to the form in the form page and the engine call of the form rendering engine under the condition that the access instruction of the form page of the subprogram is detected. And receiving the 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 subroutine.
One or more embodiments of the present specification provide a form processing apparatus applied to a subroutine, including: and the calling module is configured to trigger the interface call of the form interface corresponding to the form in the form page and the engine call of the form rendering engine under the condition that the 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, input the form configuration data into a form rendering engine returned by the engine call and conduct form rendering processing. And the form page display module is configured to display the form page obtained by the form rendering processing in the subroutine.
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 triggering the interface call of the form interface corresponding to the form in the form page and the engine call of the form rendering engine under the condition that the access instruction of the form page of the subprogram is detected. And receiving the 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 subroutine.
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 triggering the interface call of the form interface corresponding to the form in the form page and the engine call of the form rendering engine under the condition that the access instruction of the form page of the subprogram is detected. And receiving the 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 subroutine.
Drawings
For a clearer description of one or more embodiments of the present description or of the solutions of the prior art, the drawings that are needed in the description of the embodiments or of the prior art will be briefly described below, it being obvious that the drawings in the description that follow are only some of the embodiments described in the present description, from which other drawings can be obtained, without inventive faculty, for a person skilled in the art;
FIG. 1 is a flow diagram of a form processing method for use with a subroutine in accordance with one or more embodiments of the present disclosure;
fig. 2 is a schematic diagram of a form processing procedure applied to a subroutine in a terminal device scenario provided in one or more embodiments of the present disclosure;
FIG. 3 is a schematic diagram of a form handling device for use with a subroutine according to one or more embodiments of the present disclosure;
Fig. 4 is a schematic structural diagram of a form processing apparatus applied to a subroutine according to one or more embodiments of the present disclosure.
Detailed Description
In order to enable a person skilled in the art to better understand the technical solutions in one or more embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one or more embodiments of the present disclosure without inventive effort, are intended to be within the scope of the present disclosure.
The present specification provides an embodiment of a form processing method applied to a subroutine:
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 acquired by calling the corresponding form interface, the form rendering engine for performing form rendering is acquired by calling the engine, then the form configuration data acquired by calling the form interface is input into the form rendering engine for performing form rendering processing to acquire the form page, the form configuration data is acquired by calling the form interface, the development difficulty and the development cost of form development for the subprogram are reduced, and meanwhile, the probability of failure of the subprogram in the form using process is also reduced, so that the follow-up maintenance work of the subprogram for using the form is reduced, and convenience is provided for developers of the subprogram while the stability of the subprogram service is ensured.
Referring to fig. 1, the form processing method applied to the subroutine provided in the present embodiment specifically includes steps S102 to S106.
Step S102, under the condition that an access instruction of a form page of a subprogram is detected, triggering an interface call of a form interface corresponding to a form in the form page and an engine call of a form rendering engine.
The subroutine in this embodiment refers to a program function module or an application component that is installed in an application or a client, or a subroutine (applet) in an application or an application component that is installed by the application or the client. From a service perspective, the subroutine has the capability of independently providing self-closing services, such as running a subroutine with service subscription, subscription message push, self-closing capabilities within a payment application platform.
The form page of the subroutine refers to a page in which a form is configured in the page of the subroutine. The form interface is an interface for acquiring form configuration data of the forms in the form page, the form interface has a one-to-one correspondence with the form interface, and the form configuration data of the corresponding forms can be acquired by calling the form interface, that is, if a plurality of forms exist in the form page, the form interface corresponding to the forms needs to be called respectively to acquire the form configuration data of the 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 the process of accessing a subroutine, and the form rendering engine can be in a plug-in form or a component form (such as an NPM component); in addition, in a scenario specific for data collection through a form, the form rendering engine may also be integrated in SDK (Software Development Kit) form with a client of an application or device specific for data collection.
In the implementation, in the process of accessing the subprogram, the access of the form page of the subprogram is detected, the interface call of the form interface corresponding to the form in the form page is triggered under the condition that the access instruction of the form page of the subprogram is detected, the form configuration data of the form in the form page is obtained in an interface call mode, and the engine call of the form rendering engine is triggered under the condition that the access instruction is detected, so that the form rendering engine is obtained in an engine call mode.
In practical application, a certain learning cost is required for form development aiming at the subprogram, and development cost is also required, in order to reduce the form development difficulty aiming at the subprogram, in an optional implementation manner provided by 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 by adopting the following manner: generating form configuration data according to the selected form components and configuration data input by editing the form components; and storing the generated form configuration data, and generating the form interface based on the form configuration data.
Optionally, the form interface is issued to the provider of the subroutine after being generated, so as to perform the interface call initialization of the form interface in the code segment of the subroutine.
The form component is a form element required in the form development process of the subprogram, a developer only needs to select the corresponding form element, does not need to independently develop the form element for forming the form, and develops the selected form element in a configuration mode, so that the learning cost and the development difficulty in the form development process of the subprogram are greatly reduced. The form configuration data includes styles, attributes, and/or source data associated with the subroutine service for the form.
In order to further reduce the learning cost and development difficulty of form development aiming at the subprogram, the embodiment assists a developer to develop the form aiming at the subprogram by providing a visual form development environment, and the selection and editing of the form component are optional and are carried out based on a visual editing interface of a form editor; the form component is selected by the provider of the subprogram at the visual editing interface, and the configuration data is edited and input by the provider of the subprogram.
On the basis, in order to ensure the form development quality of a developer and reduce the workload of subsequent form maintenance, a preview access control can be configured in a form editor, the developer can check the page actually operated 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 form editor performs rendering processing on the currently developed form by a form rendering component configured by the form editor or calling the form rendering engine, so that the developer is helped to intuitively perceive the progress and condition 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 can be stored in a server of the subprogram, so that the access instantaneity in the actual subprogram access process is ensured, 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 a form corresponding to the form interface and returns the form configuration data to the subprogram.
In this embodiment, the volume of the code segment of the subroutine is often small, and the rendering of the form page needs to rely on a specific tool (form rendering engine), and the volume of the form rendering engine is far greater than the volume of the code segment of the subroutine, so, in order to ensure that the access of the subroutine is not affected, the form rendering engine required for performing the form rendering is remotely acquired by an engine call mode, and in an alternative implementation provided in this embodiment, the engine call includes:
An engine call request carrying a program identifier of the subprogram is sent to a subprogram service platform; the subprogram service platform refers to a platform for subscribing and issuing a form rendering engine provided for a subprogram;
and the subprogram service platform responds to the engine call request, detects whether the subprogram performs engine subscription of the form rendering engine or not based on the program identification, and if yes, returns the form rendering engine to the subprogram.
Optionally, the engine subscribes to, including: according to a subscription request submitted by a provider of the subprogram, opening the access right of the form rendering engine to the subprogram, and adding the subprogram to a subscription list of the form rendering engine; and after the engine subscription is completed, performing engine call initialization of the form rendering engine in the code fragments 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 executed in a serial manner, for example, according to the response time length of the interface call and the engine call, if the response time length of the interface call is greater than the response time length 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 the response time of the interface call, the engine call is performed first, and then the interface call is performed. 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 carried out through two processes, so that the time consumption of the call process is reduced, and the response timeliness of accessing the form page of the subroutine is further improved.
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 the form rendering processing.
After the interface call of the form interface corresponding to the form is triggered, receiving the form configuration data returned by the interface call, and after the engine call of the form rendering engine is triggered, receiving the form rendering engine returned by the engine call, specifically, the form configuration data is returned by a server in response to the interface call, and the form rendering engine is returned by a subroutine service platform in response to the engine call; and inputting the returned form configuration data into the rendering engine to perform form rendering processing on the basis of returning the form configuration data and the form rendering engine, wherein the form processing engine analyzes the form configuration data and renders and generates the form page based on an analysis result in the processing process.
And step S106, displaying the form page obtained by the form rendering processing in the subroutine.
As described above, the form rendering engine is provided by the subroutine service platform, and before the subroutine uses the form rendering engine provided by the subroutine service platform, the subroutine needs to make an engine subscription of the form rendering engine in advance, and in the case of completing the engine subscription, the form rendering engine can be used for performing the form rendering process by engine call in the process of accessing the subroutine. Optionally, the subroutine service platform is provided by an application provider of a host application of the subroutine, and the host application is run on the terminal device.
Or the subroutine service platform may also be provided by a provider of a host container of a subroutine, the host container running on an IoT device, the subroutine running on the IoT device based on the host container. The service container refers to a running framework or a running engine for loading and running the subprogram on the IoT device, and the IoT device can realize the access to 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 lightweight container, so that the occupation of the operation resources of the IoT device is reduced, and the operation efficiency of the IoT device is improved under the condition that the operation resources of the IoT device are limited. The IoT (Internet of Things) apparatus includes, but is not limited to, at least one of: the intelligent mobile phone comprises a car terminal, a car external terminal device, an intelligent sound box, an unmanned vending machine, an autonomous radio, an interactive advertisement screen, POS equipment, intelligent household appliances such as an intelligent television and an intelligent refrigerator.
In practical applications, the performance of the device in many scenes is limited by the use scenes and the cost of the device, especially for IoT devices, in this case, in order to reduce the occupation of the running resources of the IoT devices by the form rendering, after the engine subscription of the form rendering engine is completed, the form rendering engine may be sent to the server to store, after the interface call and the engine call are triggered, the server reads the form configuration data of the form corresponding to the stored form interface, and after detecting that the subroutine initiating the engine call completes the engine subscription and stores the form rendering engine in the server, the read form configuration data is input into the stored form rendering engine to perform the form rendering process, and the form page obtained by the form rendering process is returned to the subroutine to be displayed in the subroutine.
The following describes, with reference to fig. 2, a form processing method applied to a subroutine according to the present embodiment, by taking an application of the form processing method applied to a subroutine in a terminal device scenario as an example.
Referring to fig. 2, a developer of a sub program 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, after the developer of the sub program submits the form edit, the form editor generates form configuration data based on the form component selected by the developer and the configuration data input by the form component edited, and stores the form configuration data to a server of the sub program, and generates a form interface based on the generated form configuration data; and performing engine subscription of the form rendering engine on the subroutine by a developer of the subroutine in a subroutine service platform;
After generating the form interface, a developer of the subroutine performs development configuration of interface call initialization of the form interface in a code segment of the subroutine, and performs development configuration of engine call initialization of the form rendering engine in the code segment of the subroutine.
In the process that a user accesses a sub-program which is developed and configured by a developer in a host application running by the terminal equipment, if the user accesses a form page of the sub-program, the following operation is executed:
(1) Triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine;
(2) 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;
(3) Form pages obtained by the form rendering process are presented within the subroutine.
The following describes a form processing method applied to a subroutine according to the present embodiment, taking an application of the form processing method applied to a subroutine in an IoT device scenario as an example.
The method comprises the steps that a developer of a subprogram accesses a visual editing interface of a form editor in advance, a form component is selected based on the visual editing interface of the form editor, the form component is edited and configuration data is input, after the developer of the subprogram submits the 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 form component is edited, the form configuration data is stored in a server of the subprogram, and a form interface is generated based on the generated form configuration data; and performing engine subscription of the form rendering engine on the subroutine by a developer of the subroutine in a subroutine service platform;
In the process that a user accesses a sub-program 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 sub-program, the following operations are executed:
(1) Triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine;
(2) The method comprises the steps that a sub-program service platform responds to engine call and sends a form rendering engine to a sub-program server, the sub-program server responds to interface call and reads form configuration data of a form corresponding to a form interface, the form configuration data is input into the form rendering engine sent by the engine call to conduct form rendering processing to obtain a form page, and the obtained form page is sent to the sub-program to be displayed in the sub-program to display the form page.
Or alternatively
The method comprises the steps that a developer of a subprogram accesses a visual editing interface of a form editor in advance, a form component is selected based on the visual editing interface of the form editor, the form component is edited and configuration data is input, after the developer of the subprogram submits the 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 form component is edited, the form configuration data is stored in a server of the subprogram, and a form interface is generated based on the generated form configuration data; and the developer of the subprogram carries out 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 server of the subprogram for storage and records the engine subscription record of the subprogram;
In the process that a user accesses a sub-program which is developed and configured by a developer in a host application running on an IoT device, if the user accesses a form page of the sub-program, the following operations are executed:
(1) Triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine;
(2) 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 performs engine subscription of the form rendering engine (namely, whether the engine subscription record of the subprogram exists) or not, if so, inputs the form configuration data into the form rendering engine to perform 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 subroutine of the IoT device scene provided above may be applied to the terminal device as well, and refer to the two implementation manners of the form processing method applied to the subroutine of the IoT device scene provided above, which are not described in detail herein.
An embodiment of a form processing apparatus applied to a subroutine provided in the present specification is as follows:
In the above-described embodiments, a form processing method applied to a subroutine is provided, and a form processing apparatus applied to a subroutine and running in a terminal device is provided correspondingly, and 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 the present embodiment is shown.
Since the apparatus embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions should be referred to the corresponding descriptions of the method embodiments provided above. The device embodiments described below are merely illustrative.
The present embodiment provides a form processing apparatus applied to a subroutine, the apparatus including:
The calling module 302 is configured to trigger the interface call of the form interface corresponding to the form in the form page and the engine call of the form rendering engine under the condition that the access instruction of the form page of the subprogram is detected;
The form rendering module 304 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 a form page display module 306 configured to display the form page obtained by the form rendering process in the subroutine.
An embodiment of a form processing apparatus applied to a subroutine provided in the present specification is as follows:
In response to the above description of a form processing method applied to a subroutine, one or more embodiments of the present disclosure further provide a terminal device for executing the form processing method applied to a subroutine, and 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 disclosure.
The form processing device applied to the subroutine provided in the embodiment includes:
As shown in fig. 4, the form handling device applied to the subroutine may have a relatively large difference due to different configurations or performances, and may include one or more processors 401 and a memory 402, and the memory 402 may store one or more stored applications or data. Wherein the memory 402 may be transient storage or persistent storage. The application programs stored in memory 402 may include one or more modules (not shown in the figures), each of which may include a series of computer-executable instructions applied to the form handling device of the subroutine. Still further, the processor 401 may be arranged to communicate with the memory 402 to execute a series of computer executable instructions in the memory 402 on a form handling device applied to the subroutine. The form handling device applied to the subroutines 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, and the like.
In one particular embodiment, a form handling device for application to a subroutine includes 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 include one or more modules, and each module may include a series of computer executable instructions in the form handling device for the subroutine, and configured to be executed by one or more processors, the one or more programs including computer executable instructions for:
triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine under the condition that an access instruction of the form page of a subprogram is detected;
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 subroutine.
An embodiment of a storage medium provided in the present specification is as follows:
corresponding to a form processing method applied to the subroutine described above, one or more embodiments of the present specification also provide a storage medium based on the same technical idea.
The storage medium provided in this embodiment is configured to store computer executable instructions that, when executed by a processor, implement the following flow:
triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine under the condition that an access instruction of the form page of a subprogram is detected;
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 subroutine.
It should be noted that, the embodiments of the storage medium in this specification and the embodiments of the form processing method applied to the subroutine in this specification are based on the same inventive concept, so that the specific implementation of this embodiment may refer to the implementation of the corresponding method, and the repetition is omitted.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can 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 are also possible or may be advantageous.
In the 30 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable GATE ARRAY, FPGA)) is an integrated circuit whose logic functions are determined by user programming of the device. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented with "logic compiler (logic compiler)" software, which is similar to the software compiler used in program development and writing, and the original code before being compiled is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but HDL is not just one, but a plurality of kinds, such as ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language), and VHDL (Very-High-SPEED INTEGRATED Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of 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, application SPECIFIC INTEGRATED Circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, 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 functionally divided into various units, respectively. Of course, the functions of each unit may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present specification.
One skilled in the relevant 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 present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. 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 one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
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 storage media for a computer 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 Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
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 one … …" 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 specification 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.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing description is by way of example only and is not intended to limit the present disclosure. Various modifications and changes may occur to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. that fall within the spirit and principles of the present document are intended to be included within the scope of the claims of the present document.
Claims (9)
1. A form processing method applied to a subroutine, comprising:
Triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine under the condition that an access instruction of the form page of a subprogram is detected; the form interface is generated according to the selected form component and the configuration data input by editing the form component, and the form interface performs interface call initialization in the code segment of the subprogram through a provider; the form rendering engine sends the form rendering engine after the engine subscription is completed for the subprogram by a subprogram service platform, and performs engine call initialization in the code segment; the engine subscription is performed by opening the access rights of the form rendering engine to the subprogram according to a subscription request submitted by the provider and adding the subprogram to a subscription list of the 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 subroutine.
2. The form processing method applied to a subroutine according to claim 1, 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 to the subroutine in response to the interface call.
3. The form processing method applied to the subroutine according to claim 1, wherein the selection and editing of the form components is performed based on a visual editing interface of a form editor;
the form component is selected by the provider of the subprogram at the visual editing interface, and the configuration data is edited and input by the provider of the subprogram.
4. The form processing method applied to a subroutine of claim 1, said engine call comprising:
sending an engine call request carrying a program identifier of the subprogram to the subprogram service platform;
and the subprogram service platform responds to the engine call request, detects whether the subprogram performs engine subscription of the form rendering engine or not based on the program identification, and if yes, returns the form rendering engine to the subprogram.
5. The form processing method applied to a subroutine according to claim 4, wherein the subroutine service platform is provided by an application provider of a host application of the subroutine, the host application being run on a terminal device.
6. The form processing method applied to a subroutine of claim 4, the subroutine service platform being provided by a provider of a host container of a subroutine, the host container running on an IoT device, the subroutine running on the IoT device based on the host container.
7. A form processing apparatus for use in a subroutine, comprising:
The calling module is configured to trigger the interface call of the form interface corresponding to the form in the form page and the engine call of the form rendering engine under the condition that the access instruction of the form page of the subprogram is detected; the form interface is generated according to the selected form component and the configuration data input by editing the form component, and the form interface performs interface call initialization in the code segment of the subprogram through a provider; the form rendering engine sends the form rendering engine after the engine subscription is completed for the subprogram by a subprogram service platform, and performs engine call initialization in the code segment; the engine subscription is performed by opening the access rights of the form rendering engine to the subprogram according to a subscription request submitted by the provider and adding the subprogram to a subscription list of the form rendering engine;
the form rendering module is configured to receive form configuration data returned by the interface call, input the form configuration data into a form rendering engine returned by the engine call and conduct form rendering processing;
and the form page display module is configured to display the form page obtained by the form rendering processing in the subroutine.
8. A form handling device for use with a subroutine, comprising:
a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:
Triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine under the condition that an access instruction of the form page of a subprogram is detected; the form interface is generated according to the selected form component and the configuration data input by editing the form component, and the form interface performs interface call initialization in the code segment of the subprogram through a provider; the form rendering engine sends the form rendering engine after the engine subscription is completed for the subprogram by a subprogram service platform, and performs engine call initialization in the code segment; the engine subscription is performed by opening the access rights of the form rendering engine to the subprogram according to a subscription request submitted by the provider and adding the subprogram to a subscription list of the 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 subroutine.
9. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the following:
Triggering the interface call of a form interface corresponding to a form in a form page and the engine call of a form rendering engine under the condition that an access instruction of the form page of a subprogram is detected; the form interface is generated according to the selected form component and the configuration data input by editing the form component, and the form interface performs interface call initialization in the code segment of the subprogram through a provider; the form rendering engine sends the form rendering engine after the engine subscription is completed for the subprogram by a subprogram service platform, and performs engine call initialization in the code segment; the engine subscription is performed by opening the access rights of the form rendering engine to the subprogram according to a subscription request submitted by the provider and adding the subprogram to a subscription list of the 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 subroutine.
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 CN114968457A (en) | 2022-08-30 |
| CN114968457B true 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 (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9451009B2 (en) * | 2007-02-19 | 2016-09-20 | Appcentral, Inc. | Methods and system to create applications and distribute applications to a remote device |
| US9298684B2 (en) * | 2008-06-18 | 2016-03-29 | Microsoft Technology Licensing, Llc | Implementing custom user interface forms in a personal information manager |
| US10325001B2 (en) * | 2014-02-26 | 2019-06-18 | International Business Machines Corporation | Operating a portal environment |
-
2022
- 2022-05-11 CN CN202210509993.XA patent/CN114968457B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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表单自动生成引擎;李维佳;汪洪江;;计算机与网络;20150912(17);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114968457A (en) | 2022-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107038042B (en) | Service execution method and device | |
| CN111831387B (en) | Page processing method, device and equipment | |
| CN113259224B (en) | Method and device for sending customer service data | |
| CN111475142B (en) | Method, device and equipment for generating applet file package | |
| CN107092475B (en) | Calling method and device of interactive control | |
| CN111796821A (en) | Page updating method and device | |
| CN111400681B (en) | Data authority processing method, device and equipment | |
| CN114547569B (en) | Account login processing method and device | |
| CN112631679B (en) | Preloading method and device for micro-applications | |
| CN111783018B (en) | Page processing method, device and equipment | |
| CN110496395B (en) | Component operation method, system and equipment for illusion engine | |
| CN107479868B (en) | Interface loading method, device and device | |
| CN113079201B (en) | Information processing system, method, device and equipment | |
| CN113434063B (en) | An information display method, device and equipment | |
| CN111861454B (en) | Method and device for displaying unique identifier of digital object | |
| CN114661483B (en) | Subroutine synchronous processing method and device | |
| CN114546639B (en) | Service call processing method and device | |
| CN114201086B (en) | Information display method and device | |
| CN110704141A (en) | Page switching method and device and electronic equipment | |
| CN114968457B (en) | Form processing method and device applied to subprogram | |
| CN111210222B (en) | Data display and payment method, device, equipment and medium | |
| CN112698882A (en) | Page component loading method and device | |
| CN114637568B (en) | Split-screen adaptive processing method and device for equipment | |
| CN115941757A (en) | IROS robot-oriented management interaction method, equipment and medium | |
| CN115795201B (en) | Page setting and displaying method, device and equipment based on illusion engine |
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 | ||
| GR01 | Patent grant |