CN118034823A - Display method, electronic device, storage medium, and program product - Google Patents

Display method, electronic device, storage medium, and program product Download PDF

Info

Publication number
CN118034823A
CN118034823A CN202211371981.1A CN202211371981A CN118034823A CN 118034823 A CN118034823 A CN 118034823A CN 202211371981 A CN202211371981 A CN 202211371981A CN 118034823 A CN118034823 A CN 118034823A
Authority
CN
China
Prior art keywords
information
application
party
interpreter
card
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
Application number
CN202211371981.1A
Other languages
Chinese (zh)
Inventor
郭振雄
靖轲
崔巍
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Petal Cloud Technology Co Ltd
Original Assignee
Petal Cloud Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Petal Cloud Technology Co Ltd filed Critical Petal Cloud Technology Co Ltd
Priority to CN202211371981.1A priority Critical patent/CN118034823A/en
Publication of CN118034823A publication Critical patent/CN118034823A/en
Pending legal-status Critical Current

Links

Landscapes

  • Stored Programmes (AREA)

Abstract

The application discloses a display method, an electronic device, a storage medium and a program product, which can display the content outside the display range of a screen in the screen. The display method is applied to the electronic equipment, and comprises the following steps: acquiring an application package of an application program acquired from an application server; the application package comprises first information, wherein the first information is information of a card; the information of the card is information of non-application program specifications; automatically loading a third party card interpreter according to the first information; the third party card interpreter is integrated in the application program; interpreting the first information into second information conforming to the application program specification by a third party card interpreter; and displaying the card according to the second information.

Description

Display method, electronic device, storage medium, and program product
Technical Field
The present application relates to the field of terminals, and in particular, to a display method, an electronic device, a storage medium, and a program product.
Background
Currently, program developers can write quick application pages using user interface components (UI components) in the quick application specification. Wherein the UI component is operable to render rendering rules. With the expansion demand of rich media, the pages of third parties DSL (Domain Specific Language) such as cards gradually enter the field of view of people as embeddable pages, and the pages can be used for directly presenting information of interest or interest to users through electronic equipment. The third party DSL page refers to a page presented by content provided by a third party server of a non-fast application. The third party server may be a stand alone content provider that may obtain a certain branding or funding effect by embedding the content onto the quick application, etc. A third party DSL page, such as a card that is an embeddable page, may also be operated and in response to operation of the third party DSL page, such as operation of a news a card embedded in the application, the electronic device may request an application package of news a from the application server. The electronic device may also obtain data from a third party server based on a uniform resource locator (uniform resource locator, URL) of news a in the application package and jump to a page displaying news a based on the data. However, for the fast application, since the fast application can only render the UI component in the fast application specification, the card cannot be rendered, and the fast application page embedded with the card cannot be displayed normally.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a display method, an electronic device, a storage medium, and a program product that can present a card.
In a first aspect, an embodiment of the present application provides a display method, applied to an electronic device, where the method includes: acquiring an application package of an application program acquired from an application server; the application package comprises first information, wherein the first information is information of a card; the information of the card is information of non-application program specifications; automatically loading a third party card interpreter according to the first information; the third party card interpreter is integrated in the application program; interpreting, by the third party card interpreter, the first information as second information conforming to an application specification; and displaying the card according to the second information.
According to the first aspect of the application, the third-party card interpreter is automatically loaded according to the first information of the non-application program specification in the application package of the application program, the first information is interpreted as the second information which accords with the application program specification through the third-party card interpreter, and the card is displayed according to the second information, wherein the first information is the information of the card. The application can enable the third-party card interpreter to be loaded on the application program without any change to the application program, and the third-party card interpreter can interpret the first information which is not the specification of the application program into the second information which accords with the specification of the application program, so that the framework of the application program can be utilized to display the card.
According to some embodiments of the application, the application package further includes third information, the third information being information of the application program; the method further comprises the steps of: interpreting the second information and the third information as fourth information; the fourth information is a virtual DOM or DOM instruction; and displaying the page of the application program according to the fourth information, wherein the page of the application program comprises the card. The method and the device can integrate the second information and the third information and then render and display the second information and the third information by interpreting the second information and the third information, generating the fourth information which is the virtual DOM or DOM instruction, displaying the page of the application program comprising the card according to the fourth information.
According to some embodiments of the application, the first information includes third party identification information; the automatically loading a third party card interpreter according to the first information comprises: identifying the first information according to the third party identification information; and automatically loading a third-party card interpreter according to the identified first information. According to the application, the third party identification information which can be identified as the third party is newly added in the application package, so that the first information can be identified as the card information, and further, the third party card interpreter can be automatically loaded according to the identified first information, so that subsequent interpretation can be performed.
According to some embodiments of the application, before the acquiring the application package of the application program acquired from the application server, the method further includes: registering the third party card interpreter with the application. The third-party card interpreter is registered to the application program, so that the third-party card interpreter can be integrated in the application program to expand functions for the application program.
According to some embodiments of the application, the registering the third party card interpreter with the application program comprises: providing a plug-in interface through a JS framework of the application program; and registering the third-party card interpreter to the JS framework through the plug-in interface. The application can register the third-party card interpreter to the JS framework through the plug-in interface provided by the JS framework of the application program, and can provide an expansion interface externally, so that the third-party card interpreter can perform data interaction with the JS framework in a plug-in form.
According to some embodiments of the application, the registering the third party card interpreter with the application program comprises: providing a plug-in interface through a template engine of the application program; registering the third party card interpreter with the template engine through the plug-in interface. The application can register the third-party card interpreter to the template engine through the plug-in interface provided by the template engine of the application program, and can provide an expansion interface externally, so that the third-party card interpreter can perform data interaction with the template engine in a plug-in form.
According to some embodiments of the application, the first information comprises tag information, the tag information comprising third party identification information; the automatically loading a third party card interpreter according to the first information comprises: storing an address table recording unique identifiers of one or more third party card interpreters registered and installed address information; the installed address information is used for determining the third party card interpreter; determining a corresponding third-party card interpreter according to the label information in the first information and the address table; and automatically loading the third party card interpreter. The application determines the third-party card interpreter from one or more third-party card interpreters through the label information and the address table in the first information, and automatically loads the third-party card interpreter, so that a plurality of different cards can be displayed.
In a second aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor and a memory, where the memory is configured to store program instructions, and where the processor is configured to implement a display method according to any one of the possible embodiments of the first aspect, when the processor invokes the stored instructions.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium storing a program that causes an electronic device to implement a display method according to any one of the possible embodiments of the first aspect above.
In a fourth aspect, an embodiment of the present application provides a computer program product comprising computer-executable instructions stored in a computer-readable storage medium; at least one processor of the electronic device may read the computer-executable instructions from the computer-readable storage medium, the at least one processor executing the computer-executable instructions causing the electronic device to perform the display method of any one of the possible embodiments of the first aspect above.
The advantages of the second to fourth aspects and various implementations of the present application may refer to the first aspect and various implementations thereof, and the analysis of the advantages of the first aspect, which are not described herein.
Drawings
Fig. 1 (a) to (b) are schematic diagrams of a prior art electronic device displaying a fast application page.
Fig. 2 is a schematic diagram of an electronic device in the prior art displaying a quick application page with a card embedded therein.
Fig. 3 is a schematic diagram of a display system according to an embodiment of the application.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Fig. 5 is a schematic logic structure diagram of an electronic device according to an embodiment of the present application.
Fig. 6 is a schematic software structure of a development device according to an embodiment of the present application.
Fig. 7 is a schematic software structure of an application server according to an embodiment of the present application.
Fig. 8 is a schematic software structure of a third party server according to an embodiment of the present application.
Fig. 9 is a schematic diagram of a display method according to an embodiment of the present application.
Fig. 10 (a) to (b) are schematic diagrams of a user interface according to an embodiment of the present application.
Fig. 11 is a schematic diagram of a system architecture of a fast application according to an embodiment of the present application.
Fig. 12 is a schematic diagram of another display method according to an embodiment of the application.
Detailed Description
In describing embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
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 application belongs. The terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. It should be understood that in the present application, unless otherwise indicated, "a plurality" means two or more than two.
In the prior art, an electronic device may display a quick application page written using UI components in a quick application specification. For example, as shown in fig. 1 (a), the quick application page 100 may be a page of a mixed layout of an Image (picture) component and a Text (Text) component. Wherein the first picture and the first text may be at a first div (block) 101 of the fast application page 100. The second text, the second picture, and the third text may be in a second tile 102 of the quick application page 100. The code of the fast application page of fig. 1 (a) may be, for example:
The quick application 200 may render the quick application pages through JS (JavaScript) framework 201, template engine 202, and rendering engine 203, as shown in fig. 1 (b). The JS frame 201 is configured to parse codes corresponding to the quick application pages written by the program developer to generate a virtual DOM. The template engine 202 is used to build DOM (Document Object Model ) instructions from the virtual DOM. The template engine 202 is also known as VDOM (Virtual Document Object Model ) engine. Rendering engine 203 is used to display the fast application page according to DOM instructions.
In the prior art, with the rich media expansion requirements, a card component labeled "qcard" may be embedded in the code of the fast application page to embed a card 301 in the fast application page 300, as shown in fig. 2. The code of the fast application page of fig. 2 may be, for example:
when the quick application renders the quick application page shown in fig. 2, the card assembly labeled "qcard" cannot be identified, so that the quick application page cannot be displayed.
In view of the above, the embodiment of the application provides a display method capable of presenting a card.
Fig. 3 is a schematic diagram of a display system according to an embodiment of the application. Display system 400 may include a development device 410, an application server 420, an electronic device 430, and a third party server 440.
The development device 410 may be, for example, a mobile phone, a tablet computer, a digital camera, a Personal Digital Assistant (PDA), a wearable device, a laptop computer (laptop), etc., and the tablet computer is exemplified in fig. 3. The development device 410 may include an integrated development environment (INTEGRATED DEVELOPMENT ENVIRONMENT, IDE). IDE is an application software that assists program developers in developing software, and within the development tool, source code text can be written in an assisted manner, and compiled and packaged into a usable program, some of which can also be designed with graphical interfaces. A program developer may write source code for a quick application via the development device 410. After the source code of the quick application is written, the development device 410 may generate application packages of the quick application according to the source code, and upload the application packages to the application server 420 for downloading by the user. The application package is a set of self-decompressed files, and files required by running the quick application, such as source codes displayed on the front page of the quick application, can be resolved.
The application server 420 may receive and store application packages of the quick applications uploaded by the development device 410, and provide download services of the quick application packages for the electronic device 430. Specifically, the application server 420 may receive a download request sent by the electronic device 430, where the download request includes an identifier of the fast application. The application server 420 may send an application package for the fast application to the electronic device 430 based on the identity of the fast application.
The electronic device 430 may be, for example, at least one of a mobile phone, a foldable electronic device, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a Personal Digital Assistant (PDA), a wearable device, an in-vehicle device, or a smart home device, such as a mobile phone in fig. 3. A user may download an application package for a fast application from application server 420 via electronic device 430.
The third party server 440 may provide a third party DSL page interpreter for the fast application. The third party DSL page interpreter is an interpreter developed by the third party server 440 that can be used to interpret specifications used when writing the third party DSL page. The number of third party servers 440 may be one or more, and different third party servers 440 may provide different third party DSL page interpreters, the number of third party servers 440 being one example in fig. 3. During the fast application initialization process, the electronic device 430 may obtain the third party DSL page interpreter from the third party server 440 and register the third party DSL page interpreter. In some embodiments, the third party DSL page interpreter may be a third party card interpreter. The third party DSL page interpreter is an interpreter developed by the third party server 440 that can be used to interpret the specifications used in writing the third party card.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device 430 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.
It should be understood that the illustrated structure of the embodiments of the present application does not constitute a particular limitation of the electronic device 430. In other embodiments of the application, electronic device 430 may include more or fewer components than shown, or may combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural-Network Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors 110.
The processor 110 may generate operation control signals according to the instruction operation code and the timing signals to complete instruction fetching and instruction execution control.
A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 may be a cache memory. The memory may hold instructions or data that are used or used more frequently by the processor 110. If the processor 110 needs to use the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.
In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others. The processor 110 may be connected to the touch sensor, the audio module, the wireless communication module, the display, the camera, etc. module through at least one of the above interfaces.
It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and is not meant to limit the structure of the electronic device 430. In other embodiments of the present application, the electronic device 430 may also use different interfaces in the above embodiments, or a combination of interfaces.
The USB interface 130 is an interface conforming to the USB standard, and may be used to connect a display device and a peripheral device, specifically, a Mini USB interface, a Micro USB interface, a USB Type C interface, etc.
The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 430. The charging management module 140 may also provide power to the electronic device 430 through the power management module 141 while charging the battery 142.
The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.
The wireless communication function of the electronic device 430 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.
The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 430 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied on the electronic device 430. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.
The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.
The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), bluetooth (BT), bluetooth low energy (bluetooth low energy, BLE), ultra Wide Band (UWB), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near field communication (NEAR FIELD communication, NFC), infrared (IR), etc., applied on the electronic device 430. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.
In some embodiments, antenna 1 and mobile communication module 150 of electronic device 430 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 430 may communicate with networks and other electronic devices through wireless communication techniques. The wireless communication techniques can include a global system for mobile communications (global system for mobile communications, GSM), general packet radio service (GENERAL PACKET radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation SATELLITE SYSTEM, GLONASS), a beidou satellite navigation system (beidou navigation SATELLITE SYSTEM, BDS), a quasi zenith satellite system (quasi-zenith SATELLITE SYSTEM, QZSS) and/or a satellite based augmentation system (SATELLITE BASED AUGMENTATION SYSTEMS, SBAS).
The electronic device 430 may implement display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD) CRYSTAL DISPLAY, an organic light-emitting diode (OLED), an active-matrix organic LIGHT EMITTING diode (AMOLED), a flexible light-emitting diode (FLED), miniled, microLed, micro-oLed, a quantum dot LIGHT EMITTING diode (QLED), or the like. In some embodiments, the electronic device 430 may include 1 or more display screens 194.
The electronic device 430 may implement camera functions through a camera 193, isp, video codec, GPU, display 194, and application processor AP, neural network processor NPU, etc.
The camera 193 may be used to acquire color image data of a photographing object as well as depth data. The ISP may be used to process color image data acquired by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, so that the electrical signal is converted into an image visible to the naked eye. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.
The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 430. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions.
The internal memory 121 may be used to store computer executable program code that includes instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 430 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional methods or data processing of the electronic device 430 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.
The electronic device 430 may implement audio functions through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, and application processor, among others. Such as music playing, recording, etc.
The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.
The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 430 may listen to music through the speaker 170A or output an audio signal for hands-free calling.
A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When the electronic device 430 picks up a phone call or voice message, the voice can be picked up by placing the receiver 170B close to the human ear.
Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals.
The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.
The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.
The keys 190 may include a power on key, a volume key, etc.
The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback.
The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.
The SIM card interface 195 is used to connect a SIM card.
Fig. 5 is a schematic diagram of a logic structure of an electronic device according to an embodiment of the application.
The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into five layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android runtime, ART) and native C/c++ libraries, a hardware abstraction layer (Hardware Abstract Layer, HAL), and a kernel layer, respectively. It will be appreciated that the Android system is illustrated herein, and in other operating systems (e.g., hong-mong system, IOS system, etc.), the scheme of the present application can be implemented as long as the functions implemented by the respective functional modules are similar to those implemented by the embodiments of the present application.
The application layer may include a series of application packages.
As shown in fig. 5, the application package may include applications such as cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, quick applications, etc.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.
As shown in FIG. 5, the application framework layer may include a window manager, a content provider, a view system, a resource manager, a notification manager, an activity manager, an input manager, and so forth.
The Window manager provides a Window management service (Window MANAGER SERVICE, WMS), and WMS may be used for Window management, window animation management, surface management, and as a transfer station for an input system.
The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.
The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.
The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.
The activity manager may provide an activity management service (ACTIVITY MANAGER SERVICE, AMS), and the AMS may be used for system component (e.g., activity, service, content provider, broadcast receiver) start-up, handoff, scheduling, and application process management and scheduling tasks.
The Input manager may provide an Input management service (Input MANAGER SERVICE, IMS) and the IMS may be used to manage inputs to the system, such as touch screen inputs, key inputs, sensor inputs, etc. The IMS retrieves events from the input device node and distributes the events to the appropriate windows through interactions with the WMS.
The android runtime includes a core library and An Zhuoyun rows. The android runtime is responsible for converting source code into machine code. Android runtime mainly includes employing Advanced Or Time (AOT) compilation techniques and Just In Time (JIT) compilation techniques.
The core library is mainly used for providing the functions of basic Java class libraries, such as basic data structures, mathematics, IO, tools, databases, networks and the like. The core library provides an API for the user to develop the android application.
The native C/c++ library may include a plurality of functional modules. For example: surface manager (surface manager), media Framework (Media Framework), libc, openGL ES, SQLite, webkit, etc.
The surface manager is used for managing the display subsystem and providing fusion of 2D and 3D layers for a plurality of application programs. Media frames support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc. OpenGL ES provides for drawing and manipulation of 2D graphics and 3D graphics in applications. SQLite provides a lightweight relational database for applications of the electronic device 100.
The hardware abstraction layer runs in a user space (user space), encapsulates the kernel layer driver, and provides a call interface to the upper layer.
The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.
Fig. 6 is a schematic software structure diagram of a development device according to an embodiment of the application. The development device 410 may include a packaging module 411 and an upload module 412. The packaging module 411 may receive a source program (or referred to as source code) of a quick application written by a program developer, and generate an application package of the quick application according to the source program. The source program of the quick application may include a source program of the quick application written by a program developer according to a UI component in the quick application specification. The source program of the quick application can be embedded with a card component with a label comprising 'plg-', for example, the label of the card component is 'plg-qcard') when < plg-qcard url = 'xxx' data= 'xxx' >/plg-qcard >. The upload module 412 may send the generated application package to an application server.
Fig. 7 is a schematic software structure diagram of an application server according to an embodiment of the present application. The application server 420 may include an application package storage module 421 and a delivery module 422. The application package storage module may be configured to store an application package sent by the development device to the application server. The downloading module can be used for receiving a downloading request sent by the electronic equipment and responding to the downloading request to send an application package to the electronic equipment. Wherein the application package is an application package of a quick application generated according to a source program of a card assembly embedded with a 'plg-' tag. In some embodiments, the issuing module may select an application packet to be sent from the application packet storage module according to the application identifier in the download request.
Fig. 8 is a schematic software structure diagram of a third party server according to an embodiment of the present application. The third party server 440 may include a third party DSL page interpreter storage module 441 and a delivery module 442. The third party DSL page interpreter storage module 441 is operable to store the third party DSL page interpreter. The issuing module 442 may be configured to receive an upgrade request sent by an electronic device, and send a third party DSL page interpreter to the electronic device in response to the upgrade request.
For convenience of understanding, the following embodiments of the present application will take an electronic device having a structure shown in fig. 4-5, a development device having a structure shown in fig. 6, an application server having a structure shown in fig. 7, and a third party server having a structure shown in fig. 8 as examples, and specifically describe a display method provided by the embodiments of the present application in conjunction with the accompanying drawings and application scenarios.
Fig. 9 is a schematic diagram of a display method according to an embodiment of the application. The display method is used for a first scene. The first scenario is a third party DSL page interpreter registering with a template engine of the fast application. The display method comprises the following steps:
S901: the third party DSL page interpreter registers with the template engine of the fast application.
In some embodiments, the template engine of the fast application may be upgraded such that the template engine of the fast application may provide services that enable the third party DSL page interpreter to apply, including providing a plug-in interface such that the third party DSL page interpreter may register with the template engine of the fast application. So that the third party DSL page interpreter can interact data with the template engine. The third party DSL page interpreter must rely on the template engine to function itself, and the third party DSL page interpreter cannot normally operate. Conversely, the template engine does not need to rely on a third party DSL page interpreter to operate. In this way, the third party DSL page interpreter can be loaded onto the fast-applied template engine and dynamically updated without any changes to the fast-applied template engine.
In some embodiments, at the time of the update, the quick application may send a download request to the third party server based on the published update. The third party server can acquire the corresponding third party DSL page interpreter from the third party DSL page interpreter storage module according to the downloading request, and send the third party DSL page interpreter to the quick application through the issuing module. The fast application may install the third party DSL page interpreter onto the electronic device through a plug-in interface provided by a template engine of the fast application such that the third party DSL page interpreter is integrated on the template engine. The express application also generates an address table from the registered third party DSL page interpreter. The address table may be stored on the electronic device. The address table records the third party DSL page interpreter name and the corresponding installation address. The third party DSL page interpreter names are the names of the interpreters developed by the third party server 440, and the interpreters developed by the third party server 440 can be used to interpret the specifications used in writing the third party DSL page. The third party DSL page interpreter name is used to identify the third party DSL page interpreter. In some embodiments, all third party DSL page interpreter names registered with the template engine of the quick application include "plg-". Different third party DSL page interpreters are not named the same. Different third party DSL page interpreters can identify different cards. The third party DSL page interpreter name may be, for example, "plg-qcard". The installation address is used for the third party DSL page interpreter to load automatically when the fast application is running.
It will be appreciated that the express application may also register a third party DSL page interpreter into the template engine of the express application in other cases of the express application, as the application is not limited in this regard.
S902: the JS framework of the quick application acquires an application package of the quick application acquired from an application server; the application package of the quick application is an application package obtained by an application server from a development device, and is an application package generated by the development device according to a source program of a card component embedded with a 'plg-' tag written by a program developer.
In some embodiments, the user may launch the quick application and the JS framework of the quick application may obtain the application package of the quick application obtained from the application server. For example, the electronic device displays a main interface 1010 as shown in fig. 10 (a). In fig. 10 (a), the main interface 1010 may include a quick application icon 1011. It will be appreciated that (a) in fig. 10 is an example of a main interface 1010, and the present application is not limited to the content and form of the main interface 1010. The user may click on the quick application icon 1011 as shown in fig. 10 (a). In response to clicking on the quick application icon, the electronic device may send a download request to the application server. The application server may send an application package of the fast application to the electronic device in response to the download request. The electronic device can send the application package of the quick application acquired from the application server to the JS frame of the quick application. It is understood that the fast application may be started in other manners, for example, automatically starting the fast application after the update is completed, which is not limited by the present application.
In some embodiments, a card component labeled "plg-" may include, for example, an Image component and a Text component, and the code of the card component labeled "plg-" may be, for example: < plg-qcard url = "xxx" data= "xxx" >/plg-qcard >.
S903: the JS framework of the quick application interprets the application package of the quick application as a first virtual DOM and a second virtual DOM.
When the JS framework of the quick application interprets an application package of the quick application, if the JS framework of the quick application is a first source code written according to a UI component in a quick application specification, the JS framework of the quick application interprets the first source code as a first virtual DOM; if the second source code is the "plg-" tag, the JS framework of the quick application interprets the second source code as a second virtual DOM. The second source code of the "plg-" tag may be, for example: < plg-qcard url = "xxx" data= "xxx" >/plg-qcard >. The first virtual DOM is a virtual DOM recognizable by a template engine of the fast application. The second virtual DOM is a virtual DOM unrecognizable by the template engine of the fast application and is a virtual DOM recognizable by the corresponding third party DSL page interpreter. The prefix node of the second virtual DOM may include "plg-", e.g., "plg-qcard". The second virtual DOM may be, for example: < plg-qcard url = "xxx" data= "xxx" >/plg-qcard > ().
S904: the JS framework of the quick application sends the first virtual DOM and the second virtual DOM to the template engine of the quick application.
S905: the template engine of the quick application identifies a second virtual DOM whose prefix node includes "plg", and automatically loads a corresponding third party DSL page interpreter according to the prefix node of the second virtual DOM.
The third party DSL page interpreter may be registered in advance with the template engine of the fast application and recorded in an address table, so that, when the template engine of the fast application identifies a second virtual DOM whose prefix node includes "plg", the address table may be queried to determine a target third party DSL page interpreter name matching the prefix node of the second virtual DOM, and determine an installation address corresponding to the target third party DSL page interpreter name according to the address table. For example, the prefix node of the second virtual DOM is "plg-qcard", the address table records the third party DSL page interpreter name "plg-qcard" and the corresponding installation address "ABCD", and the template engine of the quick application may query the address table to determine the target third party DSL page interpreter name "plg-qcard" that matches the prefix node "plg-qcard" of the second virtual DOM, and determine the installation address "ABCD" corresponding to the target third party DSL page interpreter name "plg-qcard" according to the address table. The template engine of the fast application can also determine a corresponding third party DSL page interpreter according to the installation address, and automatically load the corresponding third party DSL page interpreter. Thus, a subsequent third party DSL page interpreter can interact data with the template engine.
S906: the template engine of the fast application sends the second virtual DOM to the corresponding third party DSL page interpreter.
In some embodiments, the template engine of the fast application sends the second virtual DOM "< plg-qcard url =" xxx "data=" xxx ">/plg-qcard > ()" to the corresponding third party DSL page interpreter.
S907: the third party DSL page interpreter interprets the second virtual DOM as a third virtual DOM that meets the fast application specification.
The third party DSL page interpreter interpreting the second virtual DOM as a third virtual DOM compliant with the fast application specification may be, for example: the third party DSL page interpreter interprets the second virtual DOM as a third virtual DOM comprising text and image. Specifically: the third party DSL page interpreter may interpret < plg-qcard url = "xxx" data= "xxx" >/plg-qcard > ():
<text>this is dsl text</text>
<image src="…/path/to/dsl/image.bmp"></image>。
Thus, the template engine of the fast application can identify the third virtual DOM.
S908: the third party DSL page interpreter sends a third virtual DOM to the template engine of the fast application.
S909: the template engine of the fast application interprets the first virtual DOM and the third virtual DOM to construct DOM instructions.
S910: the template engine of the fast application sends DOM instructions to the rendering engine of the fast application.
S911: and the rendering engine of the quick application displays the quick application page embedded with the card according to the DOM instruction.
The rendering engine of the fast application displays the fast application page 1020 with the card embedded according to the DOM instructions as shown in fig. 10 (b). In fig. 10 (b), the quick application page 1020 may include a card 1021. It will be appreciated that (b) in fig. 10 is an example of a fast application page 1020, and the present application is not limited to the content and form of the fast application page 1020.
Please refer to fig. 11, which is a schematic diagram of a system architecture of a fast application according to an embodiment of the present application. The quick application 1100 includes a JS framework 1101 of the quick application, a template engine 1102 of the quick application, a third-party DSL page interpreter 1103, and a rendering engine 1104 of the quick application. The JS frame 1101 of the quick application can acquire an application package of the quick application acquired from the application server. The application package of the fast application is obtained from the development device for the application server. The application package is generated for the development device according to the source code of the quick application written by the program developer. The source code has embedded therein a card assembly whose tag includes "plg-", i.e. a code that includes a third party DSL. Third party DSL refers to content provided by a third party server that is not a fast application. The JS frame 1101 of the fast application can interpret the application package of the fast application as a virtual DOM including the first virtual DOM and the second virtual DOM, and send the virtual DOM including the first virtual DOM and the second virtual DOM to the template engine 1102 of the fast application. The fast-application template engine 1102 may identify a second virtual DOM whose prefix node includes "plg" and automatically load a corresponding third party DSL page interpreter 1103 according to the prefix node of the second virtual DOM. The fast application template engine 1102 may also send a second virtual DOM employing a third party DSL specification to the corresponding third party DSL page interpreter 1103. The third party DSL specification refers to a specification used when writing the third party DSL page. The third party DSL page interpreter 1103 can interpret the second virtual DOM as a third virtual DOM that meets the fast application specification and send the third virtual DOM to the template engine 1102 of the fast application. Template engine 1102 of the fast application may interpret the first virtual DOM and the third virtual DOM to build DOM instructions. The template engine of the fast application may send DOM instructions to the rendering engine 1104 of the fast application. The fast application rendering engine 1104 may display the fast application page with the card embedded according to the DOM instructions.
It is understood that steps S905-S908 may be performed simultaneously with the template engine of the fast application interpreting the first virtual DOM, or may be performed after the template engine of the fast application interprets the first virtual DOM, then step S909 may interpret the third virtual DOM for the fast application, and combine the result of interpreting the first virtual DOM with the structure of interpreting the third virtual DOM to construct DOM instructions, which the present application is not limited to.
It can be appreciated that the display method can identify not only cards of the Image component and Text component mixed layout, but also cards of other component mixed layout, and the application is not limited thereto.
It may be appreciated that in step S901, the template engine of the fast application may omit providing a plug-in interface for enabling the third party DSL page interpreter to apply, and when updating, the fast application may acquire codes from the cloud server according to the issued update to form a plug-in interface for enabling the third party DSL page interpreter to apply, so that the third party DSL page interpreter may be installed on the electronic device, so that the third party DSL page interpreter may be integrated on the template engine, which is not limited in this aspect of the present application.
It will be appreciated that the display method may be used not only for the first scenario described above, but also for the second scenario. The second scenario is that the third party DSL page interpreter registers to the JS frame of the fast application. The display method is different in the second scene from the first scene in that:
In a second scenario, the third party DSL page interpreter is a JS framework registered with the express application. The process of registering the third party DSL page interpreter with the JS frame of the fast application is similar to the process of registering the third party DSL page interpreter with the template engine of the fast application in fig. 9, and will not be described again here. When the JS framework of the quick application interprets the application package of the quick application, the second source code including plg-' in the application package is identified, and a corresponding third-party DSL page interpreter is automatically loaded according to the label of the second source code. The process of automatically loading the corresponding third party DSL page interpreter by the JS frame of the fast application according to the tag of the second source code is similar to the process of automatically loading the corresponding third party DSL page interpreter by the template engine of the fast application in fig. 9 according to the prefix node of the second virtual DOM, which is not described herein again. The JS framework of the express application also sends the card component whose tag includes "plg-" to the corresponding third-party DSL page interpreter.
The third party DSL page interpreter interprets the card assembly whose tag includes "plg-" as a third source code that complies with the quick application specification. The process of the third party DSL page interpreter interpreting the card component whose tag includes "plg-" as the third source code that conforms to the fast application specification is similar to the process of the third party DSL page interpreter interpreting the second virtual DOM as the third virtual DOM that conforms to the fast application specification in fig. 9, and will not be repeated here. The third party DSL page interpreter can also send a third source code to the JS frame of the express application. The JS framework of the quick application can interpret the first source code and the third source code as a virtual DOM, and send the virtual DOM to the template engine of the quick application. The template engine of the quick application may interpret the virtual DOM to build DOM instructions. And sends the DOM instructions to the rendering engine of the fast application. The rendering engine of the fast application may display the fast application page with the card embedded according to the DOM instructions.
Fig. 12 is a schematic diagram of another display method according to an embodiment of the application. The display method comprises the following steps:
s1201: acquiring an application package of an application program acquired from an application server; the application package comprises first information, wherein the first information is information of a card; the card information is information of non-application specifications.
S1202: automatically loading a third party card interpreter according to the first information; the third party card interpreter is integrated in the application.
S1203: the first information is interpreted by a third party card interpreter as second information conforming to the application specification.
S1204: and displaying the card according to the second information.
In some embodiments, the application package further includes third information, the third information being information of the application program; the method further comprises the steps of: interpreting the second information and the third information as fourth information; the fourth information is a virtual DOM or DOM instruction; and displaying the page of the application program according to the fourth information, wherein the page of the application program comprises a card.
In some embodiments, the first information includes third party identification information, where the third party identification information refers to identification information corresponding to content provided by a third party server of the non-fast application; automatically loading the third party card interpreter according to the first information comprises: identifying the first information according to the third party identification information; and automatically loading the third-party card interpreter according to the identified first information.
In some embodiments, the third party identification information may be, for example, "plg-".
In some embodiments, prior to acquiring the application package of the application program acquired from the application server, the method further comprises: the third party card interpreter is registered with the application.
In some embodiments, registering the third party card interpreter with the application comprises: providing a plug-in interface through a JS framework of an application program; and registering the third-party card interpreter to the JS framework through the plug-in interface.
In some embodiments, registering the third party card interpreter with the application comprises: providing a plug-in interface through a template engine of an application program; the third party card interpreter is registered with the template engine through the plug-in interface.
In some embodiments, the first information comprises tag information comprising third party identification information; the method further comprises the steps of: storing an address table, wherein the address table records unique identifiers of one or more registered third-party card interpreters and installed address information; the installed address information is used for determining a third party card interpreter; automatically loading the third party card interpreter according to the first information comprises: determining a corresponding third-party card interpreter according to the label information in the first information and the address table; and automatically loading a third party card interpreter.
In some embodiments, the tag information may be, for example, "plg-qcard".
In addition to the above method and the terminal device, the embodiment of the present application further provides a computer readable storage medium, where a program is stored in the computer readable storage medium, and the program causes the electronic device to implement the above display method.
A computer program product comprising computer-executable instructions stored on a computer-readable storage medium; the at least one processor of the electronic device may read computer-executable instructions from a computer-readable storage medium, the at least one processor executing the computer-executable instructions causing the electronic device to perform the display method described above.
The scheme is that an application package of an application program obtained from an application server is obtained; the application package comprises first information, wherein the first information is information of a card; the information of the card is information of non-application program specifications; automatically loading a third party card interpreter according to the first information; the third party card interpreter is integrated in the application program; interpreting the first information into second information conforming to the application program specification by a third party card interpreter; the card may be presented according to the second information display card.
From the above description of the embodiments, it will be apparent to those skilled in the art that the present application may be implemented by means of software plus necessary general purpose hardware, or of course by means of special purpose hardware including application specific integrated circuits, special purpose CPUs, special purpose memories, special purpose components, etc. Generally, functions performed by computer programs can be easily implemented by corresponding hardware, and specific hardware structures for implementing the same functions can be varied, such as analog circuits, digital circuits, or dedicated circuits. But a software program implementation is a preferred embodiment for many more of the cases of the present application. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a readable storage medium, such as a floppy disk, a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk or an optical disk of a computer, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments of the present application.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may 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 instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be stored by a computer or data storage devices such as servers, data centers, etc. that contain an integration of one or more available media. Usable media may be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state disk (Solid STATE DISK, SSD)), etc.
Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present application and not for limiting the same, and although the present application has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made to the technical solution of the present application without departing from the spirit and scope of the technical solution of the present application.

Claims (10)

1. A display method applied to an electronic device, the method comprising:
acquiring an application package of an application program acquired from an application server; the application package comprises first information, wherein the first information is information of a card; the information of the card is information of non-application program specifications;
Automatically loading a third party card interpreter according to the first information; the third party card interpreter is integrated in the application program;
interpreting, by the third party card interpreter, the first information as second information conforming to an application specification;
and displaying the card according to the second information.
2. The method of claim 1, wherein the application package further includes third information, the third information being information of the application program; the method further comprises the steps of:
Interpreting the second information and the third information as fourth information; the fourth information is a virtual DOM or DOM instruction;
and displaying the page of the application program according to the fourth information, wherein the page of the application program comprises the card.
3. The method of claim 1, wherein the first information comprises third party identification information; the automatically loading a third party card interpreter according to the first information comprises:
Identifying the first information according to the third party identification information;
And automatically loading a third-party card interpreter according to the identified first information.
4. A method according to any one of claims 1 to 3, wherein prior to said retrieving an application package of an application program retrieved from an application server, the method further comprises:
registering the third party card interpreter with the application.
5. The method of claim 4, wherein the registering the third party card interpreter with the application program comprises:
Providing a plug-in interface through a JS framework of the application program;
and registering the third-party card interpreter to the JS framework through the plug-in interface.
6. The method of claim 4, wherein the registering the third party card interpreter with the application program comprises:
providing a plug-in interface through a template engine of the application program;
Registering the third party card interpreter with the template engine through the plug-in interface.
7. The method of claim 4, wherein the first information comprises tag information, the tag information comprising third party identification information;
The method further comprises the steps of:
Storing an address table recording unique identifiers of one or more third party card interpreters registered and installed address information; the installed address information is used for determining the third party card interpreter;
the automatically loading a third party card interpreter according to the first information comprises:
Determining a corresponding third-party card interpreter according to the label information in the first information and the address table;
and automatically loading the third party card interpreter.
8. An electronic device comprising a processor and a memory for storing program instructions, the processor implementing the display method according to any one of claims 1 to 7 when the memory instructions are invoked by the processor.
9. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a program that causes an electronic device to implement the display method according to any one of claims 1 to 7.
10. A computer program product, the computer program product comprising computer-executable instructions stored on a computer-readable storage medium; at least one processor of an electronic device may read the computer-executable instructions from the computer-readable storage medium, the execution of the computer-executable instructions by the at least one processor causing the electronic device to perform the display method of any one of claims 1 to 7.
CN202211371981.1A 2022-11-03 2022-11-03 Display method, electronic device, storage medium, and program product Pending CN118034823A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211371981.1A CN118034823A (en) 2022-11-03 2022-11-03 Display method, electronic device, storage medium, and program product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211371981.1A CN118034823A (en) 2022-11-03 2022-11-03 Display method, electronic device, storage medium, and program product

Publications (1)

Publication Number Publication Date
CN118034823A true CN118034823A (en) 2024-05-14

Family

ID=90993777

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211371981.1A Pending CN118034823A (en) 2022-11-03 2022-11-03 Display method, electronic device, storage medium, and program product

Country Status (1)

Country Link
CN (1) CN118034823A (en)

Similar Documents

Publication Publication Date Title
EP4002108B1 (en) Application start method and electronic device
CN112291764B (en) Content connection system
WO2022078295A1 (en) Device recommendation method and electronic device
WO2021052167A1 (en) Method for realizing pluginization of application, and electronic apparatus
US20230214201A1 (en) Method and System for Obtaining Download Information of Application, Server, and Storage Medium
WO2021104259A1 (en) Method and terminal for data sharing between fast application and native application
CN116009977A (en) Notification processing method, chip, electronic device and computer-readable storage medium
WO2022253158A1 (en) User privacy protection method and apparatus
CN116483734B (en) Pile inserting method and system based on compiler and related electronic equipment
CN112328330A (en) iOS component calling method, device, middleware, electronic equipment and medium
CN115309431B (en) Parameter updating method, readable medium and electronic equipment
WO2023005711A1 (en) Service recommendation method and electronic device
WO2022111664A1 (en) Patching method, related apparatus, and system
US20240095015A1 (en) Upgrade prompt method, terminal device, and computer-readable storage medium
CN116795435A (en) Compatibility management and control method and related equipment
CN115203716A (en) Permission synchronization method, related device and system
CN118034823A (en) Display method, electronic device, storage medium, and program product
CN115599565A (en) Method and device for sending clipboard data
WO2022194010A1 (en) Application program sharing method and application program sharing apparatus
CN116662270B (en) File analysis method and related device
WO2024041367A1 (en) Advertisement display method, and terminal, server and system
WO2023134525A1 (en) Appearance setting method and electronic device
CN117851617A (en) Display method, electronic device, storage medium, and program product
CN117689796A (en) Rendering processing method and electronic equipment
CN117729561A (en) System upgrading method, terminal and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination