Font processing method and device, equipment and storage medium
By obtaining and compiling desktop font files and generating and loading web page font files into virtual file systems, the problem of inconsistent loading fonts between desktop and web page applications is solved, and the consistency of user interface design style and interface display effect is improved.
Patent Information
- Application Number
- CN202411404026.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-09
- Publication Date
- 2025-03-11
- Estimated Expiration
- 2044-10-09
AI Technical Summary
Since desktop applications and client applications run on different systems, the loaded system fonts are inconsistent, which in turn affects the consistency of user interface design, resulting in poor interface display effect and affects user experience.
By obtaining the interface function code file of the target application of the desktop version, determining the packaging method and path mapping relationship of the font file, compiling and generating the web page font file, and loading it into the virtual file system to ensure that the font loaded by the web page version is consistent with the desktop version.
It realizes that the desktop and web versions of the same application are loaded consistently, ensuring the consistent user interface design style and improving the interface display effect and user experience.
Smart Images

Figure CN119598970A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a font processing method, apparatus, device and storage medium. Background Art
[0002] Application programs, referred to as applications for short, can include multiple operating versions depending on the operating environment or operating mode. For example, the versions of the same application generally include: desktop version and web version, that is, the same application generally includes desktop applications and client applications. Desktop applications refer to applications that are directly installed on users' computers and other devices; web applications (or web applications) are applications that present user interfaces and content through browsers.
[0003] Desktop applications and client applications generally have the same or corresponding functions. For example, the desktop version and web version of the same application generally have similar or consistent styles in user interface (UI) design. However, the desktop application and the client application may run on different systems. They generally load the system font of the running system by default, which makes it impossible to ensure that the loaded fonts are consistent, and thus it is impossible to ensure that the user interface design has a consistent style, resulting in poor interface display effects and affecting user experience. Summary of the invention
[0004] The present application provides a font processing method, apparatus, device and storage medium, which can ensure that the desktop version and web version of the same application can load consistent fonts and have a consistent user interface design style, thereby improving the interface display effect and user experience.
[0005] In a first aspect, the present application provides a font processing method, the method comprising: obtaining an interface function code file of a desktop version of a target application, the interface function code file comprising a desktop font file; determining a packaging method corresponding to the desktop font file and a target path mapping relationship between a target source storage path of a local file system and a target virtual storage path of a virtual file system; compiling the interface function code file according to the packaging method to generate other web page code files and web page font files stored in the target source storage path; loading the web page font files in the local file system into the virtual file system according to the mapping relationship between other web page code files and the target path; in response to an access request for the web page version of the target application, accessing the web page font files in the virtual file system, and rendering the user interface of the web page version of the target application based on the web page font files.
[0006] In a second aspect, the present application provides a font processing device, including: a first acquisition module, used to: acquire an interface function code file of a desktop version of a target application, the interface function code file including a desktop font file; a first determination module, used to: determine a packaging method corresponding to the desktop font file and a target path mapping relationship between a target source storage path of a local file system and a target virtual storage path of a virtual file system; a file compilation module, used to: compile the interface function code file according to the packaging method, generate other web page code files and web page font files stored in the target source storage path; a file loading module, used to: load the web page font files in the local file system into the virtual file system according to the mapping relationship between other web page code files and the target path; an access rendering module, used to: in response to an access request for the web page version of the target application, access the web page font files in the virtual file system, and render the user interface of the web page version of the target application based on the web page font files.
[0007] In a third aspect, the present application provides an electronic device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and executing the method in the first aspect or its various implementations.
[0008] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the method in the first aspect or its various implementations.
[0009] In a fifth aspect, the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the method in the first aspect or its various implementations.
[0010] In a sixth aspect, the present application provides a computer program, which enables a computer to execute the method in the first aspect or its various implementations.
[0011] Through the technical solution of the present application, the electronic device can obtain the web font file stored in the local file system by compiling the interface function code file including the desktop font file, thereby ensuring that the fonts corresponding to the web font file and the desktop font file are consistent, thereby ensuring that the fonts loaded by the target application of the desktop version and the target application of the web version are consistent, ensuring that the user interface design has a consistent style on multiple terminal versions to improve the interface display effect and user experience; and, due to security and privacy considerations, the web terminal cannot directly access the local file system, therefore, the electronic device also maps the web font file of the above-mentioned local file system to the virtual file system, so that the user interface of the web version of the target application can be rendered based on the web font file in the virtual file system, realizing a legal and flexible file access method. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0013] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application;
[0014] Figure 2 A flowchart of a font processing method provided in an embodiment of the present application;
[0015] Figure 3 A schematic diagram of a font processing method provided in an embodiment of the present application;
[0016] Figure 4 A schematic diagram of another font processing method provided in an embodiment of the present application;
[0017] Figure 5 A schematic diagram of another font processing method provided in an embodiment of the present application;
[0018] Figure 6 A schematic diagram of a font processing device 600 provided in an embodiment of the present application;
[0019] Figure 7 A schematic block diagram of an electronic device 700 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0020] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0021] As mentioned above, since the desktop application and the client application under the same application program run different systems, the related technology has the problem of inconsistent fonts loaded by the desktop application and the client application, which leads to inconsistent user interface design and poor display effect, affecting the user experience.
[0022] In order to solve the above technical problems, the inventive concept of the present application is: by compiling an interface function code file including a desktop font file, the web font file stored in the local file system is obtained; the web font file of the local file system is mapped to a virtual file system; and the user interface of the web version of the target application is rendered based on the web font file in the virtual file system.
[0023] It should be understood that the technical solution of the present application can be applied to the following scenarios, but is not limited to:
[0024] In one embodiment, the present application can be applied to application development or user interface display scenarios, specifically, it can be applied to: the scenario of developing the user interface of a web version of an application, or the scenario of displaying fonts in the user interface of a web version of an application.
[0025] In one embodiment, Figure 1 As shown, the application scenario may include a terminal device 110 and a server 120, and the terminal device 110 and the server 120 may be connected via a wired network or a wireless network.
[0026] Exemplarily, the browser on the terminal device 110 can launch the desktop version of the target application, the server 120 can obtain the interface function code file of the desktop version of the target application, including the desktop font file, and obtain the web font file stored in the local file system by compiling the interface function code file; map the web font file of the local file system to the virtual file system; thereafter, the server 120 can access the web font file in the virtual file system in response to an access request for the web version of the target application, and control the terminal device 110 to render the user interface of the web version of the target application based on the web font file obtained through the above access.
[0027] The server 120 may be a server, a server cluster consisting of multiple servers, or a cloud platform control center, but is not limited thereto. The terminal device 110 may be a mobile phone, a tablet computer, a laptop computer, or a desktop computer, but is not limited thereto.
[0028] It should be noted that Figure 1 The terminal devices and servers are merely exemplary. Specifically, other numbers or types of terminal devices or servers may also be included.
[0029] In addition, the technical solution of the present application can also be executed only through the terminal device. To avoid repetition, this application will not elaborate on this.
[0030] After introducing the application scenarios of the embodiments of the present application, the technical solution of the present application will be described in detail below:
[0031] Figure 2 This is a flowchart of a font processing method provided in an embodiment of the present application. The method can be executed by the terminal device 110 or the server 120 in the above application scenario, but is not limited thereto. Figure 2 As shown, the method may include the following steps:
[0032] S210: Acquire an interface function code file of a desktop version of a target application, where the interface function code file includes a desktop font file;
[0033] S220: Determine a packaging method corresponding to the desktop font file and a target path mapping relationship between a target source storage path of the local file system and a target virtual storage path of the virtual file system;
[0034] S230: compile the interface function code file according to the packaging method to generate other web page code files and web page font files stored in the target source storage path;
[0035] S240: Loading the webpage font file in the local file system into the virtual file system according to the mapping relationship between other code files on the webpage and the target path;
[0036] S250: In response to an access request for a web version of the target application, access a web font file in the virtual file system, and render a user interface of the web version of the target application based on the web font file.
[0037] The interface function code file refers to a code file used to define and implement the user interface related functions of the target application of the desktop version. Among them, the user interface related functions can be functions related to the interaction or display of the user interface (UI), but are not limited to this. For example, it can be functions related to the font of the text displayed in the user interface, the font used for drawing charts, etc.
[0038] Specifically, the interface function code file may include: desktop font files. Desktop font files refer to files used to display fonts that need to be displayed on the user interface of the target application, and may include specific resources required for the target application to load fonts on the user interface, such as specific resource information for specifying the font shape, size, and style (bold, italic, etc.) of the font. The desktop version of the target application can render the user interface based on the desktop font file to display various text, charts, or image content.
[0039] The desktop terminal may be a desktop terminal running on a system such as Windows, Mac, or Linux, but is not limited thereto.
[0040] The programming language used to develop the above-mentioned interface function code file can be C language, C++ language, Rust language, but is not limited thereto.
[0041] The desktop font files may be files associated with local custom fonts of the desktop version of the target application.
[0042] In one embodiment, the electronic device can first determine all the code files of the desktop version of the target application; then, the interface function code file can be located in the entire code file through a command line tool; finally, the interface function code file can be directly extracted from the entire code file (for example, the interface function code file can be directly copied from the entire code file), thereby obtaining the interface function code file.
[0043] Specifically, the electronic device can first determine the file name, file type, string or function involved in the interface function code file; then use the above file name, file type, string or function as the search parameter of the command line tool; thereafter, the interface function code file can be located in all code files through the command line with the above search parameters set.
[0044] The command line tools include, but are not limited to, find command, locate command, and grep command.
[0045] It should be noted that for security and privacy reasons, the web page generally cannot directly access the local file system, and the web page font files determined according to the interface function code file are generally generated directly in the local file system (for example, the generated web page font files are stored in the target source storage path of the local file system by default). Therefore, the electronic device needs to predetermine the virtual file system and store the generated web page font files in the virtual file system. After that, the web page can achieve normal access to the web page font files through the virtual file system.
[0046] In addition, the electronic device can package the desktop font files before storing the web font files in the virtual file system to reduce the file size and simplify resource management. It can also facilitate the loading / running of the obtained web font files on the web page, that is, it can be better compatible with the corresponding loading / running system of the web page.
[0047] This application will introduce the packaging and compilation of desktop font files and the virtual file system in the following embodiments:
[0048] In one embodiment, there are two packaging methods corresponding to the desktop font files: an asynchronous packaging method (preload mode) and a synchronous packaging method (embed mode).
[0049] Among them, the asynchronous packaging method means that other code files on the web page and font files on the web page are packaged independently of each other, that is, other code files on the web page and font files on the web page obtained by packaging are independent and separate. Therefore, the size of other code files on the web page is small, which is convenient for subsequent loading of font files on the web page according to other code files on the web page.
[0050] The synchronous packaging method refers to embedding the web page font files into other web page code files during the packaging process, that is, the other web page code files and the web page font files obtained by packaging are contained in one file. Therefore, the size of the obtained web page other code files is larger. Compared with the above-mentioned asynchronous packaging method, it is not convenient to subsequently load the web page font files according to other web page code files.
[0051] Therefore, the electronic device can determine other code files and font files on the web page according to the asynchronous packaging method to reduce the file size of other code files on the web page, facilitate the subsequent loading process of font files on the web page, and improve the loading speed and efficiency. Of course, other code files and font files on the web page can also be determined according to the synchronous packaging method, and this application does not limit this.
[0052] In one embodiment, the electronic device may package the interface function code files during the compilation of the interface function files; or the electronic device may perform compilation and packaging separately, for example, after compiling the interface function code files, the compiled files (for example, other code files on the web page side and font files on the web page side) may be packaged. This application does not limit the order of packaging and compiling.
[0053] Exemplarily, the electronic device can use a compiler to compile the interface function code file. Specifically, the compiler can be a compiler based on Wasm technology. For example, it can be a compiler based on EmscriptenSDK, or it can also be a Binaryen tool chain, WasmEdge, etc., but not limited to this.
[0054] Among them, the electronic device can compile and package the interface function code file according to a compiler based on the Emscripten SDK.
[0055] In addition, the electronic device can also use an automated build system to control the compilation process to achieve more efficient compilation. For example, the automated build system can be a CMake system, but is not limited to this. The electronic device can use the configuration file through the automated build system to control the compilation of the interface function code file. For example, the conditional compilation provided by the CMake system can be used to achieve the project configuration of different platforms, thereby achieving as much code reuse as possible.
[0056] Among them, the above-mentioned automated construction system for controlling the process of compiling interface function code files can be the automated construction system used when compiling the desktop version of the target application, thereby improving the compatibility and controllability of the compilation process and the code files generated by the compilation.
[0057] Exemplarily, for the method of performing compilation and packaging separately, the electronic device can use a separate packaging script to package the files compiled for the interface function code files. Specifically, the packaging script can be a script tool in EmscriptenSDK, specifically file_packager.py, but is not limited thereto.
[0058] In one embodiment, the virtual file system is a file system that does not actually exist, and is a virtual file system, whose directory structure and storage path are also virtual. The path hierarchy of the virtual file system is consistent with the path hierarchy of the local file system.
[0059] Exemplarily, the virtual file system may be MEMFS (Memory File System). MEMFS is a virtual file system provided by Emscripten, which allows files to be stored in memory instead of directly on the hard disk, thereby facilitating the simulation of file input and output in a Web environment, i.e., a web page.
[0060] In addition, the virtual file system may also be a proc file system or NFS (Network File System), but is not limited thereto.
[0061] In one embodiment, after determining the webpage font file, the electronic device may generate a target virtual storage path of a virtual file system for subsequently storing the webpage font file, wherein the path level of the target virtual storage path is consistent with the path level of the target source storage path.
[0062] It should be noted that this application will introduce the storage path mapping between the virtual file system and the local file system and the target path mapping relationship between the target source storage path and the target virtual storage path in subsequent embodiments. To avoid repetition, this application will not go into details here.
[0063] In one embodiment, in combination with the above embodiments, the electronic device can control the compilation process through an automated build system (for example, CMake compilation) and perform packaging during the compilation process. This application will introduce this in the following embodiments:
[0064] Specifically, the above-mentioned compiling the interface function code file according to the packaging method to generate other web page code files and web page font files stored in the target source storage path may include the following steps:
[0065] S230-1, constructing compilation parameters according to the mapping relationship between the packaging method and the target path.
[0066] The compilation parameters refer to the parameters used to control the compilation process of the interface function code files of the desktop application. Specifically, after obtaining the packaging method and the target path mapping relationship, the corresponding packaging tag can be generated based on the packaging method, and the target virtual storage path can be determined according to the target path mapping relationship, and then the compilation parameters can be constructed according to the packaging tag and the target virtual storage path.
[0067] The packaging tag refers to a tag used to uniquely identify the packaging method. For example, if the packaging method is an asynchronous packaging method, the packaging tag may be "--preload-file"; if the packaging method is a synchronous packaging method, the packaging tag may be "--embed-file".
[0068] The target path mapping relationship may include a target virtual storage path and a mapping symbol, wherein the mapping symbol is a symbol used to identify the step of mapping the source storage path of the local file system to the virtual storage path of the virtual file system, for example, the mapping symbol may be "@ / ". The target virtual storage path may refer to a specific level of a virtual directory of the virtual file system.
[0069] When constructing compilation parameters according to the packaging tag and the target virtual storage path, the packaging tag, the target virtual storage path and the mapping symbol may be combined, or the packaging tag and the target virtual storage path may be combined to obtain the compilation parameters.
[0070] Specifically, assuming that the packaging method is asynchronous packaging method, the target path mapping relationship includes: the specific level of the virtual directory that needs to be mapped to the virtual file system (that is, the target virtual storage path) and the mapping symbol, then the compilation parameter can be: --preload-file.. / .. / .. / .. / fonts@ / , where "--preload-file" indicates that the packaging method is asynchronous packaging method; ".. / .. / .. / .. / fonts@ / " indicates the target path mapping relationship; ".. / .. / .. / .. / fonts" indicates the target virtual storage path; "@ / " is a mapping symbol, indicating that the source storage path of the local file system needs to be mapped to the virtual file system, and the " / " in "@ / " indicates the default root directory when the virtual file system is running.
[0071] Among them, a relative path can be used to represent the target virtual storage path. Specifically, the initial path based on the relative path can be the path of the script file that will be generated for any project after compilation by the automated build system. For example, the initial path based on it can be the path of the Makefile file that will be generated for different projects after compilation with cmake.
[0072] For example, Figure 3 As shown in the figure, it is assumed that the generated web font file needs to be mapped and stored in the fonts folder, that is, the target virtual storage path is the path corresponding to the fonts folder; the path where the Makefile file is located is "M / Src / build / FTMain / MainApp", combined with Figure 3It can be seen that there is a fonts folder four levels above the folder where the Makefile file is located. Therefore, it can be determined that the target virtual storage path expressed by the relative path is: ".. / .. / .. / .. / fonts".
[0073] S230-2, configuring the compilation parameters in the project configuration file corresponding to the interface function code file through the parameter configuration command.
[0074] Specifically, in combination with the above content, the project configuration file can be a configuration file named "CMakeLists.txt" used by CMake compilation, which can generate an executable file. The executable file refers to a file that controls the compilation of the interface function code file.
[0075] Correspondingly, the parameter configuration command can be: target_link_libraries(); through the parameter configuration command, the compilation parameters are configured in the project configuration file corresponding to the interface function code file, which can be:
[0076] Add the following code to the project configuration file: target_link_libraries(${PROJECT_NAME}PUBLIC "--preload-file .. / .. / .. / .. / fonts@ / ").
[0077] S230-3, in response to the packaging method being an asynchronous packaging method, the compilation of the interface function code file is controlled by the project configuration file to generate other web page code files that are independently packaged and the web page font files stored in the target source storage path.
[0078] Correspondingly, in combination with the above content, the compilation of the interface function code files is controlled by the project configuration file. Specifically, the above-mentioned newly added code, that is, the parameter configuration command, controls the operation of the project configuration file to control the compilation of the interface function code files. Specifically, the control is implemented to package in an asynchronous packaging manner during the compilation process to generate other independent web page code files and web page font files stored in the target source storage path.
[0079] Afterwards, the process of automatically mapping the web font files stored in the target source storage path to the target virtual storage path of the virtual file system can also be controlled. This application will introduce the storage mapping process of the web font files in subsequent embodiments.
[0080] In one embodiment, other code files on the web page may include: web page script files and glue layer code files.
[0081] The web page script file includes a tag for referencing the glue layer code file, and the glue layer code file can be loaded and executed through the tag to achieve automatic execution of the glue layer code file. Specifically, the web page script file can be text.html.
[0082] The glue layer code file is used to load the web font file, which can trigger the loading interface of the virtual file system to load the web font file in the local file system into the virtual file system. In addition, the glue layer code file can also "glue" together different components or layers in the web font file to ensure that different components or layers can run smoothly and stably on the web. Specifically, the glue layer code file can be test.js.
[0083] In addition, the web page code files may also include test.wasm files, which refer to some binary files generated after compiling the interface function code files using Emscripten.
[0084] In one embodiment, Figure 4 As shown, the above-mentioned loading of the web page font file in the local file system into the virtual file system according to the mapping relationship between other code files and the target path of the web page may include the following steps:
[0085] S240-1 runs the web page script file;
[0086] S240-2 loads and executes the glue layer code file by referencing the glue layer code file tag in the web page script file;
[0087] Among them, the web page script file may include the tag that references the glue layer code file. If the web page script file is run and the tag is parsed, the glue layer code file can be automatically loaded and executed in response to the parsing of the tag.
[0088] S240-3 triggers the loading interface of the virtual file system through the glue layer code file;
[0089] Among them, Figure 4 As shown, the loading interface may be FS.createPreloadedFile.
[0090] Specifically, the glue layer code file may include a call to a virtual file system loading interface, which can operate the virtual file system, for example, can implement input and output to the virtual file system (ie, re-read or write data from the virtual file system).
[0091] S240-4 loads the web font file in the local file system into the virtual file system through the mapping relationship between the loading interface and the target path.
[0092] Among them, Figure 4 As shown, the web font file can be a test.data file. It is understandable that, by controlling the compilation of the interface function code file through the engineering configuration file, the desktop font file in the interface function code file is saved to the web font file such as the .data file, and the file path of the font file is mapped to the target source storage path.
[0093] Specifically, in combination with the above embodiments, the electronic device can control the above S240-4 through the engineering configuration file, complete the storage path mapping for the web page font files, and realize the connection between the web page and the local file system, so that the web page can use the resources stored in the local file system through the virtual file system, such as the web page font files, thereby improving the user experience and web page performance.
[0094] It can be understood that before accessing the web font file in the virtual file system, that is, before executing S250, the electronic device can first determine the function conversion relationship corresponding to the file system and the font file (for example, the function conversion relationship between the file operation functions corresponding to the desktop font file and the web font file in the virtual file system) and the path mapping relationship between the virtual file system and the local file system (including but not limited to: the target path mapping relationship between the target source storage path of the local file system and the target virtual storage path of the virtual file system, that is, the target path mapping relationship in the above S220); thereby, when accessing the virtual file system subsequently, it can be accessed directly according to the file operation function and source storage path used when accessing the local file system, and the present application can automatically convert them into the file operation function and virtual storage path corresponding to the virtual file system according to the function conversion relationship and the path mapping relationship, and access the virtual file system, thereby achieving the same effect as directly accessing the local file system, improving access efficiency and user experience.
[0095] In addition, various operations can be implemented for the virtual file system, such as obtaining the file path, reading files, writing files, etc. in the virtual file system, so that the web page font file mapping can be stored (i.e. loaded) into the virtual file system, that is, executing the above S240.
[0096] Specifically, the electronic device can determine the function conversion relationship and the path mapping relationship in the process of compiling the interface function code file, and this application does not impose any restrictions on this.
[0097] The following introduces the function conversion relationship of the file operation function and the path mapping relationship of the storage path:
[0098] In one embodiment, the electronic device can first obtain a desktop file operation function for a desktop font file; then, the desktop file operation function can be converted into a web file operation function for interacting with the virtual file system to obtain a function conversion relationship; finally, the web file operation function can be defined in a function library of the virtual file system to access the virtual file system through the function library.
[0099] Among them, the web page file operation function can achieve similar functions as accessing the local text system through the desktop file operation function by calling the corresponding interface in the virtual file system, such as opening a file, reading a file, or writing a file.
[0100] Exemplary, combined Figure 5 Assuming that the desktop font file is a C / C++ file, the electronic device can call the desktop font file operation interface to operate the desktop font file through the desktop file operation function. The desktop file operation function may include: fopen, fread and fwrite, where "fope n" is used to open a file, "fread" is used to read a file or data in a file, and "fwrite" is used to write a file or write data to a file.
[0101] Specifically, "fopen", "fread" and "fwrite" can be converted into web-side file operation functions for interacting with the virtual file system: open function, read function and write function. Among them, the "open function" can call the FS.open interface of the virtual file system to open the file in the virtual file system, or create a file stream FS.createStream, obtain the file path FS.getPath, etc.; the "read function" can call the FS.read interface of the virtual file system to read the file or the data in the file, etc.; the "write function" can call the FS.write interface of the virtual file system to write the file or write data to the file, etc.
[0102] Correspondingly, the function conversion relationship may include: a one-to-one correspondence between a web page file operation function and a desktop file operation function. For example, the function conversion relationship may be:
[0103] (fopen, open function; fread, read function; fwrite, write function).
[0104] Next, the web page file operation function can be defined in the function library of the virtual file system through the compiler, and then the virtual file system can be accessed through the web page file operation function in the function library. Figure 5 As shown, the function library of the virtual file system may be library_fs.js.
[0105] In addition, the above-mentioned function conversion relationship can also be defined in the function library, so that based on the function library and according to the function conversion relationship, the desktop file operation function can be automatically converted into the web file operation function, thereby achieving the same effect as directly accessing the local file system, thereby improving access efficiency and user experience.
[0106] In addition, if Figure 3 As shown, the compiler may also include a virtual file system, a C standard library (libc) and a C++ standard library (libcxx). Among them, the C standard library and the C++ standard library provide the basic functions (e.g., the above-mentioned desktop file operation functions) and classes required for the operation of the interface function code file, so as to perform special adaptation, encapsulation and the above-mentioned conversion on these functions and classes in the compiled interface function code file, and determine that the subsequently generated desktop font file is used to run correctly in the web page environment.
[0107] In one embodiment, the electronic device can first obtain multiple source storage paths in the local file system where the files generated after compiling the interface function code files are located; then, map the multiple source storage paths to multiple virtual storage paths in the virtual file system to obtain a path mapping relationship, and the path mapping relationship includes a target path mapping relationship; wherein the path hierarchy of the virtual file system is consistent with the path hierarchy of the local file system.
[0108] The virtual storage path may be represented by a relative path, and specific reference may be made to the representation of the target virtual storage path described above.
[0109] For example, assuming that the storage path under the Wasm file under the virtual storage path corresponds to: font / AAA.ttf, if the source storage path is ".. / .. / .. / .. / Wasm", it can be mapped to the virtual storage path " / "; if the source storage path is ".. / .. / .. / .. / Wasm / font", it can be mapped to the virtual storage path " / font"; if the source storage path is ".. / .. / .. / .. / Wasm / font / BBB.ttf", it can be mapped to the virtual storage path " / font / BBB.ttf".
[0110] Correspondingly, the path mapping relationship may include: a one-to-one corresponding source storage path and a virtual storage path. For example, the path mapping relationship may be:
[0111] (".. / .. / .. / .. / Wasm", " / "; ".. / .. / .. / .. / Wasm / font", " / font"; ".. / .. / .. / .. / Wasm / font / AAA.ttf", " / font / BBB.ttf").
[0112] The present application will introduce the process of rendering the user interface of the target application program of the web version based on the web font file in the virtual file system, that is, the above S250 in the following embodiments:
[0113] In one embodiment, the electronic device can implement the above S250 by following the steps:
[0114] S250-1, obtaining the target source storage path and the desktop font adding function corresponding to the desktop font file in the desktop file operation function.
[0115] Specifically, the electronic device may obtain the target source storage path and the desktop font adding function in response to an opening operation of the user interface of the target application program of the web version.
[0116] Exemplarily, the target source storage path and desktop font adding function obtained by the electronic device may be: ADD(str.. / .. / .. / .. / Wasm / font); wherein, "ADD()" is the desktop font adding function, and ".. / .. / .. / .. / Wasm / font" represents the target source storage path.
[0117] It should be noted that the electronic device can be a terminal device running a web version of the target application, or it can be a server corresponding to the terminal device. In this embodiment, the electronic device is taken as an example to introduce this.
[0118] In addition, the electronic device can be set to add a return function. If the addition of the web font corresponding to the web font file fails, the value "-1" can be returned by adding the return function, and no subsequent operation (for example, S250-5) is performed. If the addition of the web font corresponding to the web font file is successful, subsequent operations (for example, S250-5) are performed. That is, the addition of a return function can be used to determine whether the addition of the web font corresponding to the web font file is successful.
[0119] S250-2, converting the desktop font adding function into the webpage font adding function in the webpage file operation function according to the function conversion relationship, and mapping the target source storage path into the target virtual storage path according to the path mapping relationship.
[0120] Exemplarily, in combination with the above embodiments, assuming that the web page font adding function corresponding to the desktop font adding function "ADD()" in the function conversion relationship is "add", the electronic device can determine that the target virtual storage path is " / font" and the web page font adding function is "add".
[0121] S250-3, access the virtual file system through the function library and the target virtual storage path, and obtain the web page font file in the virtual file system.
[0122] Exemplarily, the electronic device may first determine that a desktop font adding function has been defined in a function library; then call the interface corresponding to the desktop font adding function in the virtual file system through the function library, and then obtain the web page font file from the target virtual storage path in the virtual file system through the interface.
[0123] S250-4, determine the webpage font corresponding to the webpage font file.
[0124] Specifically, the electronic device may first identify the specific resources included in the webpage font file, such as the font shape, size, and style (bold, italic, etc.) of the font, and then determine the webpage font according to the specific resources. For example, the webpage font may be a bold regular font.
[0125] Among them, the display effect of the webpage font corresponding to the webpage font file on the webpage is consistent with the display effect of the desktop font corresponding to the desktop font file on the desktop.
[0126] S250-5, set the web page font in the font instance of the user interface, and render the user interface through the font instance.
[0127] Specifically, the electronic device can set the webpage font in the font instance of the user interface through the following steps, and render the user interface through the font instance:
[0128] Step 1: Add the web page font to the font database of the web page version of the target application. The font database is used to manage fonts.
[0129] The font database can store multiple fonts, which can be all fonts involved in the target application of the web version. The font database can be used to manage multiple fonts more securely (for example, to ensure that the fonts subsequently displayed in the user interface are authorized to be used) and more centrally, which can improve the maintainability and accessibility of the fonts.
[0130] Step 2: Obtain the font family corresponding to the webpage font in the webpage font file.
[0131] Among them, a font family is a group of fonts with similar design styles and different styles (such as bold, italic, etc.). Through the font family, the fonts can be visually harmonious and unified. Among them, a font family can be included in the web font file, and can include a group of fonts with different styles and similar design styles in the same user interface.
[0132] Step three: according to the font family, set the web font in the font database in the font instance, and render the user interface through the font instance.
[0133] Specifically, the fonts in the font family and the web fonts in the font database can be set together in the font instance to provide a consistent visual style for the user interface when displaying different display elements in the user interface. Some display elements can be displayed based on the web fonts, and some display elements can be displayed based on fonts with similar design style to the web fonts but different styles (i.e., fonts in the font family).
[0134] Among them, the font instance can define the elements and execution steps required to display the webpage font in the user interface. For example, the font instance can include: the name of the font that needs to be displayed on the webpage (for example, the font name of the webpage font and the font family), the storage path of each font that needs to be displayed (for example, the above-mentioned target virtual path or the path of the font in the font database), and the execution steps for displaying the font that needs to be displayed. The execution steps can be: determining the storage path of each font that needs to be displayed through the name of the above-mentioned font that needs to be displayed; obtaining the corresponding font through the storage path of each font that needs to be displayed; loading and rendering the corresponding display element in the user interface (for example, a paragraph of text or title in the user interface) in the user interface according to the above-mentioned corresponding font.
[0135] Specifically, the above-mentioned rendering of the user interface through the font instance can be understood as displaying the display elements based on the web page font display in the user interface through the font instance. That is, the display elements in the user interface are displayed through the fonts involved in the font instance and the execution steps.
[0136] In addition, if the electronic device fails to add / set the font in an instance, a log can be recorded.
[0137] In one embodiment, the electronic device may first obtain an interface function code file of a desktop version of the target application, where the interface function code file includes a desktop font file.
[0138] Then, the electronic device can obtain the desktop file operation function for the desktop font file; convert the desktop file operation function into a web file operation function for interacting with the virtual file system to obtain a function conversion relationship; and define the web file operation function in the function library of the virtual file system to access the virtual file system through the function library.
[0139] In addition, the electronic device can also obtain multiple source storage paths in the local file system where the files generated after compiling the interface function code files are located; map the multiple source storage paths to multiple virtual storage paths in the virtual file system to obtain a path mapping relationship, and the path mapping relationship includes a target path mapping relationship; wherein the path hierarchy of the virtual file system is consistent with the path hierarchy of the local file system.
[0140] Next, the electronic device can determine the packaging method corresponding to the desktop font file (for example, asynchronous packaging method), and determine the storage location of the web font file generated after compiling the interface function code file, that is, the target source storage path of the local file system.
[0141] Then, the electronic device can compile the interface function file, and during the compilation process, package the interface function code file based on the asynchronous packaging method, and obtain other web page code files that are independently packaged and the web page font files stored in the target source storage path. Specifically, the electronic device can generate corresponding packaging tags based on the asynchronous packaging method, and determine the target virtual storage path according to the target path mapping relationship and the target source storage path, and combine the packaging tags corresponding to the asynchronous packaging method and the target virtual storage path to obtain compilation parameters; through parameter configuration commands, configure the compilation parameters in the engineering configuration file corresponding to the interface function code file in the automated construction system; control the compilation of the interface function code file through the engineering configuration file of the automated construction system, and generate other web page code files that are independently packaged and the web page font files stored in the target source storage path. Among them, other web page code files can include: web script files, glue layer code files.
[0142] Next, the electronic device can run the web page script file; load and execute the glue layer code file by referencing the tag of the glue layer code file in the web page script file; trigger the loading interface of the virtual file system through the glue layer code file; and load the web page font file stored in the target source storage path into the target virtual storage path in the virtual file system through the mapping relationship between the loading interface and the target path.
[0143] Finally, in response to an access request for a web version of the target application, the electronic device can obtain the target source storage path and the desktop font adding function corresponding to the desktop font file in the desktop file operation function; and convert the desktop font adding function into the web font adding function in the web file operation function according to the function conversion relationship, and map the target source storage path to the target virtual storage path according to the path mapping relationship; call the interface corresponding to the desktop font adding function in the virtual file system through the function library, and obtain the web font file from the target virtual storage path in the virtual file system through the interface; then, the web font corresponding to the web font file can be determined first; the web font is added to the font database of the web version of the target application, and the font database is used to manage fonts; the font family corresponding to the web font in the web font file is obtained; according to the font family, the web font in the font database is set in the font instance, and the user interface is rendered through the font instance.
[0144] It should be noted that all the above technical solutions can be combined in any way to form optional embodiments of the present application, which will not be described one by one here.
[0145] It should be noted that in the specific implementation of this application, relevant data such as code files, storage paths, packaging methods, and operation functions are involved. When the embodiments of this application are applied to specific products or technologies, user permission, consent or authorization is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
[0146] Figure 6 Schematic diagram of a font processing device 600 provided in an embodiment of the present application. Figure 6 As shown, the device 600 includes: a first acquisition module 601, a first determination module 602, a file compilation module 603, a file loading module 604, an access rendering module 605, a second acquisition module 606, a function conversion module 607, a function definition module 608, a third acquisition module 609, and a path mapping module 610.
[0147] In one embodiment, a first acquisition module 601 is used to obtain an interface function code file of a target application of a desktop version, wherein the interface function code file includes a desktop font file; a first determination module 602 is used to determine a packaging method corresponding to the desktop font file and a target path mapping relationship between a target source storage path of a local file system and a target virtual storage path of a virtual file system; a file compilation module 603 is used to compile the interface function code file according to the packaging method to generate other web page code files and web page font files stored in the target source storage path; a file loading module 604 is used to load the web page font files in the local file system into the virtual file system according to the mapping relationship between other web page code files and the target path; an access rendering module 605 is used to access the web page font files in the virtual file system in response to an access request for the target application of the web page version, and render the user interface of the target application of the web page version based on the web page font files.
[0148] In one embodiment, the file compilation module 603 is specifically used to: construct compilation parameters according to the mapping relationship between the packaging method and the target path; configure the compilation parameters in the project configuration file corresponding to the interface function code file through the parameter configuration command; in response to the packaging method being an asynchronous packaging method, control the compilation of the interface function code file through the project configuration file to generate other web page code files that are independently packaged and the web page font files stored in the target source storage path.
[0149] In one embodiment, other code files on the web page include: web page script files and glue layer code files. The web page script files include tags for referencing glue layer code files, and the glue layer code files are used to load web page font files. The file loading module 604 is specifically used to: run the web page script files; load and execute the glue layer code files by referencing the glue layer code files through tags in the web page script files; trigger the loading interface of the virtual file system through the glue layer code files; and load the web page font files in the local file system into the virtual file system through the mapping relationship between the loading interface and the target path.
[0150] In one embodiment, the second acquisition module 606 is used to: obtain the desktop file operation function for the desktop font file; the function conversion module 607 is used to convert the desktop file operation function into a web page file operation function for interacting with the virtual file system to obtain a function conversion relationship; the function definition module 608 is used to define the web page file operation function in the function library of the virtual file system to access the virtual file system through the function library.
[0151] In one embodiment, the third acquisition module 609 is used to: obtain multiple source storage paths in the local file system where the files generated after compiling the interface function code files are located; the path mapping module 610 is used to map the multiple source storage paths to multiple virtual storage paths in the virtual file system to obtain a path mapping relationship, and the path mapping relationship includes a target path mapping relationship; wherein the path hierarchy of the virtual file system is consistent with the path hierarchy of the local file system.
[0152] In one embodiment, the access rendering module 605 is specifically used to: obtain the target source storage path and the desktop font adding function corresponding to the desktop font file in the desktop file operation function; convert the desktop font adding function into the web page font adding function in the web page file operation function according to the function conversion relationship, and map the target source storage path to the target virtual storage path according to the path mapping relationship; access the virtual file system through the function library and the target virtual storage path to obtain the web page font file in the virtual file system; determine the web page font corresponding to the web page font file; set the web page font in the font instance of the user interface, and render the user interface through the font instance.
[0153] In one embodiment, the access rendering module 605 is specifically used to: add the web page font to the font database of the web page version of the target application, the font database is used to manage fonts; obtain the font family corresponding to the web page font in the web page font file; according to the font family, set the web page font in the font database in the font instance, and render the user interface through the font instance.
[0154] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 6 The device 600 shown can execute the above method embodiments, and the above and other operations and / or functions of each module in the device 600 are respectively for implementing the corresponding processes in the above methods, which will not be repeated here for the sake of brevity.
[0155] The above describes the device 600 of the embodiment of the present application from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.
[0156] Figure 7 A schematic block diagram of an electronic device 700 provided in an embodiment of the present application.
[0157] like Figure 7 As shown, the electronic device 700 may include:
[0158] The memory 710 and the processor 720, the memory 710 is used to store the computer program and transmit the program code to the processor 720. In other words, the processor 720 can call and run the computer program from the memory 710 to implement the method in the embodiment of the present application.
[0159] For example, the processor 720 may be configured to execute the above method embodiments according to instructions in the computer program.
[0160] In some embodiments of the present application, the processor 720 may include but is not limited to:
[0161] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
[0162] In some embodiments of the present application, the memory 710 includes but is not limited to:
[0163] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SL DRAM) and direct memory bus random access memory (DR RAM).
[0164] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 710 and executed by the processor 720 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.
[0165] like Figure 7 As shown, the electronic device may also include:
[0166] The transceiver 730 may be connected to the processor 720 or the memory 710 .
[0167] The processor 720 may control the transceiver 730 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.
[0168] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.
[0169] The present application also provides a computer storage medium on which a computer program is stored, and when the computer program is executed by a computer, the computer can perform the method of the above method embodiment. In other words, the present application embodiment also provides a computer program product containing instructions, and when the instructions are executed by a computer, the computer can perform the method of the above method embodiment.
[0170] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the computer can be made to perform the corresponding flow in each method in the embodiment of the present application in whole or in part, and generate the functions that can be realized by each method in the embodiment of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction can be transmitted from a website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0171] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0172] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
[0173] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
Claims
1. A font processing method, characterized in that: include: Obtaining an interface function code file of a desktop version of a target application, wherein the interface function code file includes a desktop font file; Determine a packaging method corresponding to the desktop font file and a target path mapping relationship between a target source storage path of the local file system and a target virtual storage path of the virtual file system; Compile the interface function code file according to the packaging method to generate other code files on the web page and font files on the web page stored in the target source storage path; According to the mapping relationship between the other code files on the web page and the target path, the web page font files in the local file system are loaded into the virtual file system; In response to an access request for a web version of a target application, a web font file in the virtual file system is accessed, and a user interface of the web version of the target application is rendered based on the web font file.
2. The method according to claim 1, characterized in that The compiling the interface function code file according to the packaging method to generate other web page code files and web page font files stored in the target source storage path includes: Constructing compilation parameters according to the mapping relationship between the packaging method and the target path; By means of a parameter configuration command, the compilation parameters are configured in the engineering configuration file corresponding to the interface function code file; In response to the packaging method being an asynchronous packaging method, the compilation of the interface function code file is controlled by the project configuration file to generate the other web page code files that are independently packaged and the web page font files stored in the target source storage path.
3. The method according to claim 1, characterized in that The other code files on the web page include: a web page script file and a glue layer code file, the web page script file includes a tag for referencing the glue layer code file, and the glue layer code file is used to load the web page font file; The step of loading the webpage font file in the local file system into the virtual file system according to the mapping relationship between the other code files on the webpage and the target path includes: Running the web page script file; By referencing the tag of the glue layer code file in the web page script file, loading and executing the glue layer code file; Triggering the loading interface of the virtual file system through the glue layer code file; The webpage font file in the local file system is loaded into the virtual file system through the mapping relationship between the loading interface and the target path.
4. The method according to claim 1, characterized in that: The method further includes: in response to an access request for a web version of the target application, accessing a web font file in the virtual file system, and rendering a user interface of the web version of the target application based on the web font file. Get the desktop file operation function for desktop font files; Converting the desktop file operation function into a web page file operation function for interacting with the virtual file system to obtain a function conversion relationship; The web page file operation function is defined in the function library of the virtual file system so as to access the virtual file system through the function library.
5. The method according to claim 1, characterized in that: The method further includes: in response to an access request for a web version of the target application, accessing a web font file in the virtual file system, and rendering a user interface of the web version of the target application based on the web font file. Acquire multiple source storage paths in the local file system where files generated by compiling the interface function code files are located; Mapping the multiple source storage paths to multiple virtual storage paths in the virtual file system to obtain a path mapping relationship, wherein the path mapping relationship includes the target path mapping relationship; The path level of the virtual file system is consistent with the path level of the local file system.
6. The method according to claim 4 or 5, characterized in that: The step of accessing the webpage font file in the virtual file system and rendering the webpage version of the user interface of the target application based on the webpage font file includes: Obtain the target source storage path and the desktop font adding function corresponding to the desktop font file in the desktop file operation function; The desktop font adding function is converted into the webpage font adding function in the webpage file operation function according to the function conversion relationship, and the target source storage path is mapped into the target virtual storage path according to the path mapping relationship; Access the virtual file system through the function library and the target virtual storage path to obtain the webpage font file in the virtual file system; Determine the webpage font corresponding to the webpage font file; The webpage font is set in a font instance of the user interface, and the user interface is rendered through the font instance.
7. The method according to claim 6, characterized in that The step of setting the webpage font in the font instance of the user interface and rendering the user interface through the font instance includes: Adding the webpage font to a font database of the target application of the webpage version, wherein the font database is used to manage fonts; Obtain the font family corresponding to the webpage font in the webpage font file; According to the font family, the webpage font in the font database is set in the font instance, and the user interface is rendered through the font instance.
8. A font processing device, characterized in that: include: The first acquisition module is used to: acquire an interface function code file of a desktop version of a target application, wherein the interface function code file includes a desktop font file; The first determination module is used to: determine the packaging method corresponding to the desktop font file and the target path mapping relationship between the target source storage path of the local file system and the target virtual storage path of the virtual file system; A file compiling module, used to compile the interface function code file according to the packaging method to generate other code files on the web page and font files on the web page stored in the target source storage path; A file loading module is used to: load the webpage font file in the local file system into the virtual file system according to the mapping relationship between the other code files on the webpage and the target path; The access rendering module is used to: in response to an access request for a web version of the target application, access the web font file in the virtual file system, and render the user interface of the web version of the target application based on the web font file.
9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 7 by executing the executable instructions.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
Citation Information
Patent Citations
Page rendering method and device, electronic equipment and storage medium
CN114218890A
Webpage rendering method and system, electronic equipment and computer readable storage medium
CN115168774A
Webpage rendering method and device, electronic equipment and medium
CN115758021A
Page display method and device, equipment and storage medium
CN117667084A
Mobile terminal APP embedded configuration graph rendering method and device and storage medium thereof
CN118467056A