WO2023245374A1 - 视图显示方法、装置、电子设备和存储介质 - Google Patents
视图显示方法、装置、电子设备和存储介质 Download PDFInfo
- Publication number
- WO2023245374A1 WO2023245374A1 PCT/CN2022/099938 CN2022099938W WO2023245374A1 WO 2023245374 A1 WO2023245374 A1 WO 2023245374A1 CN 2022099938 W CN2022099938 W CN 2022099938W WO 2023245374 A1 WO2023245374 A1 WO 2023245374A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- update
- node
- display data
- view
- update information
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000009471 action Effects 0.000 claims description 32
- 230000004048 modification Effects 0.000 claims description 31
- 238000012986 modification Methods 0.000 claims description 31
- 230000006870 function Effects 0.000 claims description 29
- 238000012217 deletion Methods 0.000 claims description 20
- 230000037430 deletion Effects 0.000 claims description 20
- 238000012546 transfer Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 abstract description 12
- 230000008569 process Effects 0.000 abstract description 9
- 238000009877 rendering Methods 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Definitions
- the present disclosure relates to the technical field of view display, and specifically to a view display method, device, electronic device and storage medium.
- wearable devices have also made great progress, with increasingly rich functions and superior performance.
- the hardware of wearable devices is relatively simple, such as small memory, so the applications running on wearable devices are mostly fast applications.
- the MVVM (Model-View-ViewModel) update mechanism can be used to bind data to UI views.
- a large amount of memory will be occupied during the view update process, causing the wearable device's view update to be delayed or even stuck.
- embodiments of the present disclosure provide a view display method, device, electronic device and storage medium to solve the defects in the related technology.
- a view display method including:
- obtaining update information of display data includes:
- each update function is used to obtain update information of data corresponding to a node of the DOM Tree.
- obtaining update information of display data includes:
- the listening function detects changes in the display data
- the update information of the display data is obtained.
- obtaining update information of display data includes:
- it also includes:
- the acquisition of all update information of display data in a view update scenario includes:
- Modifying at least one node of the DOM Tree corresponding to the display data based on the updated information includes:
- At least one node of the DOM Tree corresponding to the display data is modified according to the update information in the first cache area.
- modifying at least one node of the DOM Tree corresponding to the display data according to the update information includes:
- the node will be deleted after other modification actions on the node are completed.
- the node when there is a deletion action on a certain node in the update information, after other modification actions on the node are completed, the node is deleted, including:
- At least one node corresponding to the information in the second cache area is deleted.
- a view display device including:
- a patch module configured to modify at least one node of the DOM Tree corresponding to the display data according to the update information, and generate a patch file based on the modification content of the at least one node;
- the update module is used to render and update the local content in the current view based on the patch file to obtain the target view.
- the acquisition module is specifically used to:
- each update function is used to obtain update information of data corresponding to a node of the DOM Tree.
- the acquisition module is specifically used to:
- the listening function detects changes in the display data
- the update information of the display data is obtained.
- the acquisition module is specifically used to:
- a marking module is also included for:
- the acquisition module is specifically used for:
- the patch module is used to modify at least one node of the DOM Tree corresponding to the display data based on the update information, and is specifically used for:
- At least one node of the DOM Tree corresponding to the display data is modified according to the update information in the first cache area.
- the patch module is used to modify at least one node of the DOM Tree corresponding to the display data based on the update information, specifically for:
- the node will be deleted after other modification actions on the node are completed.
- the patch module is used to delete the node after other modification actions on the node are completed when there is a deletion action on a certain node in the update information.
- At least one node corresponding to the information in the second cache area is deleted.
- an electronic device includes a memory and a processor.
- the memory is used to store computer instructions executable on the processor.
- the processor is used to execute the The computer instructions are based on the view display method described in the first aspect.
- a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method described in the first aspect is implemented.
- the view display method provided by the present disclosure by obtaining the update information of the display data, can modify at least one node of the DOM Tree corresponding to the display data according to the update information, and modify the content of the at least one node according to the modification content Generate a patch file, and finally render and update the local content in the current view based on the patch file. Since only some nodes of the DOM Tree are modified in this process, the memory usage during the view update process can be reduced, especially in the related technology, when the display data is updated, it is avoided to obtain all the display data and generate another DOM accordingly.
- the memory usage caused by Tree method can improve the efficiency and smoothness of view updates of wearable devices.
- Figure 1 is a flow chart of a view display method according to an exemplary embodiment of the present disclosure
- Figure 2 is a flowchart of a view display method illustrating another exemplary embodiment of the present disclosure
- Figure 3 is a schematic structural diagram of a view display device according to an exemplary embodiment of the present disclosure.
- FIG. 4 is a structural block diagram of an electronic device according to an exemplary embodiment of the present disclosure.
- first, second, third, etc. may be used in this disclosure to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
- first information may also be called second information, and similarly, the second information may also be called first information.
- word “if” as used herein may be interpreted as "when” or “when” or “in response to determining.”
- a DOM Tree Document Object Model Tree
- This DOM Tree also corresponds to the display view of the wearable device.
- the new DOM Tree is partially The nodes are the same, but some nodes are different, so the patch file can be generated by comparing the two DOM Trees, and the view can be updated based on the patch file. Since each time the view is updated, two DOM Trees need to be saved in the memory at the same time, and the system memory of wearable devices is small, so problems such as view switching lags often occur.
- At least one embodiment of the present disclosure provides a view display method. Please refer to FIG. 1 , which shows the flow of the method, including step S101 and step S103.
- this method can be applied to the display view update process of wearable devices such as smart watches and smart bracelets.
- the display view of the wearable device may be the interface of the operating system, the UI interface of an application, etc.
- This method can be applied in a scenario where a program developer develops an application program on the operating system of the wearable device. That is, the program developer triggers a data update of the application program, and then this method can update the view based on the data update.
- step S101 update information of display data is obtained.
- the data of the application program includes data related to the view and data unrelated to the display view.
- the display data is the data related to the display view.
- the data of the application program can be data in the form of code or other forms of data.
- Display data and DOM Tree both correspond to the display view and are two format files that describe the content of the display view.
- the DOM Tree has multiple nodes in a tree structure, and each node corresponds to a certain local content in the display view.
- the display data has data corresponding to each node of the DOM Tree, and an update function can be set in advance for the data corresponding to each node.
- Each update function is used to obtain the update information of the data corresponding to a node of the DOM Tree, so In this step, the update information obtained by each update function in the display data can be obtained.
- an update function is set for the display data to obtain the update information of all the display data.
- an independent update function is set for the data corresponding to each node, which can obtain the information that occurs in the display data in a targeted manner. Data corresponding to the updated node.
- a listening function can also be set for the display data in advance, and the listening function is used to monitor whether the display data changes. Therefore, in this step, when the listening function detects changes in the display data, the update information of the display data can be obtained. For example, when the listening function detects changes in the display data, each update function is triggered to obtain the update information of the data corresponding to the node.
- all update information of the display data in the view update scenario can be obtained.
- View update scenarios can include life cycle callback scenarios, timer callback scenarios, asynchronous call scenarios, time callback scenarios, etc.
- the above-mentioned acquisition of all update information of display data in the view update scenario can obtain all display data in any of the above scenarios. Update information. This solves the problem of grouping update information when updating a single tree.
- an update start mark can be added to the operating system or application of the wearable device
- an update can be added to the operating system or application of the wearable device.
- End tag also delete the update start tag. Therefore, when the update start tag exists, the update information of the display data can be obtained, and the obtained update information can be cached in the first cache area to obtain all updates of the display data in the view update scenario. information.
- the corresponding start tag of the view update scenario can be added when each view update scenario starts, and at the end of each view update scenario, the corresponding view update scenario can be added. end tag.
- end tag For example, when the life cycle callback scenario starts, you can add the start tag of the life cycle callback scenario, and when the life cycle callback scenario ends, you can add the end tag of the life cycle callback scenario (and delete the start tag of the life cycle callback scenario).
- Multiple view update scenarios may overlap, that is, two or more view update scenarios may occur at the same time.
- each view update scenario has a corresponding first cache area. If there is a startup tag of a certain view update scenario, the update information of the display data can be obtained and the first cache corresponding to the view update scenario can be cached. district.
- step S102 modify at least one node of the DOM Tree corresponding to the display data according to the update information, and generate a patch file according to the modification content of the at least one node.
- the node modification content corresponding to the update information can be determined based on the mapping relationship between the update information and the node modification content of the DOM Tree. Therefore, at least one corresponding node can be modified according to the modification content, and the modification content can include multiple modifications to a node.
- an update start mark is added to the operating system or application of the wearable device, and when the view update scenario ends, the operating system or application of the wearable device is The program adds an update end tag (and removes an update start tag). Therefore, when the update end mark exists, at least one node of the DOM Tree corresponding to the display data can be modified according to the update information in the first cache area. It can be understood that if there are multiple view update scenes, when there is an update end mark corresponding to a certain view update scene, the display data can be updated according to the update information in the first cache area corresponding to the view update scene. At least one node of the corresponding DOM Tree is modified. In addition, after at least one node of the DOM Tree corresponding to the display data is modified, the update end mark can be deleted, thereby avoiding repeated modifications to the DOM Tree.
- the patch file can include modified nodes and the specific modification content of each node.
- the modification content can include multiple modification actions.
- step S103 the local content in the current view is rendered and updated according to the patch file to obtain the target view.
- the update information can include the deletion action for a certain node. In this case, the node will be deleted after other modification actions on the node are completed.
- the information related to the deletion action of the node can be transferred to the second cache area; according to the update information, at least one of the DOM Tree corresponding to the display data is After the node is modified, at least one node corresponding to the information in the second cache area is deleted.
- the information related to the deletion action of the node in the update information is transferred to the second cache area, and the deletion action is delayed, so that all affected components can be updated at once in the update order during a single tree update, and Solved the problem of crash caused by node deletion in advance.
- the view display method provided by the present disclosure by obtaining the update information of the display data, can modify at least one node of the DOM Tree corresponding to the display data according to the update information, and modify the content of the at least one node according to the modification content Generate a patch file, and finally render and update the local content in the current view based on the patch file.
- the present disclosure provides a new vdom update mechanism. Since only some nodes of the DOM Tree are modified during this process, the memory usage during the view update process can be reduced, and in particular, the acquisition of data when the display data is updated in related technologies is avoided. All the display data and the memory usage caused by generating another DOM Tree can improve the efficiency and smoothness of the wearable device's view update.
- Figure 2 shows the complete process of the view display method provided by the present disclosure. It can be seen from Figure 2 that when the display data (data) is modified, the listening function watcher monitors the change in the display data. , then the update function (update function) of the data corresponding to each node is triggered to obtain the update information of the data, and then the DOM Tree corresponding to the displayed data is modified based on the obtained update information, and then a patch file is generated based on the modified content. (patch), and finally the patch file is sent to the renderer (render) to render and update the local content in the current view according to the patch file to obtain the target view.
- the update function update function
- a view display device is provided. Please refer to FIG. 3.
- the device includes:
- Obtain module 301 used to obtain update information of display data
- the patch module 302 is used to modify at least one node of the DOM Tree corresponding to the display data according to the update information, and generate a patch file according to the modification content of the at least one node;
- the update module 303 is used to render and update the local content in the current view according to the patch file to obtain the target view.
- the acquisition module is specifically used to:
- each update function is used to obtain update information of data corresponding to a node of the DOM Tree.
- the acquisition module is specifically used to:
- the listening function detects changes in the display data
- the update information of the display data is obtained.
- the acquisition module is specifically used to:
- a marking module is also included for:
- the acquisition module is specifically used for:
- the patch module is used to modify at least one node of the DOM Tree corresponding to the display data based on the update information, and is specifically used for:
- At least one node of the DOM Tree corresponding to the display data is modified according to the update information in the first cache area.
- the patch module is used to modify at least one node of the DOM Tree corresponding to the display data based on the update information, specifically for:
- the node will be deleted after other modification actions on the node are completed.
- the patch module is used to delete a node after other modification actions on the node are completed when there is a deletion action on a node in the update information. Specifically used for:
- At least one node corresponding to the information in the second cache area is deleted.
- the device 400 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.
- the device 400 may include one or more of the following components: a processing component 402, a memory 404, a power supply component 406, a multimedia component 408, an audio component 410, an input/output (I/O) interface 412, a sensor component 414, and communications component 416.
- Processing component 402 generally controls the overall operations of device 400, such as operations associated with display, phone calls, data communications, camera program operations, and recording operations.
- the processing element 402 may include one or more processors 420 to execute instructions to complete all or part of the steps of the above method.
- processing component 402 may include one or more modules that facilitate interaction between processing component 402 and other components.
- processing component 402 may include a multimedia module to facilitate interaction between multimedia component 408 and processing component 402.
- Memory 404 is configured to store various types of data to support operations at device 400 . Examples of such data include instructions for any application or method operating on device 400, contact data, phonebook data, messages, pictures, videos, etc.
- Memory 404 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
- SRAM static random access memory
- EEPROM electrically erasable programmable read-only memory
- EEPROM erasable programmable read-only memory
- EPROM Programmable read-only memory
- PROM programmable read-only memory
- ROM read-only memory
- magnetic memory flash memory, magnetic or optical disk.
- Power component 406 provides power to various components of device 400 .
- Power components 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 400 .
- Multimedia component 408 includes a screen that provides an output interface between the device 400 and the user.
- the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
- the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may not only sense the boundary of the touch or sliding operation, but also detect the duration and pressure associated with the touch or sliding operation.
- multimedia component 408 includes a front-facing camera and/or a rear-facing camera. When the device 400 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data.
- Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
- Audio component 410 is configured to output and/or input audio signals.
- audio component 410 includes a microphone (MIC) configured to receive external audio signals when device 400 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 404 or sent via communication component 416 .
- audio component 410 also includes a speaker for outputting audio signals.
- the I/O interface 412 provides an interface between the processing component 402 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
- Sensor component 414 includes one or more sensors for providing various aspects of status assessment for device 400 .
- the sensor component 414 can detect the open/closed state of the device 400, the relative positioning of components, such as the display and keypad of the device 400, and the sensor component 414 can also detect a change in position of the device 400 or a component of the device 400. , the presence or absence of user contact with the device 400 , device 400 orientation or acceleration/deceleration and temperature changes of the device 400 .
- Sensor assembly 414 may also include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
- Sensor assembly 414 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
- the sensor component 414 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
- Communication component 416 is configured to facilitate wired or wireless communication between apparatus 400 and other devices.
- the device 400 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G or 5G or a combination thereof.
- the communication component 416 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
- the communications component 416 also includes a near field communications (NFC) module to facilitate short-range communications.
- NFC near field communications
- the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
- RFID radio frequency identification
- IrDA infrared data association
- UWB ultra-wideband
- Bluetooth Bluetooth
- apparatus 400 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the power supply method of the above electronic device.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGA field programmable Gate array
- controller microcontroller, microprocessor or other electronic components are implemented for executing the power supply method of the above electronic device.
- the present disclosure also provides a non-transitory computer-readable storage medium including instructions, such as a memory 404 including instructions.
- the instructions can be executed by the processor 420 of the device 400 to complete the above electronic tasks.
- the method of powering the device may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
视图显示方法、装置、电子设备和存储介质,该方法包括:获取显示数据的更新信息(S101);根据该更新信息,对显示数据对应的DOM Tree的至少一个节点进行修改,并根据该至少一个节点的修改内容,生成补丁文件(S102);根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图(S103)。由于该过程中仅对DOM Tree的部分节点进行修改,因此可以降低视图更新过程中的内存占用,尤其避免了相关技术中在显示数据更新时,获取全部的显示数据,并据此生成另一个DOM Tree的方式造成的内存占用,从而可以提高可穿戴设备的视图更新的效率和流畅度。
Description
本公开涉及视图显示技术领域,具体涉及一种视图显示方法、装置、电子设备和存储介质。
近年来,智能手机发展的同时,可穿戴设备也得到了较大的进步,其功能越来越丰富,性能越来越优越。与智能手机相比,可穿戴设备的硬件较为简单,例如内存小等,因此可穿戴设备上所运行的应用程序多为快应用。在可穿戴设备的快应用框架中,可以使用MVVM(Model-View-ViewModel)更新机制实现数据到UI视图的绑定。但是相关技术中,视图更新过程中会占用较多内存,导致可穿戴设备的视图更新不及时甚至出现卡顿。
发明内容
为克服相关技术中存在的问题,本公开实施例提供一种视图显示方法、装置、电子设备和存储介质,用以解决相关技术中的缺陷。
根据本公开实施例的第一方面,提供一种视图显示方法,所述方法包括:
获取显示数据的更新信息;
根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容,生成补丁文件;
根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图。
在一个实施例中,所述获取显示数据的更新信息,包括:
获取所述显示数据中各个更新函数所获取的更新信息,其中,每个更新函数用于获取所述DOM Tree的一个节点对应的数据的更新信息。
在一个实施例中,所述获取显示数据的更新信息,包括:
在监听函数监听到所述显示数据发生改变的情况下,获取显示数据的更新信息。
在一个实施例中,所述获取显示数据的更新信息,包括:
获取视图更新场景下的显示数据的全部更新信息。
在一个实施例中,还包括:
在所述视图更新场景启动时,添加更新开始标记;
在所述视图更新场景结束时,添加更新结束标记;
所述获取视图更新场景下的显示数据的全部更新信息,包括:
在存在所述更新开始标记的情况下,获取所述显示数据的更新信息,并将获取到的所述更新信息缓存至第一缓存区内;
所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,包括:
在存在所述更新结束标记的情况下,根据所述第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。
在一个实施例中,所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,包括:
在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除。
在一个实施例中,所述在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除,包括:
将所述更新信息中,与节点的删除动作相关的信息转存至第二缓存区内;
在所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改之后,将所述第二缓存区内的信息对应的至少一个节点删除。
根据本公开实施例的第二方面,提供一种视图显示装置,所述装置包括:
获取模块,用于获取显示数据的更新信息;
补丁模块,用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容,生成补丁 文件;
更新模块,用于根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图。
在一个实施例中,所述获取模块具体用于:
获取所述显示数据中各个更新函数所获取的更新信息,其中,每个更新函数用于获取所述DOM Tree的一个节点对应的数据的更新信息。
在一个实施例中,所述获取模块具体用于:
在监听函数监听到所述显示数据发生改变的情况下,获取显示数据的更新信息。
在一个实施例中,所述获取模块具体用于:
获取视图更新场景下的显示数据的全部更新信息。
在一个实施例中,还包括标记模块,用于:
在所述视图更新场景启动时,添加更新开始标记;
在所述视图更新场景结束时,添加更新结束标记;
所述获取模块具体用于:
在存在所述更新开始标记的情况下,获取所述显示数据的更新信息,并将获取到的所述更新信息缓存至第一缓存区内;
所述补丁模块用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改时,具体用于:
在存在所述更新结束标记的情况下,根据所述第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。
在一个实施例中,所述补丁模块用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改时,具体用于:
在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除。
在一个实施例中,所述补丁模块用于在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删 除时,具体用于:
将所述更新信息中,与节点的删除动作相关的信息转存至第二缓存区内;
在所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改之后,将所述第二缓存区内的信息对应的至少一个节点删除。
根据本公开实施例的第三方面,提供一种电子设备,所述电子设备包括存储器、处理器,所述存储器用于存储可在处理器上运行的计算机指令,所述处理器用于在执行所述计算机指令时基于第一方面所述的视图显示方法。
根据本公开实施例的第四方面,提供一种计算机可读存储介质,其上存储有计算机程序,所述程序被处理器执行时实现第一方面所述的方法。
本公开的实施例提供的技术方案可以包括以下有益效果:
本公开所提供的视图显示方法,通过获取显示数据的更新信息,可以根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容生成补丁文件,最后可以根据补丁文件对当前视图中的局部内容进行渲染和更新。由于该过程中仅对DOM Tree的部分节点进行修改,因此可以降低视图更新过程中的内存占用,尤其避免了相关技术中在显示数据更新时,获取全部的显示数据,并据此生成另一个DOM Tree的方式造成的内存占用,从而可以提高可穿戴设备的视图更新的效率和流畅度。
此处的附图被并入说明书中并构成本说明书的一部分,示出了符合本发明的实施例,并与说明书一起用于解释本发明的原理。
图1是本公开一示例性实施例示出的视图显示方法的流程图;
图2是本公开另一示例性实施例示出的视图显示方法的流程图;
图3是本公开一示例性实施例示出的视图显示装置的结构示意图;
图4是本公开一示例性实施例示出的电子设备的结构框图。
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的,而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。还应当理解,本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解,尽管在本公开可能采用术语第一、第二、第三等来描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如,在不脱离本公开范围的情况下,第一信息也可以被称为第二信息,类似地,第二信息也可以被称为第一信息。取决于语境,如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
可穿戴设备的显示视图时,其内存中具有一个与显示数据相对应的DOM Tree(Document Object Model Tree,文件对象模型树),该DOM Tree也是与可穿戴设备的显示视图相对应的。相关技术中在更新视图时,首先是显示数据发生更新,则可以获取全部的显示数据,然后根据该全部的显示数据生成一个新的DOM Tree,该新的DOM Tree与原DOM Tree相比,部分节点相同,部分节点不同,因此可以通过比较两个DOM Tree生成补丁文件,进而可以根据该补丁文件对视图进行更新。由于每次视图更新时,需要在内存中同时保存两个DOM Tree,而可穿戴设备的***内存较小,因此会经常出现视图切换卡顿等问题。
基于此,第一方面,本公开至少一个实施例提供了一种视图显示方法, 请参照附图1,其示出了该方法的流程,包括步骤S101和步骤S103。
其中,该方法可以应用于智能手表、智能手环等可穿戴设备的显示视图更新过程。可穿戴设备的显示视图可以为操作***的界面、应用程序等的UI界面。该方法可以应用在程序开发者于可穿戴设备的操作***上开发应用程序的场景下,即程序开发者触发应用程序的数据更新,则该方法可以基于该数据更新对视图进行更新。
在步骤S101中,获取显示数据的更新信息。
其中,应用程序的数据包括与视图相关的数据和与显示视图无关的数据,其中,显示数据即为与显示视图相关的数据,应用程序的数据可以为代码形式的数据,或者其他形式的数据。显示数据和DOM Tree均与显示视图相对应,是描述显示视图内容的两种格式文件,DOM Tree具有呈树状结构的多个节点,每个节点对应于显示视图中的某个局部内容。
显示数据具有与DOM Tree的每个节点对应的数据,而且可以预先为每个节点对应的数据设置更新函数,每个更新函数用于获取所述DOM Tree的一个节点对应的数据的更新信息,因此本步骤中可以获取所述显示数据中各个更新函数所获取的更新信息。相对于相关技术中为显示数据设置一个用于获取全部显示数据的更新信息的更新函数,本实施例中为每个节点对应的数据设置独立的更新函数,可以有针对性的获取显示数据中发生更新的节点对应的数据。
在一个可能的实施例中,还可以预先为显示数据设置监听函数,该监听函数用于监听显示数据是否发生改变。因此本步骤中可以在监听函数监听到所述显示数据发生改变的情况下,获取显示数据的更新信息。示例性的,在监听函数监听到所述显示数据发生改变的情况下,触发各个更新函数获取节点对应的数据的更新信息。
在程序开发者于可穿戴设备的操作***上开发应用程序的场景下,即程序开发者触发应用程序的数据更新时,可以获取视图更新场景下的显示数据的全部更新信息。这是因为程序开发者可以在视图更新场景下触发应用程序 的数据更新。视图更新场景可以包括生命周期回调场景、定时器回调场景、异步调用场景和时间回调场景等,上述获取视图更新场景下的显示数据的全部更新信息,可以获取上述任一场景下的显示数据的全部更新信息。从而解决了单树更新时的更新信息分组的问题。
示例性的,可以在所述视图更新场景启动时,在可穿戴设备的操作***或者应用程序添加更新开始标记,在所述视图更新场景结束时,在可穿戴设备的操作***或者应用程序添加更新结束标记(同时删除更新开始标记)。从而可以在存在所述更新开始标记的情况下,获取所述显示数据的更新信息,并将获取到的所述更新信息缓存至第一缓存区内,以获取视图更新场景下显示数据的全部更新信息。
可以理解的是,当具有多种视图更新场景时,可以在每种视图更新场景启动时,添加对应的视图更新场景的启动标记,在每种视图更新场景结束时,添加对应的视图更新场景的结束标记。例如,在生命周期回调场景启动时,可以添加生命周期回调场景的启动标记,在生命周期回调场景结束时,可以添加生命周期回调场景的结束标记(同时删除生命周期回调场景的启动标记)。多种视图更新场景可以存在交集,即同时处于两种或更多的视图更新场景。进而,每种视图更新场景均具有对应的第一缓存区,则可以在存在某个视图更新场景的启动标记的情况下,获取显示数据的更新信息并缓存与该视图更新场景对应的第一缓存区。
在步骤S102中,根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容,生成补丁文件。
可以根据更新信息与DOM Tree的节点修改内容间的映射关系,确定更新信息对应的节点修改内容。从而可以按照修改内容对对应的至少一个节点进行修改,这些修改内容中可以包含对一个节点的多项修改内容。
在一个可能的实施例中,在所述视图更新场景启动时,在可穿戴设备的操作***或者应用程序添加更新开始标记,在所述视图更新场景结束时,在 可穿戴设备的操作***或者应用程序添加更新结束标记(同时删除更新开始标记)。从而可以在存在所述更新结束标记的情况下,根据所述第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。可以理解的是,若存在多个视图更新场景,则可以在存在某个视图更新场景对应的更新结束标记时,根据该视图更新场景对应的第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。另外,在对所述显示数据对应的DOM Tree的至少一个节点进行修改后,可以将更新结束标记删除,从而避免重复对DOM Tree进行修改。
补丁文件可以包括存在修改的节点,以及每个节点的具体修改内容,修改内容可以包括多项修改动作。
在步骤S103中,根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图。
补丁文件中每个节点的修改内容中的修改动作是无序的,为了避免节点删除后后续操作继续对其进行访问和修改的问题,可以所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除。
示例性的,可以将所述更新信息中,与节点的删除动作相关的信息转存至第二缓存区内;在所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改之后,将所述第二缓存区内的信息对应的至少一个节点删除。将更新信息中与节点的删除动作相关的信息转存至第二缓存区,对删除动作执行了延迟处理,从而可以在单树更新时将所有受影响的组件依照更新顺序一次性更新完毕,且解决了节点提前删除后导致崩溃等问题。
本公开所提供的视图显示方法,通过获取显示数据的更新信息,可以根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容生成补丁文件,最后可以根据补丁文件对当前视图中的局部内容进行渲染和更新。本公开提供了一种新的vdom更新机制,由于该过程中仅对DOM Tree的部分节点进行修改,因此可以降低视图 更新过程中的内存占用,尤其避免了相关技术中在显示数据更新时,获取全部的显示数据,并据此生成另一个DOM Tree的方式造成的内存占用,从而可以提高可穿戴设备的视图更新的效率和流畅度。
可以参照附图2,其示出了本公开提供的视图显示方法的完整流程,从附图2中可以看出,在显示数据(data)发生数据修改时,监听函数watcher监听到显示数据发生改变,则触发各个节点对应的数据的更新函数(update function)对数据的更新信息进行获取,进而根据获取到的更新信息对所述显示数据对应的DOM Tree进行修改,然后再根据修改内容生成补丁文件(patch),最后将补丁文件发送至渲染器(render),以根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图。
根据本公开实施例的第二方面,提供一种视图显示装置,请参照附图3,所述装置包括:
获取模块301,用于获取显示数据的更新信息;
补丁模块302,用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容,生成补丁文件;
更新模块303,用于根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图。
在本公开的一些实施例中,所述获取模块具体用于:
获取所述显示数据中各个更新函数所获取的更新信息,其中,每个更新函数用于获取所述DOM Tree的一个节点对应的数据的更新信息。
在本公开的一些实施例中,所述获取模块具体用于:
在监听函数监听到所述显示数据发生改变的情况下,获取显示数据的更新信息。
在本公开的一些实施例中,所述获取模块具体用于:
获取视图更新场景下的显示数据的全部更新信息。
在本公开的一些实施例中,还包括标记模块,用于:
在所述视图更新场景启动时,添加更新开始标记;
在所述视图更新场景结束时,添加更新结束标记;
所述获取模块具体用于:
在存在所述更新开始标记的情况下,获取所述显示数据的更新信息,并将获取到的所述更新信息缓存至第一缓存区内;
所述补丁模块用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改时,具体用于:
在存在所述更新结束标记的情况下,根据所述第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。
在本公开的一些实施例中,所述补丁模块用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改时,具体用于:
在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除。
在本公开的一些实施例中,所述补丁模块用于在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除时,具体用于:
将所述更新信息中,与节点的删除动作相关的信息转存至第二缓存区内;
在所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改之后,将所述第二缓存区内的信息对应的至少一个节点删除。
关于上述实施例中的装置,其中各个模块执行操作的具体方式已经在第一方面有关该方法的实施例中进行了详细描述,此处将不做详细阐述说明。
根据本公开实施例的第三方面,请参照附图4,其示例性的示出了一种电子设备的框图。例如,装置400可以是移动电话,计算机,数字广播终端,消息收发设备,游戏控制台,平板设备,医疗设备,健身设备,个人数字助理等。
参照图4,装置400可以包括以下一个或多个组件:处理组件402,存储器404,电源组件406,多媒体组件408,音频组件410,输入/输出(I/O)的 接口412,传感器组件414,以及通信组件416。
处理组件402通常控制装置400的整体操作,诸如与显示,电话呼叫,数据通信,相机程序操作和记录操作相关联的操作。处理元件402可以包括一个或多个处理器420来执行指令,以完成上述的方法的全部或部分步骤。此外,处理组件402可以包括一个或多个模块,便于处理组件402和其他组件之间的交互。例如,处理部件402可以包括多媒体模块,以方便多媒体组件408和处理组件402之间的交互。
存储器404被配置为存储各种类型的数据以支持在设备400的操作。这些数据的示例包括用于在装置400上操作的任何应用程序或方法的指令,联系人数据,电话簿数据,消息,图片,视频等。存储器404可以由任何类型的易失性或非易失性存储设备或者它们的组合实现,如静态随机存取存储器(SRAM),电可擦除可编程只读存储器(EEPROM),可擦除可编程只读存储器(EPROM),可编程只读存储器(PROM),只读存储器(ROM),磁存储器,快闪存储器,磁盘或光盘。
电力组件406为装置400的各种组件提供电力。电力组件406可以包括电源管理***,一个或多个电源,及其他与为装置400生成、管理和分配电力相关联的组件。
多媒体组件408包括在所述装置400和用户之间的提供一个输出接口的屏幕。在一些实施例中,屏幕可以包括液晶显示器(LCD)和触控面板(TP)。如果屏幕包括触控面板,屏幕可以被实现为触控屏,以接收来自用户的输入信号。触控面板包括一个或多个触控传感器以感测触控、滑动和触控面板上的手势。所述触控传感器可以不仅感测触控或滑动动作的边界,而且还检测与所述触控或滑动操作相关的持续时间和压力。在一些实施例中,多媒体组件408包括一个前置摄像头和/或后置摄像头。当装置400处于操作模式,如拍摄模式或视频模式时,前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜***或具有焦距和光学变焦能力。
音频组件410被配置为输出和/或输入音频信号。例如,音频组件410包括一个麦克风(MIC),当装置400处于操作模式,如呼叫模式、记录模式和语音识别模式时,麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器404或经由通信组件416发送。在一些实施例中,音频组件410还包括一个扬声器,用于输出音频信号。
I/O接口412为处理组件402和***接口模块之间提供接口,上述***接口模块可以是键盘,点击轮,按钮等。这些按钮可包括但不限于:主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件414包括一个或多个传感器,用于为装置400提供各个方面的状态评估。例如,传感器组件414可以检测到装置400的打开/关闭状态,组件的相对定位,例如所述组件为装置400的显示器和小键盘,传感器组件414还可以检测装置400或装置400一个组件的位置改变,用户与装置400接触的存在或不存在,装置400方位或加速/减速和装置400的温度变化。传感器组件414还可以包括接近传感器,被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件414还可以包括光传感器,如CMOS或CCD图像传感器,用于在成像应用中使用。在一些实施例中,该传感器组件414还可以包括加速度传感器,陀螺仪传感器,磁传感器,压力传感器或温度传感器。
通信组件416被配置为便于装置400和其他设备之间有线或无线方式的通信。装置400可以接入基于通信标准的无线网络,如WiFi,2G或3G,4G或5G或它们的组合。在一个示例性实施例中,通信部件416经由广播信道接收来自外部广播管理***的广播信号或广播相关信息。在一个示例性实施例中,所述通信部件416还包括近场通信(NFC)模块,以促进短程通信。例如,在NFC模块可基于射频识别(RFID)技术,红外数据协会(IrDA)技术,超宽带(UWB)技术,蓝牙(BT)技术和其他技术来实现。
在示例性实施例中,装置400可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻 辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现,用于执行上述电子设备的供电方法。
第四方面,本公开在示例性实施例中,还提供了一种包括指令的非临时性计算机可读存储介质,例如包括指令的存储器404上述指令可由装置400的处理器420执行以完成上述电子设备的供电方法。例如,所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的公开后,将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本公开的真正范围和精神由下面的权利要求指出。
应当理解的是,本公开并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
Claims (16)
- 一种视图显示方法,其特征在于,所述方法包括:获取显示数据的更新信息;根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容,生成补丁文件;根据补丁文件对当前视图中的局部内容进行渲染和更新,得到目标视图。
- 根据权利要求1所述的视图显示方法,其特征在于,所述获取显示数据的更新信息,包括:获取所述显示数据中各个更新函数所获取的更新信息,其中,每个更新函数用于获取所述DOM Tree的一个节点对应的数据的更新信息。
- 根据权利要求1所述的视图显示方法,其特征在于,所述获取显示数据的更新信息,包括:在监听函数监听到所述显示数据发生改变的情况下,获取显示数据的更新信息。
- 根据权利要求1所述的视图显示方法,其特征在于,所述获取显示数据的更新信息,包括:获取视图更新场景下的显示数据的全部更新信息。
- 根据权利要求4所述的视图显示方法,其特征在于,还包括:在所述视图更新场景启动时,添加更新开始标记;在所述视图更新场景结束时,添加更新结束标记;所述获取视图更新场景下的显示数据的全部更新信息,包括:在存在所述更新开始标记的情况下,获取所述显示数据的更新信息, 并将获取到的所述更新信息缓存至第一缓存区内;所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,包括:在存在所述更新结束标记的情况下,根据所述第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。
- 根据权利要求1或5所述的视图显示方法,其特征在于,所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,包括:在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除。
- 根据权利要求6所述的视图显示方法,其特征在于,所述在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除,包括:将所述更新信息中,与节点的删除动作相关的信息转存至第二缓存区内;在所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改之后,将所述第二缓存区内的信息对应的至少一个节点删除。
- 一种视图显示装置,其特征在于,所述装置包括:获取模块,用于获取显示数据的更新信息;补丁模块,用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改,并根据所述至少一个节点的修改内容,生成补丁文件;更新模块,用于根据补丁文件对当前视图中的局部内容进行渲染和更 新,得到目标视图。
- 根据权利要求8所述的视图显示装置,其特征在于,所述获取模块具体用于:获取所述显示数据中各个更新函数所获取的更新信息,其中,每个更新函数用于获取所述DOM Tree的一个节点对应的数据的更新信息。
- 根据权利要求8所述的视图显示装置,其特征在于,所述获取模块具体用于:在监听函数监听到所述显示数据发生改变的情况下,获取显示数据的更新信息。
- 根据权利要求8所述的视图显示装置,其特征在于,所述获取模块具体用于:获取视图更新场景下的显示数据的全部更新信息。
- 根据权利要求11所述的视图显示装置,其特征在于,还包括标记模块,用于:在所述视图更新场景启动时,添加更新开始标记;在所述视图更新场景结束时,添加更新结束标记;所述获取模块具体用于:在存在所述更新开始标记的情况下,获取所述显示数据的更新信息,并将获取到的所述更新信息缓存至第一缓存区内;所述补丁模块用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改时,具体用于:在存在所述更新结束标记的情况下,根据所述第一缓存区内的更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改。
- 根据权利要求8或12所述的视图显示装置,其特征在于,所述补丁模块用于根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改时,具体用于:在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除。
- 根据权利要求13所述的视图显示装置,其特征在于,所述补丁模块用于在所述更新信息中存在对某个节点的删除动作的情况下,在该节点的其他修改动作执行完毕之后,将该节点删除时,具体用于:将所述更新信息中,与节点的删除动作相关的信息转存至第二缓存区内;在所述根据所述更新信息,对所述显示数据对应的DOM Tree的至少一个节点进行修改之后,将所述第二缓存区内的信息对应的至少一个节点删除。
- 一种电子设备,其特征在于,所述电子设备包括存储器、处理器,所述存储器用于存储可在处理器上运行的计算机指令,所述处理器用于在执行所述计算机指令时基于权利要求1至7中任一项所述的视图显示方法。
- 一种计算机可读存储介质,其上存储有计算机程序,其特征在于,所述程序被处理器执行时实现权利要求1至7中任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202280004258.1A CN117616385A (zh) | 2022-06-20 | 2022-06-20 | 视图显示方法、装置、电子设备和存储介质 |
PCT/CN2022/099938 WO2023245374A1 (zh) | 2022-06-20 | 2022-06-20 | 视图显示方法、装置、电子设备和存储介质 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/099938 WO2023245374A1 (zh) | 2022-06-20 | 2022-06-20 | 视图显示方法、装置、电子设备和存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023245374A1 true WO2023245374A1 (zh) | 2023-12-28 |
Family
ID=89378957
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/099938 WO2023245374A1 (zh) | 2022-06-20 | 2022-06-20 | 视图显示方法、装置、电子设备和存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN117616385A (zh) |
WO (1) | WO2023245374A1 (zh) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105324795A (zh) * | 2013-06-14 | 2016-02-10 | 微软技术许可有限责任公司 | 合并图形操作 |
CN106202529A (zh) * | 2016-07-22 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | 一种页面渲染方法及装置 |
CN108572819A (zh) * | 2017-12-21 | 2018-09-25 | 北京金山云网络技术有限公司 | 页面更新方法、装置、终端及计算机可读存储介质 |
CN109375918A (zh) * | 2018-11-23 | 2019-02-22 | 天津字节跳动科技有限公司 | 小程序的界面渲染方法、装置、电子设备和存储介质 |
CN111913705A (zh) * | 2020-05-28 | 2020-11-10 | 中南大学 | 一种基于差异更新算法的JavaScript模板实现方法 |
CN112069432A (zh) * | 2020-07-15 | 2020-12-11 | 北京邮电大学 | 基于web的数据可视化图表渲染优化方法及*** |
US20210240909A1 (en) * | 2020-01-30 | 2021-08-05 | Leap Tools Inc. | Systems and methods for product visualization using a single-page application |
-
2022
- 2022-06-20 CN CN202280004258.1A patent/CN117616385A/zh active Pending
- 2022-06-20 WO PCT/CN2022/099938 patent/WO2023245374A1/zh active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105324795A (zh) * | 2013-06-14 | 2016-02-10 | 微软技术许可有限责任公司 | 合并图形操作 |
CN106202529A (zh) * | 2016-07-22 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | 一种页面渲染方法及装置 |
CN108572819A (zh) * | 2017-12-21 | 2018-09-25 | 北京金山云网络技术有限公司 | 页面更新方法、装置、终端及计算机可读存储介质 |
CN109375918A (zh) * | 2018-11-23 | 2019-02-22 | 天津字节跳动科技有限公司 | 小程序的界面渲染方法、装置、电子设备和存储介质 |
US20210240909A1 (en) * | 2020-01-30 | 2021-08-05 | Leap Tools Inc. | Systems and methods for product visualization using a single-page application |
CN111913705A (zh) * | 2020-05-28 | 2020-11-10 | 中南大学 | 一种基于差异更新算法的JavaScript模板实现方法 |
CN112069432A (zh) * | 2020-07-15 | 2020-12-11 | 北京邮电大学 | 基于web的数据可视化图表渲染优化方法及*** |
Also Published As
Publication number | Publication date |
---|---|
CN117616385A (zh) | 2024-02-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018177208A1 (zh) | 换装方法、装置、计算机可读介质和电子设备 | |
EP3249524A1 (en) | Method and device for upgrading a zigbee device | |
WO2019109564A1 (zh) | 屏幕显示控制的方法和装置 | |
RU2633189C2 (ru) | Метод и устройство для обеспечения совместимости приложения для управления маршрутизатором и встроенного программного обеспечения маршрутизатора | |
JP2016526244A (ja) | アプリケーションプログラムの処理方法、装置、プログラム及び記憶媒体 | |
CN107357613B (zh) | 应用更新方法、装置及计算机可读存储介质 | |
JP2023506936A (ja) | マルチ画面共働方法およびシステム、ならびに電子デバイス | |
CN105808305B (zh) | 静态资源的加载方法和装置 | |
WO2016173246A1 (zh) | 基于云名片的电话呼叫方法及装置 | |
WO2016150104A1 (zh) | 应用主题的加载方法及装置 | |
WO2020020048A1 (zh) | 更新群成员数据的方法、装置、终端、***及存储介质 | |
WO2017181544A1 (zh) | 即时通信应用的任务管理方法及装置 | |
CN111222014A (zh) | 请求处理方法、装置、电子设备及存储介质 | |
CN110971974B (zh) | 配置参数创建方法、装置、终端及存储介质 | |
CN108153488B (zh) | 数据自增方法及装置 | |
CN112188034A (zh) | 一种图像处理方法、装置、终端设备及介质 | |
WO2017128664A1 (zh) | 进程调用的方法及装置 | |
WO2023245374A1 (zh) | 视图显示方法、装置、电子设备和存储介质 | |
US11847305B1 (en) | Page display method, electronic device and storage medium | |
CN107256151B (zh) | 页面渲染的处理方法、装置及终端 | |
CN107368562B (zh) | 页面的显示方法、装置及终端 | |
CN110457084B (zh) | 一种加载方法及装置 | |
CN114442789A (zh) | 暗屏控制方法、装置、设备及存储介质 | |
CN108958943B (zh) | 内存释放方法及装置 | |
CN112214252A (zh) | 一种信息扩展方法、装置和电子设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 202280004258.1 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22947155 Country of ref document: EP Kind code of ref document: A1 |