Table view rendering method and apparatus, electronic device, and storage medium

Abstract

The embodiments of the present disclosure disclose a table view rendering method and apparatus, an electronic device, and a storage medium. The method comprises: receiving a table view rendering instruction; when local structural information corresponding to the rendering instruction is not requested, requesting the local structural information from a server, wherein the local structural information comprises local group node information and item node information; when a view structure of the table view is not constructed, creating a new view structure, and setting nodes of the view structure according to the requested local structural information; when the view structure of the table view is constructed, updating the nodes of the view structure according to the requested local structural information; and rendering the view structure in an interface window. The present disclosure effectively improves table view rendering efficiency.

Description

Rendering methods, devices, electronic equipment, and storage media for table views

[0001] Cross-reference of related applications

[0002] This application claims priority to Chinese Patent Application No. 202411525208.5, filed on October 29, 2024, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to a method, apparatus, electronic device, and storage medium for rendering a table view. Background Technology

[0004] In related technologies, the rendering process of a multidimensional table view may include: the server calculating the view structure according to the presentation conditions and synchronizing it to the client; the client drawing the layout and loading data according to the view structure to complete the table view rendering. When the number of rows in a multidimensional table increases to hundreds of thousands or even millions, the large amount of view structure calculation and low synchronization efficiency result in low view rendering efficiency. Summary of the Invention

[0005] This disclosure provides a method, apparatus, electronic device, and storage medium for rendering table views, which can effectively improve the rendering efficiency of table views.

[0006] In a first aspect, embodiments of this disclosure provide a method for rendering a table view, including:

[0007] Receive rendering instructions for the table view;

[0008] If the local structure information corresponding to the rendering instruction is not requested, the local structure information is requested from the server; wherein, the local structure information includes local group node information and record node information;

[0009] If the view structure of the table view has not been built, a new view structure is created, and the nodes of the view structure are set according to the requested local structure information;

[0010] If the view structure of the table view has been constructed, the nodes of the view structure are updated according to the requested local structure information;

[0011] Render the view structure within the interface window.

[0012] Secondly, embodiments of this disclosure also provide a rendering apparatus for a table view, comprising:

[0013] The receiving module is used to receive rendering instructions for the table view;

[0014] The request module is used to request the local structure information from the server when the local structure information corresponding to the rendering instruction has not been requested; wherein, the local structure information includes local group node information and record node information;

[0015] The construction module is used to create a new view structure when the view structure of the table view has not been constructed, and to set the nodes of the view structure according to the requested local structure information;

[0016] An update module is used to update the nodes of the view structure according to the requested local structure information, provided that the view structure of the table view has been constructed.

[0017] The rendering module is used to render the view structure within the interface window.

[0018] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0019] One or more processors;

[0020] Storage device for storing one or more programs.

[0021] When the one or more programs are executed by the one or more processors, the one or more processors implement the table view rendering method as described in any embodiment of this disclosure.

[0022] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a rendering method for a table view as described in any of the embodiments of this disclosure. Attached Figure Description

[0023] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0024] Figure 1 is a flowchart illustrating a table view rendering method provided in an embodiment of this disclosure;

[0025] Figure 2 is a schematic diagram of the view structure in a table view rendering method provided in an embodiment of this disclosure;

[0026] Figure 3 is a signaling interaction diagram of a table view rendering method provided in an embodiment of this disclosure;

[0027] Figure 4 is a schematic diagram of node marking in the view structure in a table view rendering method provided by an embodiment of this disclosure;

[0028] Figure 5 is a schematic diagram of the structure of a table view rendering device provided in an embodiment of this disclosure; and

[0029] Figure 6 is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0030] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0031] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0032] The term "comprising" and its variations as used in this disclosure are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the description below.

[0033] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0034] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0035] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0036] Figure 1 is a schematic flowchart of a table view rendering method provided in an embodiment of this disclosure. This embodiment is applicable to table view rendering, such as rendering multidimensional table views of large-scale data. The method can be executed by a table view rendering device, which can be implemented in software and / or hardware. This device can be integrated into a client and installed in an electronic device, such as a mobile phone or computer.

[0037] As shown in Figure 1, the table view rendering method provided in this embodiment may include:

[0038] S110, Receive the rendering instructions for the table view.

[0039] In this embodiment, the client can generate a rendering instruction for the table view in response to access, browsing, or update operations. This rendering instruction can be sent to the rendering device integrated within the client, so that the rendering device can receive the rendering instruction.

[0040] S120. If the local structure information corresponding to the rendering instruction has not been requested, request the local structure information.

[0041] In this embodiment, the rendering instruction may carry identification information of the portion to be rendered in the table view, and the table view can be considered a view structure loaded with data. Furthermore, the rendering device can determine the local structure to be rendered in the view structure based on the identification information carried by the rendering instruction; this local structure can be referred to as the local structure corresponding to the rendering instruction. The portion to be rendered may include a fixed number of data rows, or it may include a number of data rows determined according to the interface window size of the device to which the rendering device belongs. For example, when a rendering instruction is generated based on an access operation of the table view, the identification information may include the identification information of the first screen of the table view to be rendered (e.g., 200 data rows), and the local structure in the view structure corresponding to the identification information can be determined as the local structure corresponding to the rendering instruction.

[0042] The local structure information can include local node information, which may include, for example, group node information and record node information under each group node. That is, the local structure information can include local group node information and record node information. Grouping can be understood as the table view aggregating and displaying one or more record data according to set grouping conditions, with each aggregation result considered to belong to the same group node. For example, when the grouping condition is province / city, record data from the same province / city can be aggregated and displayed, thus showing multiple province / city group nodes in the table. Each record node under a group node can correspond to one record data. The group node information can include the number of group nodes and the identifier of each group node; the record node information can include the number of record nodes under each group node and the identifier of each record node.

[0043] In this embodiment, local structure information can be used to construct the view structure. If local structure information has been requested previously, it can be considered that the local structure information has already been requested. In this case, the view structure can be considered to contain the corresponding local structure, and there is no need to request the local structure information again. Instead, the local structure in the already constructed view structure can be directly rendered and displayed in the interface window. If local structure information has not been requested previously, it can be considered that the local structure information has not been requested. In this case, the local structure information can be requested from the server.

[0044] S130. If the view structure of the table view has not been built, create a new view structure and set the nodes of the view structure according to the requested local structure information.

[0045] When a table view is accessed for the first time, the view structure can be assumed to be unbuilt. In this case, the local structure information corresponding to the data on the first screen can be requested; a new view structure can be created using existing view structure building methods; and the nodes in the view structure can be set according to the grouping node information and record node information in the local structure information to complete the construction of the view structure.

[0046] S140. If the view structure of the table view has been constructed, update the nodes of the view structure according to the requested local structure information.

[0047] Once the table view is open and being browsed or edited, the view structure corresponding to the table view can be considered to have been constructed. At this point, the grouping nodes and record nodes can be updated in the constructed view structure based on the grouping node information and record node information in the local structure information.

[0048] For example, Figure 2 is a schematic diagram of the view structure in a table view rendering method provided by an embodiment of this disclosure. Referring to Figure 2, the view structure may include a tree structure, and the view structure may include a root node, group nodes (such as group nodes 1-3, etc.), and record nodes (such as record nodes 1-3, etc.). Figure 2 shows a single-level group node; in actual applications, group nodes may not be included, or two or more levels of group nodes may be included. In the view structure shown in Figure 2, unfilled node boxes can represent nodes that have requested structure information, and dot-filled node boxes can represent nodes that have not requested structure information. As can be seen from Figure 2, the view structure maintained by the rendering device may include some group nodes and some record nodes, rather than necessarily maintaining the entire view structure.

[0049] In some optional implementations, the rendering instructions for the table view can be generated based on browsing operations of the table view. Browsing operations can include, for example, scrolling up / down. The situation where the table view is opened and rendering instructions are generated based on browsing operations can be considered as the view structure having been constructed. In this case, updating the nodes of the view structure according to the requested local structure information can include adding nodes to the already constructed view structure. In these optional implementations, rendering instructions can be generated when browsing to a preset progress point of the rendered table view, to request local structure information corresponding to the part of the table view to be rendered. After receiving the local structure information returned by the server, nodes can be added to the already constructed view structure according to the local structure information to update the view structure.

[0050] S150. Render the view structure within the interface window.

[0051] In this embodiment, the number of nodes in the local view structure corresponding to the rendering instruction can be greater than the number of nodes in the view structure presented in the interface window. This allows for rapid rendering of the table view through pre-construction of the view structure. For example, when the rendering instruction is generated based on an access operation, a view structure containing 200 record nodes can be constructed, while the interface window can present a view structure corresponding to 50 record nodes. This enables rapid rendering of the view structure within the interface window when browsing subsequent table views.

[0052] In this embodiment, the view structure portion that needs to be presented within the interface window can be rendered based on the constructed view structure. Specifically, the view structure can be rendered using existing rendering methods. Furthermore, existing data loading methods can be used to load the data that needs to be presented within the interface window into the view structure to achieve table view rendering.

[0053] For example, Figure 3 is a signaling interaction diagram of a table view rendering method provided in an embodiment of this disclosure. Referring to steps 1-4 in Figure 3, when the client 1 executes the rendering method provided in this embodiment of the disclosure, in step 1, the client 1 can generate a rendering instruction in response to the table view access operation; in step 2, the rendering device in the client 1 can request local structure information from the server according to the rendering instruction; in step 3, the server can return the local structure information to the client 1; in step 4, the rendering device in the client 1 can create a new view structure and set the nodes of the view structure according to the local structure information to realize the view structure construction, and can render the view structure in the interface window.

[0054] Referring to steps 15-16 in Figure 3, when the client 1 executes the rendering method provided in this embodiment of the disclosure, in step 15, the client 1 can generate a rendering instruction in response to the scrolling operation of the table view; in step 16, the rendering device in the client 1 can execute steps 2-4 to render the view structure if the view structure in the current interface window has not been constructed.

[0055] In the technical solution of this embodiment, a rendering instruction for a table view is received; if the local structure information corresponding to the rendering instruction is not requested, the local structure information is requested from the server; wherein, the local structure information includes local group node information and record node information; if the view structure of the table view has not been constructed, a new view structure is created, and the nodes of the view structure are set according to the requested local structure information; if the view structure of the table view has been constructed, the nodes of the view structure are updated according to the requested local structure information; and the view structure within the interface window is rendered.

[0056] Compared to related technologies where the client requests the complete view structure from the server, in this embodiment, the client can request local structure information from the server based only on the local view structure upon which the interface window depends, and can construct and update the view structure based on the local structure information. Therefore, the server does not need to calculate the complete view structure, nor does it need to synchronize the complete view structure to the client. By maintaining the local view structure, the client can achieve fast rendering of the table view, effectively improving the rendering efficiency of the table view.

[0057] This embodiment can be combined with various optional solutions in the table view rendering method provided in the above embodiments. The table view rendering method provided in this embodiment describes in detail the table view rendering process when it is being edited. By marking the view structure nodes affected by the editing command, it is beneficial to achieve local updates of the view structure, ensuring high update efficiency.

[0058] The table view rendering method provided in this embodiment may further include: receiving editing instructions for the table view; and marking the changed nodes within the view structure when the editing instructions cause changes to the view structure.

[0059] The editing instructions for a table view can be generated based on at least one of the following editing operations: resetting grouping conditions, resetting filter conditions, resetting sorting conditions, and adding, deleting, modifying, and changing groupings of record data. Editing a table view based on these instructions may or may not change the view structure. For example, resetting grouping conditions typically changes the overall view structure; adding record data changes some nodes in the view structure; and modifying record data does not change the view structure.

[0060] In this embodiment, there are cases where editing commands cause changes to the view structure, but these changes are not reflected in the current interface window. For example, if the recorded data is grouped differently, the group node to which the recorded data has been changed may not be displayed in the current interface window. In this embodiment, when editing the table view based on editing commands causes changes to the view structure, the changed nodes within the view structure can be marked (also known as dirtying). This allows for partial updates to the marked nodes in the view structure if the view structure to be rendered within the interface window contains the marked nodes, ensuring high update efficiency for the view structure.

[0061] For example, Figure 4 is a schematic diagram of node marking in a table view rendering method provided by an embodiment of this disclosure. Figure 4 can be considered a schematic diagram of node marking based on the view structure shown in Figure 2. Referring to Figure 4, the diagonally filled node boxes can represent nodes within the constructed view structure that need to be changed. In Figure 4, the marked nodes may include grouping nodes 2 and their contained record nodes 3.

[0062] Furthermore, if the editing command does not cause changes to the view structure, there is no need to mark the view structure; only the data changes corresponding to the editing command need to be recorded. This allows for updating the loaded record data based solely on the recorded information without altering the view structure, facilitating the rapid presentation of table views.

[0063] In some optional implementations, the table view rendering method may further include: generating first editing description information according to editing instructions, and sending the first editing description information to the server so that the server updates the table data of the table view according to the first editing description information; upon receiving a first update success message sent by the server and the interface window contains marked nodes, requesting local structure information from the server again to re-render the view structure within the interface window; wherein the first update success message corresponds to the first editing description information.

[0064] The first edit description information can be in the form of a code segment, which may include multiple fields and their corresponding values. The first edit description information may include the node identifier of the changed node, such as a group node identifier and / or a record node identifier. Furthermore, the first edit description information may also include the changed record data, which can be used to update the record data.

[0065] Referring to steps 5-7, 9-10, and 12 in Figure 3, when client 1 executes the rendering method provided in this embodiment of the present disclosure, in step 5, client 1 can generate an editing instruction in response to the editing operation; in step 6, the rendering device in client 1 can mark the changed nodes in the view structure when the editing instruction causes a change in the view structure; in step 7, the rendering device in client 1 can generate first editing description information according to the editing instruction and send the first editing description information to the server; in step 9, the server can update the record data of the table view according to the first description information and save it to a preset database; in step 10, after the update is completed, the server can return a first update success message corresponding to the first editing description information to client 1; in step 12, when client 1 receives the first update success message and the current interface window contains the marked nodes, it can request local structure information from the server again to execute steps 2-4 again, thereby re-rendering the view structure in the interface window.

[0066] Furthermore, if the server fails to update, it can return a first update failure message corresponding to the first edit description information, allowing client 1 to display the interface window before editing. Additionally, if the current interface window does not contain the marked node, there is no need to re-render the view structure of the interface window.

[0067] Among these optional implementation methods, if the server-side update is successful and the interface window contains the marked nodes, the view structure within the interface window can be partially updated. This can avoid the situation where the server and client updates are out of sync, speed up the view structure update efficiency, and avoid the situation where the content presented in the interface window is frequently updated when the interface window does not contain the marked nodes, which would affect the user's viewing experience, thus improving the user experience.

[0068] The technical solutions of this disclosure embodiment describe in detail the rendering of a table view when it is being edited. By marking the view structure nodes affected by the editing command, it is beneficial to achieve local updates of the view structure and ensure high update efficiency. Furthermore, the table view rendering method provided in this disclosure embodiment belongs to the same disclosed concept as the table view rendering method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and the same technical features have the same beneficial effects in this embodiment and the above embodiments.

[0069] This embodiment can be combined with various optional solutions in the table view rendering method provided in the above embodiments. The table view rendering method provided in this embodiment describes in detail the rendering scenario when a collaboratively editable table view is edited by other clients. When other clients edit the table view, they can receive second edit description information forwarded by the server. By marking the view structure nodes affected by the second edit description information, it is beneficial to achieve local updates of the view structure and ensure high update efficiency of the view structure.

[0070] The table view rendering method provided in this embodiment may further include: receiving second editing description information sent by a server; wherein the second editing description information is generated by a client other than this client; and, upon receiving a second update success message sent by the server, marking the changed nodes in the view structure according to the second editing description information; wherein the second update success message corresponds to the second editing description information.

[0071] In this embodiment, the table view may include a table view that can be collaboratively edited by multiple clients. When other clients besides this client receive editing instructions for the table view, and these instructions cause changes to the view structure, the other clients can generate second editing description information. This second editing description information is essentially the same as the first editing description information, and may contain the same fields. Specifically, the editing description information generated by this client can be referred to as the first editing description information, while the editing description information generated by other clients can be referred to as the second editing description information. It can be understood that the same editing description information can be referred to as either the first or the second editing description information on different clients.

[0072] Upon receiving a second edit description from any other client within the collaboration scope, the server can synchronize it to this client. The server can update the record data of the table view based on the second description and save it to a preset database. After the update is complete, it can also send a second update success message corresponding to the second edit description to all clients within the collaboration scope. Upon receiving the second update success message, this client can mark the changed nodes within the view structure based on the node identifiers of the changed nodes contained in the second edit description. Therefore, if the view structure to be rendered within the interface window contains marked nodes, the marked nodes can be partially updated to ensure high update efficiency of the view structure.

[0073] The server can synchronize the second editing description information to the client at the same time or before updating the record data of the table view according to the second editing description information, so that the client can pre-cache the second editing description information, which can improve the update efficiency of the view structure to a certain extent.

[0074] Referring to steps 8-9, 11, and 13-14 in Figure 3, when client 2 executes the rendering method provided in this embodiment, in step 8, client 2 can receive second editing description information sent by the server; wherein, the second editing description information is generated by client 1 outside of this client; in step 9, the server can update the record data of the table view according to the second description information and save it to a preset database; in step 11, the server can send a second update success message to client 2 after the update is completed; in step 13, client 2 can mark the changed nodes in the view structure according to the second editing description information upon receiving the second update success message; in step 14, if the view structure to be rendered in the current interface window contains the marked nodes, the client can request local structure information from the server again to execute steps 2-4 again, thereby re-rendering the view structure in the interface window. Furthermore, step 14 may also include the option that if the current interface window does not contain the marked nodes, the view structure of the interface window does not need to be re-rendered.

[0075] In some alternative implementations, the table view rendering method may also include: upon receiving a rendering instruction, having requested local structure information, and having the interface window containing marked nodes, requesting the local structure information again from the server to re-render the view structure within the interface window.

[0076] Referring again to steps 15-16 in Figure 3, when the client 1 executes the rendering method provided in this embodiment of the disclosure, in step 15, the client 1 may generate a rendering instruction in response to the scrolling operation of the table view; step 16 may also include the rendering device in the client 1, which, when the view structure in the current interface window has been constructed and contains marked nodes, may request local structure information from the server again to execute steps 2-4 again, so as to re-render the view structure in the interface window.

[0077] Among these optional implementations, when browsing the table view portion of the constructed view structure and the interface window contains marked nodes, the marked nodes in the view structure can be partially updated, thereby improving the update efficiency of the view structure.

[0078] Furthermore, in some optional implementations, the table view rendering method may also include: rendering the view structure within the interface window based on the already constructed view structure when a rendering instruction is received, local structure information has been requested, and the interface window does not contain marked nodes. In these optional implementations, the view structure within the interface window can be rendered based on the already constructed view structure even when browsing the table view portion of the constructed view structure and the interface window does not contain marked nodes, thereby improving the rendering efficiency of the view structure.

[0079] This disclosure provides a detailed description of the rendering scenario when a collaboratively editable table view is edited by other clients. When other clients edit the table view, they can receive second edit description information forwarded by the server. By marking the view structure nodes affected by the second edit description information, local updates of the view structure are facilitated, ensuring high update efficiency. Furthermore, the table view rendering method provided in this disclosure belongs to the same concept as the table view rendering method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and the same technical features have the same beneficial effects in this embodiment and the above embodiments.

[0080] Figure 5 is a schematic diagram of a table view rendering apparatus provided in an embodiment of this disclosure. The table view rendering apparatus provided in this embodiment is applicable to table view rendering, such as the rendering of multidimensional table views of large-scale data.

[0081] As shown in Figure 5, the table view rendering apparatus provided in this embodiment of the present disclosure may include:

[0082] The receiving module 510 is used to receive rendering instructions for the table view;

[0083] The request module 520 is used to request local structure information from the server when the local structure information corresponding to the rendering instruction has not been requested; wherein, the local structure information includes local group node information and record node information;

[0084] Module 530 is used to create a new view structure when the view structure of the table view has not been built, and to set the nodes of the view structure according to the requested local structure information.

[0085] The update module 540 is used to update the nodes of the view structure based on the requested local structure information, provided that the view structure of the table view has been constructed.

[0086] Rendering module 550 is used to render the view structure within the interface window.

[0087] In some optional implementations, the rendering instructions for the table view are generated based on the browsing operations of the table view;

[0088] Builder modules can be used to add nodes to an already constructed view structure.

[0089] In some alternative implementations, the receiving module can also be used to: receive editing instructions from the table view;

[0090] The rendering apparatus for a table view may further include:

[0091] The tagging module is used to tag nodes that have changed within the view structure when editing commands cause changes to the view structure.

[0092] In some alternative implementations, the rendering device for the table view may also include:

[0093] The sending module is used to generate first editing description information according to the editing instructions and send the first editing description information to the server so that the server updates the table data in the table view according to the first editing description information;

[0094] Correspondingly, the rendering module can also be used to request local structure information from the server again when it receives the first update success message from the server and the interface window contains the marked nodes, so as to re-render the view structure in the interface window; wherein the first update success message corresponds to the first edit description information.

[0095] In some alternative implementations, the receiving module can also be used for:

[0096] Receive the second edit description information sent by the server; wherein the second edit description information is generated by a client other than this client;

[0097] Correspondingly, the marking module can also be used to mark the changed nodes in the view structure according to the second edit description information when a second update success message is received from the server.

[0098] The second update success message corresponds to the second edit description information.

[0099] In some alternative implementations, the rendering module can also be used for:

[0100] If a rendering instruction has been received, local structure information has been requested, and the interface window contains marked nodes, the local structure information is requested again from the server in order to re-render the view structure within the interface window.

[0101] In some alternative implementations, the rendering module can also be used for:

[0102] Upon receiving rendering instructions, requesting local structural information, and when the interface window does not contain marked nodes, the view structure within the interface window is rendered based on the constructed view structure.

[0103] The table view rendering apparatus provided in this disclosure can execute the table view rendering method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the method execution.

[0104] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0105] Referring now to FIG6, a schematic diagram of the structure of an electronic device (e.g., the terminal device or server in FIG6) 600 suitable for implementing embodiments of the present disclosure is shown. The terminal device in embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in FIG6 is merely an example and should not impose any limitation on the functionality and scope of use of embodiments of the present disclosure.

[0106] As shown in Figure 6, the electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0107] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although FIG. 6 illustrates electronic device 600 with various devices, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0108] According to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the table view rendering method of embodiments of this disclosure.

[0109] The electronic device provided in this embodiment and the table view rendering method provided in the above embodiments belong to the same disclosed concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0110] This disclosure provides a storage medium for computer-executable instructions, which, when executed by a computer processor, can be used to perform the table view rendering method provided in the above embodiments.

[0111] It should be noted that the storage medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory (FLASH), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium that contains or stores executable instructions that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable executable instructions. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit executable instructions for use by or in connection with an instruction execution system, apparatus, or device. Executable instructions contained on the storage medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0112] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0113] The aforementioned storage medium may be included in the aforementioned electronic device; or it may exist independently and not be assembled into the electronic device.

[0114] The aforementioned storage medium carries one or more executable instructions, which, when executed by the electronic device, cause the electronic device to:

[0115] Receive rendering instructions from the table view; if the local structure information corresponding to the rendering instructions is not requested, request the local structure information from the server; the local structure information includes local group node information and record node information; if the view structure of the table view has not been built, create a new view structure and set the nodes of the view structure according to the requested local structure information; if the view structure of the table view has been built, update the nodes of the view structure according to the requested local structure information; render the view structure within the interface window.

[0116] Executable instructions for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The executable instructions can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0117] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, can implement the table view rendering method provided in any embodiment of this disclosure.

[0118] In implementing a computer program product, computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0119] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0120] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units and modules do not, in certain circumstances, constitute a limitation on the unit or module itself.

[0121] The functions described above in this disclosure can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), Application Specific Standard Parts (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), and so on.

[0122] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0123] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, the method comprising:

[0124] Receive rendering instructions for the table view;

[0125] If the local structure information corresponding to the rendering instruction is not requested, the local structure information is requested from the server; wherein, the local structure information includes local group node information and record node information;

[0126] If the view structure of the table view has not been built, a new view structure is created, and the nodes of the view structure are set according to the requested local structure information;

[0127] If the view structure of the table view has been constructed, the nodes of the view structure are updated according to the requested local structure information;

[0128] Render the view structure within the interface window.

[0129] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, further comprising:

[0130] In some optional implementations, the rendering instructions for the table view are generated based on the browsing operation of the table view;

[0131] Updating the nodes of the view structure according to the requested local structure information includes adding nodes to the already constructed view structure.

[0132] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, further comprising:

[0133] In some optional implementations, editing instructions for the table view are received;

[0134] If the edit command causes a change in the view structure, the nodes within the view structure that have changed are marked.

[0135] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, further comprising:

[0136] In some optional implementations, a first editing description is generated according to the editing instruction, and the first editing description is sent to the server so that the server updates the table data of the table view according to the first editing description.

[0137] Upon receiving the first update success message from the server, and if the interface window contains the marked node, the system re-requests the local structure information from the server to re-render the view structure within the interface window; wherein the first update success message corresponds to the first edit description information.

[0138] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, further comprising:

[0139] In some optional implementations, the second edit description information sent by the server is received; wherein the second edit description information is generated by a client other than this client.

[0140] Upon receiving the second update success message sent by the server, the changed nodes within the view structure are marked according to the second edit description information;

[0141] The second update success message corresponds to the second edit description information.

[0142] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, further comprising:

[0143] In some alternative implementations, upon receiving the rendering instruction, having already requested the local structure information, and with the interface window containing marked nodes, the local structure information is re-requested from the server to re-render the view structure within the interface window.

[0144] According to one or more embodiments of this disclosure, a method for rendering a table view is provided, further comprising:

[0145] In some alternative implementations, when the rendering instruction is received, the local structure information has been requested, and the interface window does not contain marked nodes, the view structure within the interface window is rendered according to the constructed view structure.

[0146] According to one or more embodiments of the present disclosure, a rendering apparatus for a table view is provided, the apparatus comprising:

[0147] The receiving module is used to receive rendering instructions for the table view;

[0148] The request module is used to request the local structure information from the server when the local structure information corresponding to the rendering instruction has not been requested; wherein, the local structure information includes local group node information and record node information;

[0149] The construction module is used to create a new view structure when the view structure of the table view has not been constructed, and to set the nodes of the view structure according to the requested local structure information;

[0150] An update module is used to update the nodes of the view structure according to the requested local structure information, provided that the view structure of the table view has been constructed.

[0151] The rendering module is used to render the view structure within the interface window.

[0152] The above description is merely an embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0153] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0154] Although this disclosure has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method for rendering a table view, comprising: Receive rendering instructions for the table view; If the local structure information corresponding to the rendering instruction is not requested, the local structure information is requested from the server; wherein, the local structure information includes local group node information and record node information; If the view structure of the table view has not been built, a new view structure is created, and the nodes of the view structure are set according to the requested local structure information; If the view structure of the table view has been constructed, the nodes of the view structure are updated according to the requested local structure information; Render the view structure within the interface window.

2. The method according to claim 1, wherein, The rendering instructions for the table view are generated based on the browsing operation of the table view; Updating the nodes of the view structure according to the requested local structure information includes adding nodes to the already constructed view structure.

3. The method according to claim 1 or 2, further comprising: Receive editing instructions from the table view; If the edit command causes a change in the view structure, the nodes within the view structure that have changed are marked.

4. The method according to claim 3, further comprising: The first editing description information is generated according to the editing instructions, and the first editing description information is sent to the server so that the server updates the table data of the table view according to the first editing description information; Upon receiving the first update success message from the server, and if the interface window contains the marked node, the system re-requests the local structure information from the server to re-render the view structure within the interface window; wherein the first update success message corresponds to the first edit description information.

5. The method according to any one of claims 1-4, further comprising: Receive the second edit description information sent by the server; wherein the second edit description information is generated by a client other than this client; Upon receiving the second update success message sent by the server, the changed nodes within the view structure are marked according to the second edit description information; The second update success message corresponds to the second edit description information.

6. The method according to any one of claims 3 or 5, further comprising: Upon receiving the rendering instruction, having already requested the local structure information, and with the interface window containing marked nodes, the system re-requests the local structure information from the server to re-render the view structure within the interface window.

7. The method according to any one of claims 1-5, further comprising: Upon receiving the rendering instruction, having requested the local structure information, and when the interface window does not contain any marked nodes, the view structure within the interface window is rendered according to the constructed view structure.

8. A rendering apparatus for a table view, comprising: The receiving module is configured to receive rendering instructions for the table view; The request module is configured to request the local structure information from the server when the local structure information corresponding to the rendering instruction is not requested; wherein the local structure information includes local group node information and record node information; The construction module is configured to create a new view structure if the view structure of the table view has not been constructed, and to set the nodes of the view structure according to the requested local structure information; The update module is configured to update the nodes of the view structure based on the requested local structure information, provided that the view structure of the table view has been constructed. The rendering module is configured to render the view structure within the interface window.

9. An electronic device, comprising: One or more processors; Storage device, configured to store one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the table view rendering method as described in any one of claims 1-7.

10. A storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a rendering method for a table view as described in any one of claims 1-7.

11. A computer program product comprising a computer program that, when executed by a processor, implements the rendering method of a table view as described in any one of claims 1-7.

Images