CN112114890A - Method, device and equipment for processing small program and storage medium - Google Patents
Method, device and equipment for processing small program and storage medium Download PDFInfo
- Publication number
- CN112114890A CN112114890A CN201910538843.XA CN201910538843A CN112114890A CN 112114890 A CN112114890 A CN 112114890A CN 201910538843 A CN201910538843 A CN 201910538843A CN 112114890 A CN112114890 A CN 112114890A
- Authority
- CN
- China
- Prior art keywords
- applet
- component
- instance
- party
- party component
- 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.)
- Pending
Links
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/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Abstract
The invention provides a method, a device, equipment and a storage medium for processing an applet; the method comprises the following steps: running the applet in the client; creating an instance corresponding to a third-party component of the applet by calling an entry file constructed corresponding to the applet; acquiring an event corresponding to the third-party component in the applet, and transmitting the event to an instance of the third-party component through a sub-component; and acquiring data generated by the third-party component instance corresponding to the event, and rendering the data through the applet rendering environment. By the method and the device, the processing of the third-party component in the running environment of the third-party component can be converted into the running of the subassembly, the decoupling between the development frameworks of the applet and the third-party component is realized, and various third-party components can be reused in the applet.
Description
Technical Field
The present invention relates to electrical digital data processing technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing an applet.
Background
A small program (Web Application), also called a small program, is a program that can be downloaded over a network and run directly in a browser environment, and because an installation process is saved with respect to a dedicated client, it is possible to flexibly expand and upgrade functions of the client.
The page of the applet realizes different functions by calling various components, and the related art provides a development framework of the components and a running environment of the components to provide the call of the components to the page of the applet to realize the corresponding functions of the components in the page.
Because the operating environment provided by the related technology is tightly coupled with the applet, the applet can normally operate only by integrally packaging the applet and the operating environment, and the applet and the component cannot be reused in the development process of different projects, so that the development efficiency is influenced.
Disclosure of Invention
Embodiments of the present invention provide an applet processing method, apparatus, device, and storage medium, which can decouple an operating environment of an applet and a third-party component to flexibly operate various third-party components in the applet.
The technical scheme of the embodiment of the invention is realized as follows:
the embodiment of the invention provides a small program processing method, which comprises the following steps:
running the applet in the client;
creating an instance corresponding to a third-party component of the applet by calling an entry file constructed corresponding to the applet;
acquiring an event corresponding to the third-party component in the applet, and transmitting the event to an instance of the third-party component through a sub-component of the applet;
and acquiring data generated by the third-party component instance corresponding to the event, and rendering the data through the applet rendering environment.
An embodiment of the present invention further provides an applet processing apparatus, including:
an operation unit for operating the applet in the client;
a creating unit configured to create an instance corresponding to a third-party component of the applet by calling an entry file constructed corresponding to the applet;
the acquisition unit is used for acquiring an event corresponding to the third-party component in the applet and transmitting the event to an instance of the third-party component through a sub-component;
and the rendering unit is used for acquiring data generated by the third-party component instance corresponding to the event and rendering the data through the applet rendering environment.
In the above scheme, the creating unit is further configured to obtain a virtual node corresponding to a custom component of the applet by calling an entry file of the custom component, and create an instance of the third-party component in an instance of the custom component according to the virtual node.
In the above scheme, the creating unit is further configured to create an instance of the sub-component in an instance of the parent component by using the page of the applet as a parent component and the custom component as a sub-component;
transferring an event to the parent component through an event interface of the applet by the sub-component instance, wherein the event carries a callback function;
searching a virtual node corresponding to the identifier of the sub-component through the instance of the parent component, and transmitting the data of the virtual node into the callback function;
acquiring data of the virtual node from the callback function through the sub-component instance;
and creating an instance of the third-party component in the instance of the custom component according to the data of the virtual node.
In the foregoing solution, the rendering unit is further configured to compare, by the instance of the sub-component, the data with data used in a previous rendering of the rendering environment, and transmit difference data obtained by the comparison to the rendering environment for rendering.
In the above scheme, the creating unit is further configured to construct a reference relationship graph according to reference relationships between the third-party component and native components of the applet;
and recursively analyzing the reference relation graph according to the reference scene of the third-party component, and generating an entry file of the applet according to the recursively analyzed reference relation.
In the above scheme, the creating unit is further configured to update a construction tool in a development project of the third-party component through a plug-in;
and analyzing the syntax of the third-party component through the updated construction tool to obtain the reference relation of the third-party component and the small program, the page of the small program and the self-defined component of the small program in the syntax.
In the above scheme, the creating unit is further configured to recursively analyze the reference relationship in the reference relationship graph from a building entry of the reference relationship graph;
when the reference scene of the reference relation refers to the third-party component by the small program, the page of the small program or the self-defined component of the small program, generating the following target file:
an entry file of the applet, an entry file of a page of the applet, an entry file of the third party component, a configuration file of the applet, a template file of the applet, and a style sheet of the applet.
In the above scheme, the creating unit is further configured to assign, in a template of the applet, an identifier to a tag of a non-native component of the applet and a tag with a time binding property, and add an event monitoring function to the non-native component.
An embodiment of the present invention further provides an applet processing apparatus, including:
a memory for storing executable instructions;
and the processor is used for realizing the processing method of the small program provided by the embodiment of the invention when the executable instruction stored in the memory is executed.
The embodiment of the invention provides a storage medium, which stores executable instructions and is used for causing a processor to execute so as to realize the small program processing method provided by the embodiment of the invention.
The embodiment of the invention has the following beneficial effects:
the instance of the third-party component is created by calling the entry file constructed corresponding to the small program, and the processing of the third-party component in the running environment of the third-party component can be converted into the running of the sub-component through the transmission of the event and the data between the sub-component and the third-party component, so that the decoupling between the development frameworks of the small program and the third-party component is realized, and various third-party components can be reused in the small program.
Drawings
FIG. 1 is a schematic diagram of an applet constructed in an mpvue project provided by the related art;
FIG. 2 is a diagram illustrating a scenario 100 for building and operating an applet according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an applet processing apparatus 50 according to an embodiment of the present invention;
FIG. 4 is an alternative flow diagram of an applet processing method provided in an embodiment of the present invention;
FIG. 5 is a diagram of an alternative reference relationship diagram provided by an embodiment of the present invention;
FIG. 6 is an alternative diagram of generating an entry file of an applet according to a reference relationship according to an embodiment of the present invention;
FIG. 7 is an alternative flow diagram of an applet processing method provided in an embodiment of the present invention;
fig. 8 is a schematic flowchart of creating an instantiation of a sub-component in an instantiation of a parent component and creating a vue.js instantiation on the instantiation of the sub-component according to an embodiment of the present invention;
FIG. 9 is a diagram illustrating data flow provided by an embodiment of the present invention;
FIG. 10 is a schematic diagram of a user interface of an applet processing method according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of an applet processing apparatus 50 according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail with reference to the accompanying drawings, the described embodiments should not be construed as limiting the present invention, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.
In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein is for the purpose of describing embodiments of the invention only and is not intended to be limiting of the invention.
Before further detailed description of the embodiments of the present invention, terms and expressions mentioned in the embodiments of the present invention are explained, and the terms and expressions mentioned in the embodiments of the present invention are applied to the following explanations.
1. A Mini Program (Program) is a Program developed based on a front-end-oriented Language (e.g., JavaScript) and implementing a service in a hypertext Markup Language (HTML) page, and software downloaded by a client (e.g., a browser or any client embedded in a browser core) via a network (e.g., the internet) and interpreted and executed in a browser environment of the client saves steps installed in the client. For example, an applet for implementing various services such as ticket purchase, a ride code, and the like may be downloaded and run in the social network client.
2. The runtime environment, the engine for interpreting and executing code, for example, for an applet, may be JavaScript Core of the iOS platform, X5JS Core of the android platform.
3. The rendering environment, the control for rendering the view, for example, for the rendering environment of the applet, may be wkwwebview of the iOS platform, X5 of the android platform (based on Chrome 53/57 kernel).
4. A Component (Component), which is a functional module of a view of an applet, also called the front-end Component, buttons, titles, tables, sidebars, content, and footers in a page, includes modular code to facilitate reuse among different pages of the applet.
5. A third party component, a component that can be used by the applet for development of the applet based on a third party development framework (e.g., Vue development framework).
6. And the self-defined component is a component which is defined and operated in the running environment of the applet and is used for realizing the function of the third-party component.
7. Build (Webpack), is a process of packaging the source files of an applet into a target file (e.g., a JavaScript file) that can be recognized and run in a client browser environment.
8. Reference relationships, also known as dependencies, syntactically referenced or referenced relationships between components, and graphical representations of reference relationships are referred to as reference relationship graphs or reference relationship graphs.
9. And the Document Object Model (DOM) is a copy of a DOM node of the page recorded by the JS Object, when data is required to be rendered, the virtual DOM corresponding to the rendered data is used for carrying out difference calculation with the real DOM to obtain difference, and the difference is used for modifying the real DOM in batch at one time so as to accelerate the display and refresh speed of the page.
10. The Template (Template), the structure and the style of the data to be rendered in the applet are used for rendering in the rendering environment after filling different data, so that the multiplexing of the structure and the style can be realized.
For example, in a template of an applet page, a structure is described in an eXtensible Markup Language (XML) file, a Style is described in a Cascading Style Sheets (CSS) file describing a component Style, the layout and the Style of the applet page may be multiplexed, and the template of the component may be used for multiplexing the layout and the Style of the component.
The following first analyzes and explains the processing scheme of the applet provided by the related art, including the building scheme and the running scheme of the applet.
The Vue development framework provided by the related art is a view development framework of an applet, which provides a running environment of components (hereinafter also referred to as vue.js components since the components are implemented in front-end scripting language JavaScript), allows reuse of the components in pages of the applet, and provides a Webpack tool capable of building source code of a project developed based on Vue development framework into a JavaScript file running in a browser environment.
Various types of development frameworks, such as mpvue development framework and megalo development framework, are derived from the Vue development framework, and realize the function of running vue. The working principle is as follows: the function of generating relevant files of the applet is added into the native building flow of the Vue framework, and meanwhile, the function of the vue.js component is realized by using the function referenced by a Template (Template) of the applet, namely, the Template referencing the vue.js component in the page of the applet.
And generating corresponding entry files for the applet pages only in the building stage, and generating corresponding templates for other Vue.
When the applet runs, an instance of the vue.js component runs in the Vue runtime environment, while in the applet environment the vue.js component exists in the form of a template reference.
When the Vue.js component is rendered, the Vue.js component reports data used for rendering to an example of an applet page to which the component belongs, then the data are aggregated by the example of the applet page and sent to a rendering environment of the applet, and in the rendering environment of the applet, the data are sent to corresponding templates layer by layer between the templates of the applet, and the templates filled with corresponding data are used for rendering.
Taking an mpvue project as an example, referring to fig. 1, fig. 1 is a schematic diagram of an operating principle of an applet constructed by the mpvue project provided by the related art, wherein A, B two sub-components (vue.js component a and vue.js component B) operating in an Vue operating environment are called in an applet page, and the sub-component B contains a sub-component C (vue.js component C); the corresponding templates in the applet are: an applet template a, an applet template B and an applet template C.
When the view of the Vue.js component is rendered, the data used for rendering is reported to the instance of the corresponding small program page by the instance of the Vue.js component, and then the related rendering data is aggregated and sent to the rendering environment of the small program by the instance of the small program page. The rendering environment of the applet extracts data used for rendering the sub-component from the received data according to logic (namely the structure and the style of the data) in the sub-component template, transfers the data to the sub-component template (an applet page template A, an applet template B and an applet template C), and performs rendering by combining the rendering environment with the template based on the filling data so as to realize view updating of the components in the page.
Through analysis, the related art has the following problems:
1. rendering of the applet page and the applet component depends on the applet page to send rendering data, so that the generated applet page and the generated applet component can only run in Vue running environment and cannot be reused in other projects without using Vue development frameworks, and development cost is greatly improved.
2. The target file of the applet is output in the form of an additional resource file in the building process, so that the applet file cannot be expressed in the reference relation diagram of the building tool, and the file of the applet is difficult to generate based on the reference relation diagram.
3. Js component functions are realized in a page by using template references of the applet, and the template is extremely different from a native code file of the applet, so that debugging is difficult, and unexpected exceptions can occur, for example, a calling mode of the template requires a caller to explicitly specify the component and data used by the template during rendering, which also causes the applet to encounter a situation that list data cannot be accessed in a specific scene during actual running.
In view of the foregoing problems in the related art, embodiments of the present invention provide a method, an apparatus, a device, and a storage medium for processing an applet, which can implement decoupling between development frameworks of the applet and a third-party component, and further can reuse various third-party components in the applet.
Referring to fig. 2, fig. 2 is a schematic diagram of a scenario 100 for building and operating an applet according to an embodiment of the present invention. A developer of the applet deploys a development framework (for example, Vue development framework) of the applet in a development device 200 (for example, a user terminal such as a computer, a server) to complete project development for the applet, and the applet can be used to implement services provided by various service parties, for example, a car code service, an express delivery service, online shopping, and the like.
A building tool of the applet is provided in the development framework, and is used to execute a building function in the applet processing method provided in the embodiment of the present invention, so as to encapsulate codes in a project of the applet into one or more JavaScript files capable of running in a browser environment of a client, and upload the JavaScript files to the server 300, where the server 300 may be a server that carries a service logic of a service party, for example, a background server that carries a riding service of a riding service provider, or may be a dedicated storage server, for example, a node of a shortest link with a terminal of a user in a Content Delivery Network (CDN).
Various types of clients can run in the terminal 400 held by the user, and various applets can be provided in the client for the user to select and use, for example, the social network client can provide the user with a riding code applet, a shopping application and the like, so that the user can flexibly use various functions in the social network client without installing a special riding code client and an online shopping client. Once the user confirms to download the applet in the terminal 400, the client requests the application server to download the JavaScript file of the applet through the network 500, and executes the operation function in the applet processing method provided in the embodiment of the present invention: the JavaScript file is interpreted and executed in the browser environment of the client, thereby running an instance of the applet.
As an example of an execution function of the applet processing method, an instance of an applet first initializes a page, may request page data from the server 300, and renders in the page. The page is composed of a series of components, when the user operates the components, the operating system of the terminal will deliver corresponding events to the instances of the applet, and the components will re-render according to their own logic, for example, when the component is a button in the page of the applet, the rendering can be reproduced to display the dynamic effect of the button being pressed and the corresponding content. When an instance of an applet receives data for a page updated by the server 300, the component will also re-render according to the data to update the page.
In some embodiments, the functions of the applet processing apparatus provided in the embodiment of the present invention may be distributed and deployed in different devices, for example, the building function in the applet processing apparatus may be deployed in the development device 200 shown in fig. 1, and the running function in the applet processing apparatus may be in the terminal 400 shown in fig. 2. Of course, in other embodiments, the function deployment in the applet processing apparatus may also be centrally deployed in the same device, for example, the development device 200 and the terminal 400 shown in fig. 2 may be the same device.
Referring to fig. 3, fig. 3 is a schematic structural diagram of an applet processing apparatus 50 according to an embodiment of the present invention, and the applet processing apparatus 50 shown in fig. 3 includes: at least one processor 510, memory 550, at least one network interface 520, and a user interface 530. The various components in the applet processing device 50 are coupled together by a bus system 540. It is understood that the bus system 540 is used to enable communications among the components. The bus system 540 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 540 in fig. 3.
The Processor 510 may be an integrated circuit chip having Signal processing capabilities, such as a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like, wherein the general purpose Processor may be a microprocessor or any conventional Processor, or the like.
The user interface 530 includes one or more output devices 531 enabling presentation of media content, including one or more speakers and/or one or more visual display screens. The user interface 530 also includes one or more input devices 532, including user interface components to facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.
The memory 550 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard disk drives, optical disk drives, and the like. Memory 550 optionally includes one or more storage devices physically located remote from processor 510.
The memory 550 may comprise volatile memory or nonvolatile memory, and may also comprise both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a Random Access Memory (RAM). The memory 550 described in connection with embodiments of the invention is intended to comprise any suitable type of memory.
In some embodiments, memory 550 can store data to support various operations, examples of which include programs, modules, and data structures, or subsets or supersets thereof, as exemplified below.
An operating system 551 including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;
a network communication module 552 for communicating to other computing devices via one or more (wired or wireless) network interfaces 520, exemplary network interfaces 520 including: bluetooth, wireless compatibility authentication (WiFi), and Universal Serial Bus (USB), etc.;
a presentation module 553 for enabling presentation of information (e.g., a user interface for operating peripherals and displaying content and information) via one or more output devices 531 (e.g., a display screen, speakers, etc.) associated with the user interface 530;
an input processing module 554 to detect one or more user inputs or interactions from one of the one or more input devices 532 and to translate the detected inputs or interactions.
In some embodiments, the memory 550 may be used for storing a building module 4551 and an operating module 4552 of the applet, for implementing the building function and the operating function, respectively, of the applet, as will be exemplified below.
Next, a method for processing an applet according to an embodiment of the present invention will be described with reference to exemplary application scenarios and structures of the applet processing apparatus described above.
First, a method for processing an applet provided in an embodiment of the present invention is described by taking an example of implementing an applet processing method to implement a building function of the applet. Fig. 4 is an optional flowchart schematic diagram of the applet processing method according to the embodiment of the present invention, and referring to fig. 4, the applet processing method according to the embodiment of the present invention includes:
step 401: constructing a reference relation graph according to reference relations between the third-party components and the original components of the small programs;
step 402: and recursively analyzing the reference relation graph according to the reference scene of the third-party component, and generating an entry file of the applet according to the recursively analyzed reference relation.
In some embodiments, according to the reference relationship between the third-party component and the native component of the applet, the construction of the reference relationship graph can be realized by the following steps:
updating a build tool in a development project of a third party component through a plug-in; and analyzing the syntax of the third-party component through the updated construction tool to obtain the syntactic reference relation between the third-party component and the applet, the page of the applet and the self-defined component of the applet.
In actual implementation, the code merging and generating logic of the construction tool native to Vue project is replaced by a plug-in, so that the following code merging and generating processes are realized:
and recursively traversing the reference relations in the reference relation graph from the building entry, and converting a source file (including source code, pictures, configuration and other static resources) of the referenced components in the reference relations into a file which can be identified and executed in a browser environment, namely a target file. For example, a JavaScript module in the source file and some extension languages (Scss, TypeScript, etc.) that cannot be directly run in the browser environment are converted into JavaScript files.
In some embodiments, generating the portlet's entry file may be accomplished by:
recursively analyzing the reference relations in the reference relation graph from a construction inlet of the reference relation graph; when the reference scene of the reference relation refers to the third-party component by the small program, the page of the small program or the self-defined component of the small program, generating the following target file:
an entry file for the applet, an entry file for a page of the applet, an entry file for a third party component, a configuration file for the applet, a template file for the applet, and a style sheet for the applet.
Here, in actual implementation, when a template file (JSON file) of an applet is generated, in a template of the applet, an Identifier (ID) is assigned to a tag of a non-native component (e.g., a veu, js component) of the applet and a tag with a time-binding property, and an event listening function is added to the non-native component.
Next, the building function of the applet will be described by taking the third-party component as a vue.js component as an example.
For the construction of the reference relationship diagram, the code analysis logic of the construction tool of the development framework is replaced by the plug-in Vue, so that the analysis work of the Vue.js component is carried out through the plug-in, the reference relationship between the Vue.js component and the small program page is determined, and the reference relationship diagram is formed.
Here, the build entry in the reference relationship graph is the main.js file of the Vue project, the build entry is the starting point of the reference relationship graph, and an instance of Vue is defined.
The reference relationship diagram generated in the embodiment of the present invention is independent of an actual reference scenario of components (i.e., the reference subject is an applet, an applet page, or vue.
Fig. 5 is a schematic diagram of an optional reference relationship diagram provided by an embodiment of the present invention, and see fig. 5, where a.vue, b.vue, c.vue, and d.vue are encapsulation files corresponding to vue.js component a, vue.js component B, vue.js component C, and vue.js component D, respectively. The module adopts a vue file format, html, css and js can be packaged, so that packaging of one module is realized, and a vue file is a single module. For fig. 5, when the reference relationship diagram is generated, the reference relationship between the components is determined only by the syntax of the components, and at this time, the construction tool does not need to acquire the reference scenario of the components in the whole application; that is, for the a.vue component, it is not necessary to know whether the applet refers to the a.vue component or the applet page refers to the a.vue component, but only if the syntax of the a.vue is analyzed to find that the a.vue component refers to the c.vue and the d.vue, the component at the next level of the a.vue is generated in the reference relationship diagram.
And for the generation of the entry file, namely the target file, of the applet, traversing the generated reference relation graph in combination with the reference scene, and forming a corresponding entry file, namely the target file, according to each reference relation in the reference relation graph.
Illustratively, for references whose reference scenario is by applet applications, applet pages, and custom components (vue.js components), the following reference relationships are generated: a reference to an entry file of an applet, a reference to an entry file of an applet page, a reference to an entry file of a vue.js component; a reference of a configuration file (JSON file) of the applet, a reference of a template file (i.e., XML file) of the applet, and a reference of the applet style sheet to generate a corresponding entry file based on the reference relationship.
Referring to fig. 5, c.vue is referred to by an applet page, and for this reference relationship, an entry file of the applet page is generated correspondingly according to a source file of c.vue; assuming that c.vue is also found to be referenced when traversing to b.vue, for this reference relationship, the portal file of vue.js component is generated according to the source file of c.vue, that is, one vue file can generate portal files under various scenarios (such as pages/components).
In practical applications, the entry file of the vue.js component includes: js, an entry file for the project, defines an Vue instance, and introduces a root component app. vue, which is mounted on a node with id 'app' in directory file index. html.
The portal file of the applet, named app, includes: js, the overall logic of the applet; json, common configuration of small programs, determination of paths of page files, overall window expression, setting of network timeout time, setting of multiple tabs and the like; wxss, applet common style sheet, describes the display attributes of various elements in a component.
The entry file of the applet page, taking the page name "page" as an example, includes: js, page logic; wxml, page structure; wxss, page style sheet; json, page configuration.
Taking a building tool as a Webpack as an example, fig. 6 is an optional schematic diagram of an entry file for generating applets according to a reference relationship provided by an embodiment of the present invention, referring to fig. 6, in actual implementation, static analysis is performed according to the reference relationship of modules, and then the modules generate corresponding static resources according to a specified rule, for example, if an application of an applet is to be generated by a.vue, a corresponding entry file is generated according to a rule of the applet, and if an applet page is generated by c.vue and d.vue, a corresponding entry file is generated according to a rule of a page, as can be seen from fig. 6, Webpack can convert multiple static resources js, css, and less into a static file, thereby reducing requests of the page.
The method for processing the applet provided in the embodiment of the present invention is described by taking the method for processing the applet as an example to implement the execution function of the applet. Referring to fig. 7, fig. 7 is an optional flowchart schematic diagram of an applet processing method according to an embodiment of the present invention, and referring to fig. 7, the applet processing method according to the embodiment of the present invention includes:
step 701: an applet is run in the client.
In some embodiments, the applet is used as a child application, the client is used as a parent application, the applet runs in a browser environment of the client, in an actual application, the client downloads a JavaScript file of the applet from the server, and runs an instance of the applet in the browser environment: the applet is interpreted and executed by an interpretation engine of a JavaScript file included in the browser environment, and a view of the applet is rendered in the client by a rendering engine included in the browser environment.
Here, the creation of an instance of an applet is explained.
In actual applications, the applet is downloaded by the client, the entry file (app. JS) of the applet is interpreted by a JS interpretation engine (browser core component) of the client, and the page of the applet is rendered in the client by a rendering engine (browser core component) of the client. In practical implementation, the execution environment and rendering environment of the applet in different terminals are different, for example, on iOS, the javascript code of the applet runs in javascript core and is rendered by wkvewviview, and the environments are iOS8, iOS9, iOS 10; on Android, applet javascript codes are parsed by X5JSCore, rendered by X5 based on the Mobile Chrome 53/57 kernel; on the development tool, the javascript code of the applet is run in nwjs and is rendered by Chrome Webview.
Step 702: an instance corresponding to a third party component of the applet is created by calling the entry file constructed for the applet.
In some embodiments, the instance corresponding to the third-party component of the applet may be a global instance of the third-party component, and accordingly, the global instance of the third-party component is created in the instance of the applet by calling the entry file of the applet, so as to share the configuration of the third-party component through the global instance.
In some embodiments, the instance corresponding to the third-party component of the applet may be an instance of the third-party component, which is accordingly created in the instance of the page of the applet by calling the entry file of the page of the applet, and which points to the global instance of the applet.
In some embodiments, when the instance corresponding to the third-party component is the instance of the third-party component, the virtual node corresponding to the custom component can be obtained by calling the entry file of the custom component of the applet, and the instance of the third-party component is created in the instance of the custom component according to the virtual node.
Here, in actual implementation, the virtual node corresponding to the custom component may be obtained as follows:
taking a page of the applet as a parent component and the custom component as a child component, and creating an instance of the child component in the instance of the parent component; transferring an event to a parent component through an event interface of the applet by an example of the sub-component, wherein the event carries a callback function; searching a virtual node corresponding to the identifier of the sub-component through the instance of the parent component, and transmitting the data of the virtual node into the callback function; and acquiring the data of the virtual node from the callback function through the instantiation of the subcomponent.
Here, the virtual node will be explained. In practical application, the virtual node can be understood as a virtual DOM, the virtual DOM is a copy of a DOM node recorded by a JS object, the hierarchical relationship and some basic attributes between elements are reserved, when the DOM is changed, diff is firstly carried out by the virtual DOM to calculate the minimum difference, and then the real DOM is modified in batch once to accelerate the display refresh speed.
Rendering of a real DOM tree requires that a CSS style and a DOM tree are parsed first, then the CSS style and the DOM tree are integrated into a rendering tree, then the position of each node in a browser is calculated through a layout algorithm, and finally the position is output to a display, while the virtual DOM can be understood as storing all information contained before a DOM tree is rendered, and the information can be stored in a memory all the time in an object form and maintained through JavaScript operation.
Accordingly, an instance of a third-party component can be created from the virtual nodes in the instance of the custom component by: and creating an instance of the third-party component in the instance of the custom component according to the data of the virtual node.
Taking the third-party component as the vue.js component as an example, calling the entry file to create the vue.js instance corresponding to the vue.js component of the applet may include the following several cases:
1) for the case of calling an applet's entry file, a unique global instance (vue.js instance) corresponding to the vue.js component is created on the applet application instance, which is used to implement global configuration sharing.
2) For the case of calling the applet page entry file, a vue.js instance is created on the applet page instance that corresponds to the vue.js component, the parent component of which points to the global instance of the applet application.
3) And for the condition of calling the entry file of the custom component, acquiring the virtual node corresponding to the custom component, creating a Vue.js instance of the corresponding Vue.js component on the instance of the applet custom component, and returning the Vue.js instance of the Vue.js component.
Next, taking an applet as a parent component, a page of the applet as a parent component, and a custom component as a child component as an example, a vue.js instance for creating a corresponding vue.js component on an applet custom component instance is described. Fig. 8 is a flowchart illustrating creating an instantiation of a sub-component in an instantiation of a parent component and creating a vue.js instantiation on the instantiation of the sub-component according to an embodiment of the present invention, which will be described with reference to the steps shown in fig. 8.
First, before an instantiation of a sub-component is created in an instantiation of a parent component, an applet application instantiation needs to be created to create a global instantiation on the applet application instantiation for implementing global configuration sharing.
After the applet application instantiation is created, an instantiation of a sub-component can be created in an instantiation of a parent component and a Vue.
Step 801: the parent component (i.e., the entity in the applet that references the vue. js component) creates an instantiation of the child component.
Step 802: the child component sends an internal event to the parent component.
The sub-component sends the internal event to the parent component through a custom event interface provided by the applet, and simultaneously carries a corresponding callback function; the internal event may be a predetermined event, and is used to acquire the virtual node data.
Step 803: and the parent component searches the virtual node according to the sub-component ID.
In actual implementation, the parent component monitors an internal event sent by the child component, if the parent component is not the vue.js component, the internal event is ignored, otherwise, according to the unique ID of the sender, the corresponding virtual node is searched from the component instance, and the virtual node data is transmitted to a callback function of the event.
Step 804: the parent component returns the virtual node data to the child component.
And the parent component acquires the virtual node data from the callback function and returns the virtual node data to the child component.
Step 805: the subcomponent creates a Vue. js instantiation on the instantiation of the subcomponent from the virtual node data.
In practical applications, event and data binding needs to be performed on a sub-component after creating a vue.js instance on an instantiation of the sub-component.
Specifically, an event is received in the applet environment for the vue.js component, and the subcomponent passes the event to the instance of the vue.js component, with a callback function.
For data binding of sub-components, the following steps may be included:
and 1, in the stage of initial rendering of vue.js by the rendering environment of the applet, the subcomponent runs a subcomponent rendering function, transmits rendering data returned by the function into the rendering function of the applet, and renders the rendering data by the rendering environment of the applet, and meanwhile, the data is stored in the applet instance.
In the building stage, a rendering function of a sub-component is generated in advance according to a template of the Vue.js component, wherein the rendering function of the sub-component comprises a logic structure (structure and style) of the Vue.js component in addition to data (namely DOM data) required by the applet application in rendering, so that the data which is rendered for the first time and the data which is newly generated later and needs to be rendered are compared based on the logic structure.
And 2, an event aiming at the vue.js component occurs in the view, and an instance of the vue.js component generates new data needing to be rendered according to business logic.
In practical application, a user clicks a vue.js component in an applet page, and a sub-component transmits an event to vue.js; the instances of the vs. js component generate data to be rendered according to the business logic of the instances, the data are transmitted into the callback function, and the subcomponents take out the rendering data from the callback function.
And 3, the sub-component operates the rendering function again, and transmits the difference data to the rendering function of the applet for rendering by comparing the new data needing to be rendered returned by the v ue.
The applet component and the Vue.js component bound in the steps are directly transmitted through the corresponding callback function according to data needing to be rendered by the Vue.js component, the data are filled in a template of the applet component to be rendered, the component rendering data are irrelevant to an upper page, and the relevant page and the component can independently run.
Fig. 9 is a schematic diagram of data flow provided by an embodiment of the present invention, referring to fig. 9, data required when rendering is performed on the vue.js component a referenced by the page a, is directly transferred from an instance of the vue.js component to an instance of a parent component, that is, an instance of the applet page a (sub component), and the data is fetched by the instance of the applet page a according to logic in the applet page template a and transferred to a rendering environment of the applet for rendering; in fig. 9, data required for rendering of page a is directly transferred from the instantiation of the vue.js component to the instantiation of the applet page a (subcomponent), and the data is fetched by the instantiation of the applet page a according to the logic in the applet page template a and transferred to the rendering environment of the applet for rendering; in fig. 9, the related data required for rendering the page a and the component B are directly transferred from the vue.js instance to the applet related instance, and the operation of the component B is not dependent on the logic of the upper page.
Step 703: and acquiring an event corresponding to the third-party component in the applet, and transmitting the event to an instance of the third-party component through the sub-component.
Step 704: and acquiring data generated by the event corresponding to the instance of the third-party component, and rendering the data through the rendering environment of the applet.
In some embodiments, after obtaining data generated by an event corresponding to an instance of a third-party component, rendering of the data in the rendering environment may be achieved by:
and comparing the data with data used for rendering the rendering environment at the previous time through the sub-component instance, and transmitting the difference data obtained by comparison into the rendering environment for rendering.
Taking an event triggered by a user in an applet to realize data update as an example, fig. 10 is a schematic user interface diagram of an applet processing method provided in an embodiment of the present invention, in this example, an applet page is used as a parent component, a selection frame in the applet page is a child component, an instance of the selection frame is created in the instance of the applet page, and a vue.js instance corresponding to the vue.js component is created on the instance of the selection frame, as shown in fig. 10, a current user interface is an applet page selected by a user on a device, when the user clicks the selection frame in the applet page, an event for the vue.js component is triggered, the child component transfers the event to the instance of the vue.js component through a function, the instance of the vue.js component generates new callback data to be rendered according to its own business logic, transfers the callback data to the function, takes out the rendering data from the child component, runs a rendering function, js instance, the new data to be rendered and the data rendered last time are compared by the rendering function, and the difference data is transmitted to the rendering function of the applet for rendering, so that data updating is realized, as shown in fig. 10, after the user clicks the selection box, the selectable items of the device are displayed.
Continuing with the description of exemplary functions in the applet processing apparatus 50 provided in the embodiment of the present invention, for details which are not described in detail below, it can be understood from the above description that fig. 11 is a schematic diagram of a constituent structure of the applet processing apparatus 50 provided in the embodiment of the present invention, and referring to fig. 11, the applet processing apparatus 50 provided in the embodiment of the present invention includes: a construction module 4551 and an operation module 4552;
the building module 4551 is configured to build a reference relationship diagram according to reference relationships between the third-party component and the native component of the applet;
and the system is used for recursively analyzing the reference relation graph according to the reference scene of the third-party component and generating the entry file of the applet according to the recursively analyzed reference relation.
The execution module 4552 is configured to implement an execution function of an applet, and includes:
an execution unit 51 for executing an applet in the client;
a creating unit 52 configured to create an instance corresponding to a third-party component of the applet by calling the entry file constructed corresponding to the applet;
an obtaining unit 53, configured to obtain an event corresponding to the third-party component in the applet, and transmit the event to an instance of the third-party component through a subcomponent;
and a rendering unit 54, configured to obtain data generated by the instance of the third-party component corresponding to the event, and render the data through a rendering environment of the applet.
In some embodiments, the creating unit is further configured to create a global instance of the third-party component in the instance of the applet by calling an entry file of the applet, so as to perform configuration sharing on the third-party component through the global instance.
In some embodiments, the creating unit is further configured to create an instance of the third-party component in an instance of a page of the applet by calling an entry file of the page of the applet, and the instance of the third-party component points to a global instance of the applet.
In some embodiments, the creating unit is further configured to obtain a virtual node corresponding to a custom component of the applet by calling an entry file of the custom component, and create an instance of the third-party component in the instance of the custom component according to the virtual node.
In some embodiments, the creating unit is further configured to create an instantiation of the sub-component in an instantiation of a parent component by taking a page of the applet as a parent component and taking the custom component as a sub-component;
transferring an event to the parent component through an event interface of the applet by the sub-component instance, wherein the event carries a callback function;
searching a virtual node corresponding to the identifier of the sub-component through the instance of the parent component, and transmitting the data of the virtual node into the callback function;
acquiring data of the virtual node from the callback function through the sub-component instance;
and creating an instance of the third-party component in the instance of the custom component according to the data of the virtual node.
In some embodiments, the rendering unit is further configured to compare, by the instantiation of the sub-component, the data with data used in a previous rendering of the rendering environment, and transfer difference data obtained by the comparison into the rendering environment for rendering.
In some embodiments, the creating unit is further configured to construct a reference relationship graph according to reference relationships between the third-party component and the native component of the applet;
and recursively analyzing the reference relation graph according to the reference scene of the third-party component, and generating an entry file of the applet according to the recursively analyzed reference relation.
In some embodiments, the creating unit is further configured to update a build tool in a development project of the third-party component through a plug-in;
and analyzing the syntax of the third-party component through the updated construction tool to obtain the reference relation of the third-party component and the small program, the page of the small program and the self-defined component of the small program in the syntax.
In some embodiments, the creating unit is further configured to recursively parse the reference relationships in the reference relationship graph from a building entry of the reference relationship graph;
when the reference scene of the reference relation refers to the third-party component by the small program, the page of the small program or the self-defined component of the small program, generating the following target file:
an entry file of the applet, an entry file of a page of the applet, an entry file of the third party component, a configuration file of the applet, a template file of the applet, and a style sheet of the applet.
In some embodiments, the creating unit is further configured to assign, in a template of the applet, an identifier to a tag corresponding to a non-native component of the applet and a tag with a time-binding property, and add an event listening function to the non-native component.
The embodiment of the invention also provides a storage medium which stores executable instructions, wherein the executable instructions are stored in the storage medium and can cause a processor to execute the processing method of the small program provided by the embodiment of the invention when being executed by the processor.
In some embodiments, the storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.
In some embodiments, executable instructions may be written in any form of programming language (including compiled or interpreted languages), in the form of programs, software modules, scripts or code, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
By way of example, executable instructions may correspond, but do not necessarily have to correspond, to files in a file system, and may be stored in a portion of a file that holds other programs or data, such as in one or more scripts in a hypertext Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
By way of example, executable instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network.
In summary, the embodiments of the present invention have the following beneficial effects:
1. the operating environment of the applet and the Vue.js component is decoupled, the limitation that the component in the prior art depends on a corresponding page in rendering is removed, the entry file of the applet generated by the Vue.js component can be reused in the applet, and the development efficiency is improved.
2. The template file of the applet generated according to the reference scene of the Vue.js component is consistent with the native user code structure of the applet, so that the debugging is convenient, and the problems that data cannot be accessed in a specific scene and the like are solved.
3. Corresponding applet applications and plug-ins can be generated for the Vue project according to the reference relation diagram, and independent applet pages and components can be generated according to independent Vue.
4. The generated small program page and the generated small program assembly can be independently quoted, and the performance of the small program page and the small program assembly is consistent with that of a normal small program page and the small program assembly, so that the visual effect of the small program is unified, and the mutual calling between the small program assembly and the Vue.
The above description is only an example of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present invention are included in the protection scope of the present invention.
Claims (15)
1. A method for processing an applet, comprising:
running the applet in the client;
creating an instance corresponding to a third-party component of the applet by calling an entry file constructed corresponding to the applet;
acquiring an event corresponding to the third-party component in the applet, and transmitting the event to an instance of the third-party component through a sub-component of the applet;
and acquiring data generated by the third-party component instance corresponding to the event, and rendering the data through the applet rendering environment.
2. The method of claim 1,
the creating an instance corresponding to a third-party component of the applet by calling the entry file constructed corresponding to the applet comprises:
and creating a global instance of the third-party component in the instance of the applet by calling the entry file of the applet so as to share the configuration of the third-party component through the global instance.
3. The method of claim 1,
the creating an instance corresponding to a third-party component of the applet by calling the entry file constructed corresponding to the applet comprises:
creating an instance of the third party component in an instance of a page of the applet by calling an entry file for the applet, and the instance of the third party component points to a global instance of the applet.
4. The method of claim 1,
the creating an instance corresponding to a third-party component of the applet by calling the entry file constructed corresponding to the applet comprises:
and acquiring a virtual node corresponding to the custom component by calling an entry file of the custom component of the applet, and creating an instance of the third-party component in the instance of the custom component according to the virtual node.
5. The method of claim 4, wherein the obtaining the virtual node corresponding to the custom component comprises:
taking a page of the applet as a parent component and the custom component as a child component, and creating an instance of the child component in an instance of the parent component;
transferring an event to the parent component through an event interface of the applet by the sub-component instance, wherein the event carries a callback function;
searching a virtual node corresponding to the identifier of the sub-component through the instance of the parent component, and transmitting the data of the virtual node into the callback function;
acquiring data of the virtual node from the callback function through the sub-component instance;
the creating an instance of the third-party component in the instance of the custom component according to the virtual node includes:
and creating an instance of the third-party component in the instance of the self-defined component according to the data of the virtual node.
6. The method of claim 5, wherein obtaining data generated by the instance of the third-party component in response to the event and rendering the data through the applet's rendering environment comprises:
and comparing the data with data used by the previous rendering of the rendering environment through the instantiation of the sub-component, and transmitting the difference data obtained by comparison into the rendering environment for rendering.
7. The method of claim 1, further comprising:
constructing a reference relation graph according to reference relations between the third-party components and the original components of the small program;
and recursively analyzing the reference relation graph according to the reference scene of the third-party component, and generating an entry file of the applet according to the recursively analyzed reference relation.
8. The method of claim 7, wherein constructing a reference relationship graph according to reference relationships between the third-party component and native components of the applet comprises:
updating a build tool in a development project of the third party component through a plug-in;
and analyzing the syntax of the third-party component through the updated construction tool to obtain the reference relation of the third-party component and the small program, the page of the small program and the self-defined component of the small program in the syntax.
9. The method of claim 7, wherein recursively parsing the reference relationship graph according to the reference scenario of the third-party component and generating the entry file of the applet according to the recursively parsed reference relationship comprises:
recursively resolving the reference relations in the reference relation graph from a construction inlet of the reference relation graph;
when the reference scene of the reference relation refers to the third-party component by the small program, the page of the small program or the self-defined component of the small program, generating the following target file:
an entry file of the applet, an entry file of a page of the applet, an entry file of the third party component, a configuration file of the applet, a template file of the applet, and a style sheet of the applet.
10. The method of claim 9, further comprising:
in the template of the small program, distributing identifications for the tags of the non-native components of the small program and the tags with the time binding attributes, and adding an event monitoring function for the non-native components.
11. An applet processing apparatus, comprising:
an operation unit for operating the applet in the client;
a creating unit configured to create an instance corresponding to a third-party component of the applet by calling an entry file constructed corresponding to the applet;
the acquisition unit is used for acquiring an event corresponding to the third-party component in the applet and transmitting the event to an instance of the third-party component through a sub-component of the applet;
and the rendering unit is used for acquiring data generated by the third-party component instance corresponding to the event and rendering the data through the applet rendering environment.
12. The apparatus of claim 11,
the creating unit is further configured to create a global instance of the third-party component in the instance of the applet by calling the entry file of the applet, so as to perform configuration sharing on the third-party component through the global instance.
13. The apparatus of claim 11,
the creating unit is further configured to create an instance of the third-party component in an instance of a page of the applet by calling an entry file of the page of the applet, and the instance of the third-party component points to a global instance of the applet.
14. An applet processing apparatus, comprising:
a memory for storing executable instructions;
a processor for implementing the method of processing an applet as claimed in any one of claims 1 to 10 when executing executable instructions stored in the memory.
15. A storage medium storing executable instructions for causing a processor to perform a method of processing an applet as claimed in any one of claims 1 to 10 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910538843.XA CN112114890A (en) | 2019-06-20 | 2019-06-20 | Method, device and equipment for processing small program and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910538843.XA CN112114890A (en) | 2019-06-20 | 2019-06-20 | Method, device and equipment for processing small program and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112114890A true CN112114890A (en) | 2020-12-22 |
Family
ID=73796586
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910538843.XA Pending CN112114890A (en) | 2019-06-20 | 2019-06-20 | Method, device and equipment for processing small program and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112114890A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282291A (en) * | 2021-06-10 | 2021-08-20 | 豆盟(北京)科技股份有限公司 | Method, device and equipment for generating small program and storage medium |
| CN113703878A (en) * | 2021-10-29 | 2021-11-26 | 腾讯科技（深圳）有限公司 | Component starting method and device, storage medium and electronic equipment |
| CN113741764A (en) * | 2021-07-30 | 2021-12-03 | 阿里巴巴新加坡控股有限公司 | Component processing method, device and equipment |
| CN114035885A (en) * | 2021-12-22 | 2022-02-11 | 北京百度网讯科技有限公司 | Applet page rendering method and device and electronic equipment |
| CN115809056A (en) * | 2023-02-07 | 2023-03-17 | 深圳复临科技有限公司 | Component multiplexing implementation method and device, terminal equipment and readable storage medium |
| WO2023245375A1 (en) * | 2022-06-20 | 2023-12-28 | 北京小米移动软件有限公司 | Method and apparatus for binding wasm rapid application framework data, and electronic device and storage medium |
-
2019
- 2019-06-20 CN CN201910538843.XA patent/CN112114890A/en active Pending
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282291A (en) * | 2021-06-10 | 2021-08-20 | 豆盟(北京)科技股份有限公司 | Method, device and equipment for generating small program and storage medium |
| CN113741764A (en) * | 2021-07-30 | 2021-12-03 | 阿里巴巴新加坡控股有限公司 | Component processing method, device and equipment |
| CN113703878A (en) * | 2021-10-29 | 2021-11-26 | 腾讯科技（深圳）有限公司 | Component starting method and device, storage medium and electronic equipment |
| CN113703878B (en) * | 2021-10-29 | 2022-02-22 | 腾讯科技（深圳）有限公司 | Component starting method and device, storage medium and electronic equipment |
| CN114035885A (en) * | 2021-12-22 | 2022-02-11 | 北京百度网讯科技有限公司 | Applet page rendering method and device and electronic equipment |
| WO2023245375A1 (en) * | 2022-06-20 | 2023-12-28 | 北京小米移动软件有限公司 | Method and apparatus for binding wasm rapid application framework data, and electronic device and storage medium |
| CN115809056A (en) * | 2023-02-07 | 2023-03-17 | 深圳复临科技有限公司 | Component multiplexing implementation method and device, terminal equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112114890A (en) | Method, device and equipment for processing small program and storage medium | |
| CN106843869B (en) | Front-end development engineering system and method | |
| US20230036980A1 (en) | Micro-frontend system, sub-application loading method, electronic device, computer program product, and computer-readable storage medium | |
| US8504913B2 (en) | Client-side components | |
| CN110806863A (en) | Interface document generation method and device, electronic equipment and storage medium | |
| US9384005B2 (en) | Systems and methods for dynamic configuration of client-side development environments through use of application servers | |
| US20030182626A1 (en) | On-demand creation of MIDlets | |
| CN106997298A (en) | A kind of application resource acquisition methods and device | |
| CN107807859A (en) | A kind of FaaS frameworks and its method of work, the system of exploitation O＆M FaaS frameworks | |
| CN111414350A (en) | Service generation method and device | |
| CN110580174A (en) | application component generation method, server and terminal | |
| Challita et al. | Model-based cloud resource management with TOSCA and OCCI | |
| US11604662B2 (en) | System and method for accelerating modernization of user interfaces in a computing environment | |
| CN114297549A (en) | Component processing method and device | |
| CN107608672B (en) | UI module manager, UI module management method and system | |
| CN116301951B (en) | Micro-service application installation upgrading method and device based on kubernetes | |
| CN116166907B (en) | Method and device for developing Web application by using WebAsssembly and service page compiling technology | |
| Fujima | Building a meme media platform with a JavaScript MVC framework and HTML5 | |
| CN114721647B (en) | Object-oriented programming method based on codeless application development | |
| CN116431155A (en) | Front-end application construction method, medium, device and computing equipment | |
| WO2021146895A1 (en) | Optimization method and apparatus for vehicle-mounted image display, computer device and storage medium | |
| CN115113869A (en) | Online webpage development method and device based on browser | |
| CN111880775A (en) | Multi-module layered architecture implementation method and device, electronic equipment and storage medium | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN114254232A (en) | Cloud product page generation method and device, computer equipment and storage medium |
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 |