Component resource management method and device, medium and product
By determining the activity level based on interaction events in dynamic forms and loading only the component resources of highly active fields, the problem of memory consumption and resource waste caused by full loading is solved, achieving smooth display and performance optimization of dynamic forms.
Patent Information
- Application Number
- CN202511683372.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-17
- Publication Date
- 2026-02-17
AI Technical Summary
In existing technologies, the full preloading of dynamic form components leads to a surge in memory usage and a waste of CPU resources, affecting the smoothness of dynamic form display.
By responding to the display of dynamic forms and triggering operations, the activity level is determined based on the interaction event information of the fields. Only component resources with an activity level higher than the threshold are loaded, thereby realizing intelligent management and unloading of component resources.
It reduces memory usage when displaying dynamic forms, improves the loading speed and smoothness of dynamic forms, reduces component loading requests for non-interactive fields, and enhances user experience and device performance.
Smart Images
Figure CN121542033A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of computer technology, and in particular to a component resource management method, device, medium and product. Background Technology
[0002] Dynamic forms are user input components that can be dynamically generated and have their field layout and interaction logic adjusted according to business needs. They are widely used in scenarios such as data collection and workflow approval.
[0003] In existing technologies, the data resources of dynamic form components are displayed using a resource display scheme that involves full preloading and rendering of the entire form. Full preloading of resources leads to a surge in memory usage, and rendering components with non-interactive fields wastes CPU (Central Processing Unit) resources. Summary of the Invention
[0004] This invention provides a component resource management method, device, medium, and product that can selectively load some component resources of dynamic forms, reduce the memory usage when displaying dynamic forms, avoid wasting resources used for component rendering, and make the display process of dynamic forms smoother.
[0005] In a first aspect, embodiments of the present invention provide a component resource management method, the method comprising:
[0006] In response to the operation that triggers the display of the first dynamic form, initialize and display the first dynamic form;
[0007] The activity level of a field in the first dynamic form is determined based on the interaction event information for any field in the first dynamic form.
[0008] Manage the component resources corresponding to the fields in the first dynamic form based on activity level;
[0009] Among them, the component resources loaded during the initialization and display of the first dynamic form are the component resources corresponding to the first field in the last time the first dynamic form was triggered for display. The first field is the field whose activity level is greater than the first activity threshold during the display process.
[0010] In a second aspect, embodiments of the present invention provide a component resource management device, the device comprising:
[0011] The form display module is used to respond to the display trigger operation of the first dynamic form and initialize and display the first dynamic form;
[0012] The form interaction information processing module is used to determine the activity level of a field in the first dynamic form based on the interaction event information for any field in the first dynamic form.
[0013] The form resource management module is used to manage the component resources corresponding to the fields in the first dynamic form based on activity level;
[0014] Among them, the component resources loaded during the initialization and display of the first dynamic form are the component resources corresponding to the first field in the last time the first dynamic form was triggered for display. The first field is the field whose activity level is greater than the first activity threshold during the display process.
[0015] Thirdly, embodiments of the present invention also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the component resource management method as described in any of the embodiments of the present invention.
[0016] Fourthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the component resource management method as described in any of the embodiments of the present invention.
[0017] Fifthly, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the component resource management method as described in any of the embodiments of the present invention.
[0018] In this embodiment of the invention, the first dynamic form is initialized and displayed in response to a display trigger operation. The activity level of each field in the first dynamic form is determined based on interaction event information for any field within the form. The component resources corresponding to the fields in the first dynamic form are managed according to their activity levels. The component resources loaded during the initial display process are those corresponding to the first field in the previous display process, where the first field is the field with an activity level greater than a first activity threshold during the display process. This invention solves the problem of excessive memory consumption when loading all form component resources. It allows for targeted loading of only a portion of the dynamic form's component resources, reducing memory usage during dynamic form display, avoiding waste of resources used for component rendering, and making the dynamic form display process smoother. Attached Figure Description
[0019] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0020] Figure 1A flowchart illustrating a component resource management method provided in an embodiment of the present invention;
[0021] Figure 2 A flowchart illustrating a component resource management example provided in an embodiment of the present invention;
[0022] Figure 3 This is a schematic diagram of the structure of a component resource management device provided in an embodiment of the present invention;
[0023] Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation
[0024] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.
[0025] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this invention, terms such as "first," "second," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with the relevant provisions of national laws and regulations.
[0026] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the relevant content of the solution.
[0027] Figure 1 This is a flowchart illustrating a component resource management method provided in an embodiment of the present invention. This embodiment is applicable to scenarios involving the management of component resources in dynamic forms. The method can be executed by a component resource management device, which can be implemented in software and / or hardware and integrated into a computer device.
[0028] like Figure 1 As shown, the component resource management method includes the following steps:
[0029] S110. In response to the display trigger operation for the first dynamic form, initialize and display the first dynamic form.
[0030] Dynamic forms refer to user input components that can be dynamically generated and have their field layout and interaction logic adjusted according to business needs. They are widely used in scenarios such as data collection and workflow approval, and are typically based on the MVVM (Model-View-View-Model) framework to bind data and views. A dynamic form can be any form that allows a user to interact with data in any business scenario.
[0031] After receiving the trigger operation for displaying the first dynamic form, the first dynamic form will be initialized and displayed. Specifically, during the initialization and display process of the first dynamic form, the basic configuration information of the first dynamic form, such as the field set, layout configuration, and global settings, is first loaded, and the mapping relationship between fields and component resources is parsed. Then, the linkage logic of the initial data is processed to complete the initialization validation. Subsequently, the DOM structure and styles of the page corresponding to the first dynamic form can be rendered, interaction and state management tools are bound, and finally the first dynamic form is displayed.
[0032] During the initialization of the first dynamic form, the loaded component resources may only be those corresponding to a subset of the fields in the field set. These subset fields may be fields determined from the field set according to preset rules.
[0033] S120. Determine the activity level of a field in the first dynamic form based on the interaction event information for any field in the first dynamic form.
[0034] The interactive events can be events that focus on any field during the initial display of the dynamic form. For example, selecting at least one text box corresponding to any field. Furthermore, they can also be events that allow further interaction with the focused text box. For example, these could be data input interactive events, information selection interactive events, or other special component interactions.
[0035] Data input interaction events can be triggered by components such as single-line text boxes, multi-line text boxes, and numeric input boxes, which receive events detected by the user's keyboard input and can update field values in real time. Information selection interaction events can be triggered by components such as dropdown selectors, radio buttons, and checkboxes, which allow users to directly replace field values by clicking on preset options. Special component interaction events can include date pickers that automatically format values after clicking on a date.
[0036] Interaction event information can include information such as the field objects in the interaction event and the time of the interaction event. For data input type interaction events, it can also include information such as the amount of data input and the input speed.
[0037] Field activity can be a quantitative indicator reflecting the frequency of user interaction with the field, with its core being the density of user actions on the field. The activity level of each field can be determined by statistically analyzing the interaction event information, including the number of interactions, interaction duration, or interaction depth, for each field in the first dynamic form.
[0038] Furthermore, in an optional implementation, determining the activity level of a field in the first dynamic form based on interaction event information for any field in the first dynamic form may include the following process:
[0039] First, in response to an interactive operation on any field in the first dynamic form, the interaction event type, interaction event time, and cumulative number of interactions corresponding to the interaction operation are recorded. Then, based on the interaction event type, interaction event time, and cumulative number of interactions corresponding to each field in the first dynamic form, the activity level of each field is determined. The interaction event type includes field data input events and field focus events.
[0040] Determining the activity level of each field can be achieved by weighting the cumulative number of interactions corresponding to the field's focused events and the cumulative number of interactions corresponding to the field's data input events to obtain a first weighted calculation result; determining the time decay factor based on the latest time record in the interaction event time; and using the product of the first weighted calculation result and the time decay factor as the activity level.
[0041] The meaning of "time decay" is that more recent interactions contribute more to activity levels, while the influence of older interactions gradually decreases. This allows activity scores to better reflect the "current level of activity" and avoids excessive interference from historical interactions in the current evaluation. The time decay factor can be calculated by first calculating the time difference between the current timestamp (when updating the activity value) and the timestamp of the last interaction (the interaction time closest to the current time), divided by the number of milliseconds in a day. This gives the number of days since the last interaction. The time decay factor can be calculated using an inverse proportional decay formula, for example, the formula can be expressed as:
[0042] The attenuation coefficient can be adjusted according to business needs; a larger coefficient indicates a faster rate of time decay, while a smaller coefficient indicates a smoother decay.
[0043] In one alternative implementation, before performing weighted calculations, the weight parameters for the cumulative number of interactions corresponding to field focus events and the cumulative number of interactions corresponding to field data input events can be determined based on the business scenario of the first dynamic form. The weight parameter for the cumulative number of interactions corresponding to field focus events can be 0.4, which can be adjusted to 0.3 in a form search scenario; the weight parameter for the cumulative number of interactions corresponding to field data input events can be 0.6, which can be reduced to 0.2 in a business scenario that purely displays fields. Furthermore, the decay coefficient in the time decay factor can be 0.5, which can be set to 0.3 in dynamic form associations for enterprise applications to extend caching.
[0044] It should be noted that the specific rules for determining the activity level of each field are not limited in this embodiment. The specific mapping rules between interaction event information and activity level can satisfy the following logic: the more interactions, the higher the activity level; and the longer the time interval between the last interaction time and the time of determining or updating the activity level value, the lower the activity level.
[0045] S130. Manage the component resources corresponding to the fields in the first dynamic form based on the activity level.
[0046] Managing component resources can include loading, unloading, and caching their state. Components can be categorized into different activity levels based on their activity level values. Then, different loading, unloading, and state caching management strategies can be set for the component resources corresponding to different activity levels.
[0047] During the display of the first dynamic form, the activity level of each field can be dynamically updated based on user interaction with the fields in the form, and the component resources corresponding to fields with low activity levels can be uninstalled. Specifically, the management strategy for uninstalling component resources corresponding to fields in the first dynamic form based on activity level can include: for the first field with an activity level greater than a first activity level threshold, the component resources corresponding to the first field are not uninstalled during the display of the first dynamic form; for the second field with an activity level less than a second activity level threshold, the component resources corresponding to the second field are uninstalled if no interaction event is generated for more than a first duration during the display of the first dynamic form; and for the third field with an activity level between the first and second activity level thresholds, the component resources corresponding to the third field are uninstalled if no interaction event is generated for more than a second duration during the display of the first dynamic form; wherein the first duration is longer than the second duration. This can implement an intelligent recycling mechanism for component resources, performing delayed uninstallation of interactive components corresponding to fields with low activity levels to release memory resources.
[0048] The first activity threshold can be a lower limit threshold used to determine whether the activity is high-frequency activity, and the second activity threshold can be an upper limit threshold used to determine whether the activity is low-frequency activity.
[0049] Managing component resource loading based on activity levels allows for the priority loading of component resources corresponding to fields with high activity levels. In one optional implementation, the component resources loaded during the initial display of the first dynamic form are those corresponding to the first field from the last time the form was triggered for display. This first field is defined as the field whose activity level during the display process exceeds a first activity threshold. This allows loading only component resources with high user engagement and a higher probability of interaction, reducing the initial loading load and thus improving the loading speed of dynamic forms.
[0050] For example, in a specific instance, one can refer to the strategy of hierarchical management based on field activity as shown in Table 1.
[0051] Table 1
[0052]
[0053] Initial loading refers to loading the component resources corresponding to the fields in a dynamic form when it is first displayed after a cold start of the application system. Viewport loading means that the component resources are only loaded when a field appears in the viewport. Interaction-based loading means that the component resources are only loaded when the user interacts with a field.
[0054] It is understood that 0.7 in Table 1 could be the corresponding first activity threshold, and 0.3 could be the corresponding second activity threshold. It is also understood that the values 0.3 and 0.7 used to differentiate activity levels in the table above are merely examples and could be other pre-configured values.
[0055] The technical solution of this invention initializes and displays the first dynamic form in response to a display trigger operation; determines the activity level of a field in the first dynamic form based on interaction event information for any field in the first dynamic form; and manages the component resources corresponding to the fields in the first dynamic form based on the activity level. The component resources loaded during the initial display process of the first dynamic form are the component resources corresponding to the first field in the previous display process of the first dynamic form, where the first field is the field with an activity level greater than a first activity level threshold during the display process. This technical solution solves the problem of excessive memory consumption when loading all form component resources. It allows for targeted loading of some component resources of the dynamic form, reducing memory usage during dynamic form display, avoiding waste of resources used for component rendering, and making the dynamic form display process smoother.
[0056] Compared to existing technologies that preload all form components for dynamic forms regardless of whether fields are visible, the technical solutions described above manage the component resources of dynamic forms, optimizing form performance during application. For example, the initial form loading time is reduced by 40%-60%, and JS execution time is reduced by 35%; memory usage for complex forms (with more than the preset number of fields, such as 200) is reduced from 280MB to 90MB, a reduction of 68%; component loading requests for non-interactive fields are reduced by 75%, and traffic consumption in weak network environments is reduced by 50%; the response speed of frequently interacting fields is improved by 2-3 times, and the scrolling stutter rate is reduced from 18% to below 3%.
[0057] Furthermore, based on the above embodiments, the component resource management process also includes loading the component resource corresponding to any field when it enters the form viewport in the first dynamic form. That is, during the display of the first dynamic form, an Intersection Observer instance can be bound to each field container, and a visibility threshold can be set. When a field enters the viewport and meets the corresponding visibility threshold, component resource loading is triggered, implementing asynchronous component loading logic. This means loading component resources that were not loaded during the initial display of the first dynamic form. The visibility threshold for a field entering the viewport can be set to 0.5 to reduce scroll trigger latency.
[0058] Furthermore, based on the above embodiments, the component resource management process also includes a state caching management strategy for component resources. For example, the data entered in the first dynamic form is cached, but the component instances associated with the input data are not cached.
[0059] Furthermore, based on the above embodiments, the management process of component resources also includes a reconstruction strategy, which may prioritize restoring the most recent input state when reloading.
[0060] In a specific example, the management process for the component resources corresponding to each field in a dynamic form could be as follows: Figure 2 The process is shown.
[0061] Figure 2 The documentation demonstrates the complete lifecycle of a component resource, from unloaded to loaded and then unloaded. Unloaded component resources can be loaded through viewport visibility monitoring or user interaction, and then rendered and displayed after loading. Users can interact with loaded component resources, and components corresponding to fields that are loaded but have no associated interaction events can be unloaded. This allows for differentiated resource management and recycling based on the activity level of component resources for fields.
[0062] In a further, alternative implementation, parameters in the component resource management strategy can be configured to match different dynamic form application scenarios. For example, refer to the scenario adaptation parameter configuration examples provided in Table 2.
[0063] Table 2
[0064]
[0065] The solutions described above can reduce enterprise operating costs and improve user experience and conversion rates.
[0066] Specifically, in enterprise applications, numerous complex forms often lead to wasted server resources and degraded device performance due to redundant loading. This embodiment's solution, through on-demand loading and intelligent resource recycling, can reduce component loading by over 60%, lower server bandwidth costs by approximately 40%, and extend the lifespan of terminal devices, reducing hardware maintenance costs. In industries with extremely high user experience requirements, such as e-commerce and finance, form loading speed and interaction smoothness directly impact user retention and transaction conversion. Taking e-commerce platforms as an example, adopting this embodiment's technical solution can shorten form completion time by 30%, reduce error rates by 40%, thereby improving user satisfaction and conversion rates, and is expected to increase transaction conversion rates by 15% - 25%.
[0067] Figure 3 This is a schematic diagram of the component resource management device provided in an embodiment of the present invention. This embodiment is applicable to scenarios involving the management of component resources of dynamic forms. The device can be implemented in software and / or hardware and integrated into a computer device.
[0068] like Figure 3 As shown, the component resource management device includes: a form display module 210, a form interaction information processing module 220, and a form resource management module 230.
[0069] The form display module 210 is used to initialize and display the first dynamic form in response to the display trigger operation for the first dynamic form; the form interaction information processing module 220 is used to determine the activity level of a field in the first dynamic form based on the interaction event information of any field in the first dynamic form; the form resource management module 230 is used to manage the component resources corresponding to the fields in the first dynamic form according to the activity level; wherein, the component resources loaded by the first dynamic form during the initial display process are the component resources corresponding to the first field in the last triggered display process of the first dynamic form, and the first field is the field whose activity level is greater than the first activity level threshold during the display process.
[0070] The technical solution of this invention initializes and displays the first dynamic form in response to a display trigger operation; determines the activity level of a field in the first dynamic form based on interaction event information for any field in the first dynamic form; and manages the component resources corresponding to the fields in the first dynamic form based on the activity level. The component resources loaded during the initial display process of the first dynamic form are the component resources corresponding to the first field in the previous display process of the first dynamic form, where the first field is the field with an activity level greater than a first activity level threshold during the display process. This technical solution solves the problem of excessive memory consumption when loading all form component resources. It allows for targeted loading of some component resources of the dynamic form, reducing memory usage during dynamic form display, avoiding waste of resources used for component rendering, and making the dynamic form display process smoother.
[0071] In one optional implementation, the form interaction information processing module 220 is specifically used for:
[0072] In response to an interactive operation on any field in the first dynamic form, record the interactive event type, interactive event time, and cumulative number of interactions corresponding to the interactive operation;
[0073] The activity level of each field is determined based on the interaction event type, interaction event time, and cumulative number of interactions corresponding to each field in the first dynamic form.
[0074] The interaction event types include field data input events and field focus events.
[0075] In one alternative implementation, the form interaction information processing module 220 may further be used for:
[0076] For each field, the cumulative number of interactions corresponding to the field focus event and the cumulative number of interactions corresponding to the field data input event are weighted and calculated to obtain the first weighted calculation result;
[0077] Determine the time decay factor based on the latest time record in the interaction event time;
[0078] The product of the first weighted calculation result and the time decay factor is used as the activity level.
[0079] In an alternative implementation, the form interaction information processing module 220 can also be used for:
[0080] Before performing weighted calculations, the weight parameters corresponding to the cumulative number of interactions for the field focus event and the cumulative number of interactions for the field data input event are determined based on the business scenario of the first dynamic form.
[0081] In an alternative implementation, the form display module 210 can also be used for:
[0082] In response to any field in the first dynamic form entering the form viewport, load the component resources corresponding to that field.
[0083] In one alternative implementation, the form resource management module 230 is specifically used for:
[0084] For the first field whose activity level exceeds the first activity threshold, the component resources corresponding to the first field will not be uninstalled during the first dynamic form display process; and,
[0085] For the second field whose activity level is less than the second activity threshold, during the first dynamic form display process, if the second field does not generate an interaction event for more than a first duration, the component resources corresponding to the second field are unloaded; and,
[0086] For the third field whose activity level falls within the range of the first activity threshold and the second activity threshold, during the first dynamic form display process, if the third field does not generate an interaction event for more than the second duration, the component resources corresponding to the third field are unloaded.
[0087] The first duration is longer than the second duration.
[0088] In one alternative implementation, the component resource management device further includes a data caching module for:
[0089] The data entered in the first dynamic form is cached, but the component instances associated with the input data are not cached.
[0090] The component resource management device provided in the embodiments of the present invention can execute the component resource management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.
[0091] Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Figure 4 A block diagram of an exemplary computer device 12 suitable for implementing embodiments of the present invention is shown. Figure 4 The computer device 12 shown is merely an example and should not be construed as limiting the functionality or scope of the embodiments of the present invention. The computer device 12 can be any terminal device with computing capabilities, such as intelligent controllers and servers, mobile phones, and other terminal devices.
[0092] like Figure 4As shown, the computer device 12 is represented in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processing unit 16).
[0093] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.
[0094] Computer device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by computer device 12, including volatile and non-volatile media, removable and non-removable media.
[0095] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (…). Figure 4 Not shown; usually referred to as a "hard drive"). Although Figure 4 As not shown, disk drives for reading and writing to removable non-volatile disks (e.g., "floppy disks") and optical disc drives for reading and writing to removable non-volatile optical discs (e.g., CD-ROMs, DVD-ROMs, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.
[0096] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of the present invention.
[0097] Computer device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with the computer device 12, and / or with any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 22. Furthermore, computer device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with other modules of computer device 12 via bus 18. It should be understood that, although... Figure 4 As not shown, it can be used in conjunction with computer device 12 with other hardware and / or software modules, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0098] Processing unit 16 executes various functional applications and data processing by running programs stored in system memory 28, such as implementing the component resource management method provided in this embodiment, which includes:
[0099] In response to the operation that triggers the display of the first dynamic form, initialize and display the first dynamic form;
[0100] The activity level of a field in the first dynamic form is determined based on the interaction event information for any field in the first dynamic form.
[0101] Manage the component resources corresponding to the fields in the first dynamic form based on activity level;
[0102] Among them, the component resources loaded during the initialization and display of the first dynamic form are the component resources corresponding to the first field in the last time the first dynamic form was triggered for display. The first field is the field whose activity level is greater than the first activity threshold during the display process.
[0103] This embodiment provides a computer-readable storage medium storing a computer program thereon. When executed by a processor, the program implements the component resource management method as provided in any embodiment of the present invention, the method comprising:
[0104] In response to the operation that triggers the display of the first dynamic form, initialize and display the first dynamic form;
[0105] The activity level of a field in the first dynamic form is determined based on the interaction event information for any field in the first dynamic form.
[0106] Manage the component resources corresponding to the fields in the first dynamic form based on activity level;
[0107] Among them, the component resources loaded during the initialization and display of the first dynamic form are the component resources corresponding to the first field in the last time the first dynamic form was triggered for display. The first field is the field whose activity level is greater than the first activity threshold during the display process.
[0108] The computer storage medium of this invention can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. 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 computer-readable storage media (a non-exhaustive list) include: 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), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0109] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.
[0110] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0111] Computer program code for performing the operations of this invention can be written in one or more programming languages or a combination thereof, including 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 it can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0112] Those skilled in the art will understand that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby allowing them to be stored in a storage device for execution by a computing device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.
[0113] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the component resource management method provided in any embodiment of this application.
[0114] In implementing the computer program product, computer program code for performing the operations of this invention 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).
[0115] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.
[0116] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.
Claims
1. A component resource management method, characterized in that, include: In response to a display trigger operation on the first dynamic form, the first dynamic form is initialized and displayed. The activity level of a field in the first dynamic form is determined based on the interaction event information for any field in the first dynamic form. Manage the component resources corresponding to the fields in the first dynamic form based on the activity level; The component resources loaded during the initialization and display of the first dynamic form are the component resources corresponding to the first field in the last time the first dynamic form was triggered for display. The first field is the field whose activity level is greater than the first activity threshold during the display process.
2. The method according to claim 1, characterized in that, The step of determining the activity level of a field in the first dynamic form based on interaction event information for any field in the first dynamic form includes: In response to an interactive operation on any field in the first dynamic form, the interactive event type, interactive event time, and cumulative number of interactions corresponding to the interactive operation are recorded; The activity level of each field is determined based on the interaction event type, interaction event time, and cumulative interaction count corresponding to each field in the first dynamic form. The interaction event types include field data input events and field focus events.
3. The method according to claim 2, characterized in that, The step of determining the activity level of each field based on the interaction event type, interaction event time, and cumulative interaction count corresponding to each field in the first dynamic form includes: For each field, the cumulative number of interactions corresponding to the field focus event and the cumulative number of interactions corresponding to the field data input event are weighted and calculated to obtain a first weighted calculation result; The time decay factor is determined based on the latest time record in the interaction event time; The product of the first weighted calculation result and the time decay factor is taken as the activity level.
4. The method according to claim 3, characterized in that, The method further includes: Before performing the weighted calculation, the weight parameters corresponding to the cumulative number of interactions for the field focus event and the cumulative number of interactions for the field data input event are determined based on the display business scenario of the first dynamic form.
5. The method according to claim 1, characterized in that, Also includes: In response to any field in the first dynamic form entering the form viewport, the component resource corresponding to that field is loaded.
6. The method according to claim 1, characterized in that, The step of managing the component resources corresponding to the fields in the first dynamic form based on the activity level includes: For the first field whose activity level is greater than the first activity threshold, the component resources corresponding to the first field are not uninstalled during the first dynamic form display process; and, For the second field whose activity level is less than the second activity level threshold, during the first dynamic form display process, if the second field does not generate an interaction event for a period of time, the component resources corresponding to the second field are unloaded; and, For the third field whose activity level falls within the range of the first activity level threshold and the second activity level threshold, during the first dynamic form display process, if the third field does not generate an interaction event for more than a second duration, the component resources corresponding to the third field are unloaded. Wherein, the first duration is longer than the second duration.
7. The method according to claim 1, characterized in that, The method further includes: The data entered in the first dynamic form is cached, but component instances associated with the input data are not cached.
8. An electronic device, characterized in that, The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor, when executing the computer program, implements the component resource management method as described in any one of claims 1-7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the component resource management method as described in any one of claims 1-7.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the component resource management method as described in any one of claims 1-7.