Software interface interaction system based on browser

Abstract

The invention provides a browser-based software interface interaction system, which comprises an interface design module used for designing interface display elements corresponding to a function demand library, and the interface display elements comprise a plurality of data triggering objects; the interface display module is used for responding to the triggering operation of the user equipment on the function demand library and displaying a plurality of data triggering objects corresponding to the function demand library and the application description data associated with each data triggering object in the correspondingly packaged browser page; the interface data application module is used for responding to a triggering operation of the user equipment on the application description data associated with the data triggering object and generating triggering application information of the data description information associated with the data triggering object; and the interface data updating module is used for updating the application description data associated with the data triggering object based on the triggering application information of the application description data associated with the data triggering object. Therefore, the interface interaction experience feeling of the user is effectively improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the technical field of interface interaction, and in particular, to a software interface interaction system based on a browser. Background Art

[0002] The interactive interface is the channel for information exchange between people and computer devices. Users can input information and perform operations on computer devices through the interactive interface, and computer devices can provide information to users through the interactive interface for users to read, analyze and judge.

[0003] In the prior art, interface development requires certain programming skills, and most interface development is completed by programmers. However, programmers generally find it difficult to design a relatively ideal interface scenario, and different programmers have different interface design capabilities, which will lead to inconsistent interface styles displayed by the overall software interface, affecting user interface interaction. Summary of the invention

[0004] The embodiments described herein provide a browser-based software interface interaction system that overcomes the above-mentioned problems.

[0005] According to the content of the present disclosure, a browser-based software interface interaction system is provided, comprising: an interface design module, an interface display module, an interface data application module and an interface data update module; the interface design module is connected to the interface display module, the interface display module is connected to the interface data application module, and the interface data application module is connected to the interface data update module;

[0006] The interface design module is used to design interface display elements corresponding to the function requirement library, and the interface display elements include: a plurality of data triggerable objects, each of which is associated with application description data with a triggerable triggering state;

[0007] The interface display module is used to display a plurality of data triggerable objects corresponding to the function requirement library and application description data associated with each data triggerable object in a corresponding encapsulated browser page in response to a triggering operation of the user device on the function requirement library;

[0008] The interface data application module is used to generate trigger application information of the data description information associated with the data triggerable object in response to the trigger operation of the user equipment on the application description data associated with the data triggerable object;

[0009] The interface data updating module is used to update the application description data associated with the data-triggerable object based on the triggering application information of the application description data associated with the data-triggerable object.

[0010] Optionally, when the application description data associated with the data triggerable object is the number of object applications, the triggering application information of the application description data associated with the data triggerable object is a change value of the number of applications;

[0011] The interface data updating module is specifically used for:

[0012] Based on the application count change value of the application description data associated with the data-triggerable object, the application description data associated with the data-triggerable object is updated.

[0013] Optionally, when the application description data associated with the data triggerable object is a data download indication, the triggering application information of the application description data associated with the data triggerable object is a data download completion identifier;

[0014] The interface data updating module is specifically used for:

[0015] Based on a data download completion flag of the application description data associated with the data-triggerable object, the application description data associated with the data-triggerable object is updated.

[0016] Optionally, it also includes: an interface data monitoring module;

[0017] The interface data monitoring module is used to monitor the application description data associated with each of the data triggerable objects corresponding to the functional requirement library, and when it is determined that the application description data associated with the target triggerable object does not meet the preset conditions, send a trigger state adjustment indication of the application description data associated with the target triggerable object to the interface display module;

[0018] The interface display module is further configured to adjust the trigger state of the application description data associated with the target triggerable object in response to the trigger state adjustment instruction.

[0019] Optionally, the interface data application module is further configured to send a data trigger prompt to the user device in response to a trigger operation of the user device on the application description data associated with the target triggerable object;

[0020] The data trigger prompt is used to describe that the application description data associated with the target triggerable object has no corresponding trigger data.

[0021] Optionally, the interface data application module is further used to obtain other triggerable objects associated with the target triggerable object, and send data display indications corresponding to the other triggerable objects to the interface display module;

[0022] The interface display module is further configured to display the other triggerable objects and application description data associated with the other triggerable objects in response to the data display indication.

[0023] Optionally, the interface display element further includes: a plurality of interface display objects, each of which is not associated with application description data whose triggering state is triggerable;

[0024] The interface display module is also used to display each of the interface display objects.

[0025] Optionally, each of the data-triggerable objects corresponds to a regional display identifier;

[0026] The interface display module is specifically used for:

[0027] In response to a triggering operation of the function requirement library by a user device, obtaining a region display identifier corresponding to each of the data-triggerable objects;

[0028] Determine the page display area corresponding to each of the data-triggerable objects based on the area display identifier corresponding to each of the data-triggerable objects;

[0029] In the corresponding encapsulated browser page, a plurality of the data-triggerable objects and application description data associated with each of the data-triggerable objects are displayed based on the page display area corresponding to each of the data-triggerable objects.

[0030] Optionally, the interface design module is further used to design first display objects and second display objects corresponding to other requirement libraries;

[0031] The interface display module is further configured to display the first display object and the second display object in a browser page that displays data of the functional requirement library in response to a triggering operation of the user device on the other requirement library.

[0032] Optionally, the interface display module is further used to display the first display object and the second display object in a browser page encapsulated corresponding to the other demand library in response to a triggering operation of the user device on the other demand library.

[0033] The browser-based software interface interaction system provided by the embodiment of the present application includes: an interface design module, an interface display module, an interface data application module and an interface data update module; the interface design module is connected to the interface display module, the interface display module is connected to the interface data application module, and the interface data application module is connected to the interface data update module; the interface design module is used to design interface display elements corresponding to the function requirement library, and the interface display elements include: multiple data triggerable objects, each data triggerable object is associated with application description data with a trigger state of triggerable; the interface display module is used to respond to the user device's triggering operation on the function requirement library, and display the multiple data triggerable objects corresponding to the function requirement library and the application description data associated with each data triggerable object in the corresponding encapsulated browser page; the interface data application module is used to respond to the user device's triggering operation on the application description data associated with the data triggerable object, and generate trigger application information of the data description information associated with the data triggerable object; the interface data update module is used to update the application description data associated with the data triggerable object based on the trigger application information of the application description data associated with the data triggerable object. In this way, interface display elements with a unified style are designed through the interface design module, which makes it easier for the interface display module to display the interactive interface to the user, and the interface is updated in real time based on user operations through the interface data application module and the interface data update module, effectively improving the user's interface interaction experience.

[0034] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the embodiment of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments will be briefly described below. It should be noted that the drawings described below only relate to some embodiments of the present disclosure, but are not intended to limit the present disclosure, wherein:

[0036] Figure 1 It is a structural diagram of a browser-based software interface interaction system provided by the present disclosure.

[0037] Figure 2 It is a schematic diagram of a page displayed based on a browser provided by the present disclosure.

[0038] Figure 3 It is a structural diagram of another browser-based software interface interaction system provided by the present disclosure.

[0039] Figure 4 It is a structural schematic diagram of a computer device provided by the present disclosure.

[0040] It should be noted that the elements in the drawings are schematic and not drawn to scale. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative work also fall within the scope of protection of the present disclosure.

[0042] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by a person skilled in the art to which the subject matter of the present disclosure belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the specification and the relevant art, and will not be interpreted in an idealized or overly formal form unless otherwise explicitly defined herein. As used herein, a statement that two or more parts are "connected" or "coupled" together shall mean that the parts are joined together directly or through one or more intermediate components.

[0043] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase "embodiments" in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0044] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists, A and B exist at the same time, and B exists. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. Terms such as "first" and "second" are only used to distinguish one component (or a part of a component) from another component (or another part of a component).

[0045] In the description of the present application, unless otherwise specified, "plurality" means more than two (including two), and similarly, "multiple groups" means more than two groups (including two).

[0046] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0047] Figure 1 is a structural diagram of a browser-based software interface interaction system provided by an embodiment of the present disclosure, such as Figure 1 As shown, the browser-based software interface interaction system includes: an interface design module 110 , an interface display module 120 , an interface data application module 130 and an interface data update module 140 .

[0048] The interface design module 110 is connected to the interface display module 120 , the interface display module 120 is connected to the interface data application module 130 , and the interface data application module 130 is connected to the interface data update module 140 .

[0049] The interface design module 110 is used to design interface display elements corresponding to the function requirement library, and the interface display elements include: multiple data triggerable objects, each of which is associated with application description data with a triggerable triggering state.

[0050] Among them, the function requirement library can be some libraries that need to involve function production interfaces, such as software databases. The data triggerable object can be an application, a virtual model, a virtual product, etc. The application description data associated with the data triggerable object can be used to describe the application information of the data triggerable object. For example, when the data triggerable object is a virtual model, the associated application description data can be download controls, next times, etc.

[0051] The display area of ​​the application description data associated with the data triggerable object can be below the display area of ​​the data triggerable object, so as to ensure the association between the application description data and the data triggerable object. Figure 2 As shown, the display area of ​​the data triggerable object is shown in area A1, and the display area of ​​the associated application description data is shown in area A2. The display form of the application description data can be displayed in the form of a virtual control to facilitate users to trigger the application.

[0052] In some embodiments, the interface display element further includes: a plurality of interface display objects, each interface display object is not associated with application description data whose triggering state is triggerable, and the interface display object is in a non-triggerable state and is only displayed for browsing.

[0053] The interface display module 120 is also used to display each interface display object.

[0054] The display area of ​​the interface display object can be displayed separately from the display area of ​​the data triggerable object, see Figure 2 As shown, the display area of ​​an interface display object may be shown as area B. Thus, the triggerable and non-triggerable interface display elements can be effectively distinguished according to the display area, which facilitates the convenience of user interface interaction.

[0055] The interface display module 120 is used to display multiple data triggerable objects corresponding to the function requirement library and application description data associated with each data triggerable object in a corresponding encapsulated browser page in response to a triggering operation of the user device on the function requirement library.

[0056] Among them, the functional requirement library is a database that stores certain virtual application software in the application software to facilitate users to experience software interaction.

[0057] When displaying multiple data-triggerable objects corresponding to the function requirement library and application description data associated with each data-triggerable object, it can be implemented based on a pre-packaged browser.

[0058] For example, the Chromium kernel is encapsulated and called in a multi-process manner, namely, the Browser process + the Render process. The Browser process is the main process, responsible for window management, interface drawing, and network interaction. The CBrowser class implemented in the software provides the external interface of the Browser process, such as browser creation, web page loading, setting and obtaining web page control values, registering js functions and their matching C++ function relationships, executing js statements, etc. The Render process is the rendering process, responsible for web page rendering and js execution, etc.

[0059] Implement a Helper.exe as the Rendere process in the software. Initialize Chromium when the software starts, set multi_threaded_message_loop to true, and set browser_subprocess_path to the path of Helper.exe, that is, Chromium can be used in multi-process form.

[0060] In some embodiments, each data triggerable object corresponds to a region display identifier. Different distinguishing display identifiers can be used to sort the positions of multiple data triggerable objects, so as to facilitate the rapid distribution of multiple data triggerable objects.

[0061] The interface display module 120 is specifically used for:

[0062] In response to a triggering operation of a user device on a function requirement library, an area display identifier corresponding to each data-triggerable object is obtained; based on the area display identifier corresponding to each data-triggerable object, a page display area corresponding to each data-triggerable object is determined; in a corresponding encapsulated browser page, multiple data-triggerable objects and application description data associated with each data-triggerable object are displayed based on the page display area corresponding to each data-triggerable object.

[0063] Among them, when determining the page display area corresponding to each data triggerable object based on the area display identifier corresponding to each data triggerable object, the position priority of each data triggerable object can be identified according to the area display identifier, and the data triggerable objects with higher position priority can be arranged in the front row of the page display area.

[0064] Therefore, by reasonably distributing the positions of objects that can be triggered by different data, the aesthetics and rationality of the interactive interface display can be effectively improved.

[0065] The interface data application module 130 is used to generate trigger application information of data description information associated with a data triggerable object in response to a trigger operation of a user device on application description data associated with a data triggerable object.

[0066] The user may use a data-triggerable object by performing a triggering operation such as clicking or double-clicking on the application description data associated with the data-triggerable object through a user device.

[0067] The interface data updating module 140 is used to update the application description data associated with the data triggerable object based on the triggering application information of the application description data associated with the data triggerable object.

[0068] In some embodiments, when the application description data associated with the data triggerable object is the number of object applications, the triggering application information of the application description data associated with the data triggerable object is the application number change value.

[0069] The interface data updating module 140 is specifically used for:

[0070] Based on the application count change value of the application description data associated with the data triggerable object, the application description data associated with the data triggerable object is updated.

[0071] The object application times can be used to constrain the user application times of the data triggerable object. After the application description data associated with a data triggerable object is triggered once, the interface data application module 130 generates an application times change value (such as 1), and the interface data update module 140 reduces the object application times of the application description data associated with the data triggerable object by 1, so as to update the application description data in real time, so as to ensure the practicality of the application description data associated with the data triggerable object.

[0072] In some other embodiments, when the application description data associated with the data-triggerable object is a data download indication, the triggering application information of the application description data associated with the data-triggerable object is a data download completion identifier.

[0073] The interface data updating module 140 is specifically used for:

[0074] Based on the data download completion identifier of the application description data associated with the data triggerable object, the application description data associated with the data triggerable object is updated.

[0075] Among them, when the application description data associated with the data-triggerable object is a data download indication, the user can trigger the application description data associated with the data-triggerable object to realize the application download of the data-triggerable object, and the interface data application module 130 will generate a data download completion mark to prompt the interface data update module 140 to update the application description data associated with the data-triggerable object, such as updating the application description data associated with the data-triggerable object from a data download indication to a data viewing indication.

[0076] In addition, when the application description data associated with the data triggerable object is a data viewing indication, if the user device triggers the application description data, the interface data application module 130 can directly obtain the content corresponding to the data triggerable object from the local database and send it to the user device for viewing.

[0077] The browser-based software interface interaction system provided in this embodiment includes: an interface design module, an interface display module, an interface data application module and an interface data update module; the interface design module is connected to the interface display module, the interface display module is connected to the interface data application module, and the interface data application module is connected to the interface data update module; the interface design module is used to design interface display elements corresponding to the function requirement library, and the interface display elements include: multiple data triggerable objects, each data triggerable object is associated with application description data with a trigger state of triggerable; the interface display module is used to respond to the user device's triggering operation on the function requirement library, and display the multiple data triggerable objects corresponding to the function requirement library and the application description data associated with each data triggerable object in the corresponding encapsulated browser page; the interface data application module is used to respond to the user device's triggering operation on the application description data associated with the data triggerable object, and generate trigger application information of the data description information associated with the data triggerable object; the interface data update module is used to update the application description data associated with the data triggerable object based on the trigger application information of the application description data associated with the data triggerable object. In this way, interface display elements with a unified style are designed through the interface design module, which makes it easier for the interface display module to display the interactive interface to the user, and the interface is updated in real time based on user operations through the interface data application module and the interface data update module, effectively improving the user's interface interaction experience.

[0078] When the interface interaction is implemented in this embodiment, the interaction of the web page interface logic itself is implemented by js itself. The interaction between the web page interface control and the software business logic is implemented by the js function to call the C++ function. For example, when the browser is created in the software, the js function and C++ function in this interface that require the web page to interact with the software business logic are registered to CBrowser and cached in a table (such as function table A); CBrowser adds a derivative relationship with CefLifeSpanHandler and rewrites the OnAfterCreated function. When the browser object is created, it will enter the OnAfterCreated function, in which a shared memory is created with the string "Ro_browser_mem_" plus the created browser ID as the name, and the js function name in the function table A registered by the software to the browser is written into the shared memory; Helper.exe creates a derivative relationship with CefRenderProcessHandler, rewrites the OnContextCreated method of CefRenderProcessHandler, opens the shared memory with the string "Ro_browser_mem_" plus the created browser ID as the name, and reads the written js function name.Then, the CreateFunction and SetValue methods provided by the ChromiumV8 engine are used to register the js function to the context of the V8 engine; a derivative relationship with CefV8Handler is created in Helper.exe, and the Execute function is rewritten. When the js function registered in the page is called, the Execute function is entered, in which a CefProcessMessage object (such as objMsg) is created, and the js function name and function parameters are set to objMsg. A shared memory is created with the name of a string composed of the agreed string "Ro_browser_mem_" plus the created browser ID plus the agreed string "_RoShared", a flag indicating that the js function has not been executed is written, objMsg is sent to the Browser process through SendProcessMessage, and then the above shared memory is read through a while loop. The js function execution completion flag is used to block the Render process and wait for the Browser process to process the call of the js function; CBrowser adds a derived relationship with CefClient and rewrites the OnProcessMessageReceived function to receive the message sent by the Render process, parses the js function name and function parameters from the message object, finds the C++ function corresponding to the js function from the function table A according to the js function name, executes the function and passes in the function parameters. After the C++ function is executed, open the shared memory with the name of the string composed of the agreed string "Ro_browser_mem_" plus the created browser ID plus the agreed string "_RoShared", write the js function execution completion flag, and then write the js function execution result. After the shared memory is updated, the js function execution completion flag can be read in the while loop, and then the js function execution result is read.

[0079] When implementing data interaction, set global data: when designing a web page, define the global variables that need to be used, that is, the Var variable, determine the name, and encapsulate the SetGlobalStringValue function in the CBrowser class. Concatenate the assigned js string as follows, "window.paraName="paraValue";", paraName is the name of the global variable, paraValue is the value to be set to the global variable, and call the ExecuteJavaScript method of CefFrame to pass in the concatenated assignment string to refresh the value to the Var variable on the js side; Set the value of the web page control: support setting string and bool type values, CBrowser class encapsulates the SetBoolValue function to set bool type data, and concatenate the js string "document.getElementById("paraCtrlID").checked=1;" or "document.getElementById("paraCtrlID").value=paraValue;", paraCtrlID is the web page control ID, and call CefFrame's ExecuteJavaScript The method passes the concatenated assignment string to refresh the bool value to the control on the js side. The CBrowser class encapsulates the SetStringValue function to set the string data, in which the js string "document.getElementById("paraCtrlID").value="paraValue";" is concatenated. The ExecuteJavaScript method of CefFrame is called to pass the concatenated assignment string to refresh the string value to the control on the js side. Get global / string type web control data: The CBrowser class encapsulates the GetGlobalStringValue function to get global data, and creates a CefProcessMessage message object named "RoGetStringValue" in the function. Get global data with the "window.paraName;" js statement as the message parameter, and get string type web control data with "document.getElementById("paraCtrlID").value;" as the message parameter, and send this message to the Render process through SendProcessMessage.After sending, create a shared memory in the function with the name of the string composed of the agreed string "Ro_browser_mem_" plus the created browser ID plus the agreed string "_RoGetStringValue", read the data completion mark, if not read, block the process and keep reading, create a derived relationship with CefRenderProcessHandler in Helper.exe (Render process), rewrite the OnProcessMessageReceived function, intercept the message named "RoGetStringValue" in the function, get the message parameters, that is, get the value of the js statement, and then call the Eval method of CefV8Context to pass in the js statement, get the return value, open the browser ID created with the agreed string "Ro_browser_mem_" plus the specified string, and then call the Eval method of CefV8Context to pass in the specified string, get the return value, and then open the browser ID created with the agreed string "Ro_browser_mem_". The shared memory is named after the string composed of the agreed string "_RoGetStringValue". The return value is written first, and then the flag for completing the data acquisition is written. After the shared memory is refreshed, the flag for completing the data acquisition will be obtained, and then the result can be read to obtain the global data value. Get bool type web page control data: The steps for getting bool type are similar to the above, except that the CefProcessMessage message created by the Browser process is named "RoGetBoolValue", and the parameter is "document.getElementById("paraCtrlID").checked;", and the created shared memory is named after the agreed string "Ro_browser_mem_" plus the created browser ID plus the agreed string "_RoGetBoolValue". The message intercepted in the Render process is named "RoGetBoolValue", and the opened shared memory is named after the agreed string "Ro_browser_mem_" plus the created browser ID plus the agreed string "_RoGetBoolValue".

[0080] like Figure 3 As shown, the browser-based software interface interaction system further includes: an interface data monitoring module 150 ; the interface data monitoring module 150 is connected to the interface display module 120 .

[0081] The interface data monitoring module 150 is used to monitor the application description data associated with each data triggerable object corresponding to the function requirement library, and when it is determined that the application description data associated with the target triggerable object does not meet the preset conditions, send a trigger status adjustment indication of the application description data associated with the target triggerable object to the interface display module 120.

[0082] When the application description data associated with the data triggering object is a change value of the number of applications, the corresponding preset condition is a preset number threshold.

[0083] The interface display module 120 is further configured to adjust the trigger state of the application description data associated with the target triggerable object in response to the trigger state adjustment instruction.

[0084] When receiving the trigger state adjustment instruction sent by the interface data monitoring module 150 , the interface display module 120 may adjust the trigger state of the application description data associated with the target triggerable object to non-triggerable, so as to facilitate normal browsing by other users.

[0085] In some embodiments, the interface data application module 130 is further configured to send a data trigger prompt to the user device in response to a trigger operation of the user device on the application description data associated with the target triggerable object.

[0086] The data trigger prompt is used to describe that the application description data associated with the target triggerable object has no corresponding trigger data, that is, the application description data associated with the target triggerable object in the current state cannot be triggered, so that the user can timely understand the trigger status of the application description data associated with the target triggerable object.

[0087] In some embodiments, the interface data application module 130 is also used to obtain other triggerable objects that have an association relationship with the target triggerable object, and send data display indications corresponding to the other triggerable objects to the interface display module 120; the interface display module 120 is also used to display other triggerable objects and application description data associated with other triggerable objects in response to the data display indication.

[0088] Among them, when displaying other triggerable objects and application description data associated with other triggerable objects, the interface display module 120 can display other triggerable objects in the page display area of ​​the target triggerable object, and display application description data associated with other triggerable objects in the page display area of ​​the application description data associated with the target triggerable object, so as to facilitate users to effectively apply the associated data.

[0089] In some embodiments, the interface design module 110 is also used to design the first display object and the second display object corresponding to other requirement libraries; the interface display module 120 is also used to display the first display object and the second display object in the browser page that displays data of the functional requirement library in response to the triggering operation of the user device on other requirement libraries.

[0090] Among them, other requirement libraries include other functional requirement libraries, equipment databases, software databases, etc.

[0091] The first display object corresponding to the other demand library is a display object associated with target description data whose trigger state is triggerable. The second display object corresponding to the other demand library is a display object not associated with target description data whose trigger state is triggerable. When displaying the first display object and the second display object, the target description data associated with the first display object can also be displayed.

[0092] Therefore, when the user triggers the two databases in sequence, the display objects and description data corresponding to the two databases can be displayed in the same browser page, which is convenient for the user to compare and view the data contents in the two databases.

[0093] In some embodiments, the interface display module 120 is further configured to display the first display object and the second display object in the browser page corresponding to the package of the other demand library in response to the triggering operation of the user device on the other demand library.

[0094] Among them, the browser page encapsulated corresponding to other requirement libraries and the browser page for displaying data in the functional requirement library are different browser pages. By independently displaying the data content in the corresponding database in different browser pages, it is convenient for users to independently view the data content in different databases.

[0095] In this embodiment, a browser is encapsulated based on the Chromium kernel, the browser is integrated into the software, and a browser is created at the function where the interface needs to be displayed to open and display the web page, and UI (User Interface) interaction and data exchange can be performed. The interface is designed by the product manager, handed over to the artist for drawing, and the front-end cuts the picture to produce offline or online html (HyperText Markup Language) web pages, which not only meets the requirements of beautiful and ideal interfaces, but also makes the overall interface style of the software more consistent.

[0096] The present application also provides a computer device that can be used to carry out material processing of overhead line engineering based on intelligent identification. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0097] The computer device includes a memory 410 and a processor 420 that are connected to each other through a system bus. It should be noted that the figure only shows a computer device with a memory 410 and a processor 420, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0098] Computer devices can be computing devices such as desktop computers, notebooks, PDAs, and cloud servers. Computer devices can interact with users through keyboards, mice, remote controls, touch pads, or voice control devices.

[0099] The memory 410 includes at least one type of readable storage medium, and the readable storage medium includes a non-volatile memory or a volatile memory, for example, a flash memory, a hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc., and the RAM may include a static RAM or a dynamic RAM. In some embodiments, the memory 410 may be an internal storage unit of a computer device, for example, a hard disk or a memory of the computer device. In other embodiments, the memory 410 may also be an external storage device of the computer device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, or a flash card (FlashCard) equipped on the computer device. Of course, the memory 410 may also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the memory 410 is generally used to store the operating system and various application software installed on the computer device. In addition, the memory 410 may also be used to temporarily store various data that have been output or are to be output.

[0100] The processor 420 is generally used to perform the overall operation of the computer device. In this embodiment, the memory 410 is used to store program codes or instructions, the program code includes computer operation instructions, and the processor 420 is used to execute the program codes or instructions stored in the memory 410 or process data.

[0101] In this article, the bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus system can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0102] Another embodiment of the present application also provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads a computer-readable program code stored in the computer-readable medium and generates a device for implementing the functional actions specified in each block or combination of blocks in the block diagram.

[0103] Computer-readable media include but are not limited to electronic, magnetic, optical, electromagnetic, infrared storage or semiconductor systems, devices or apparatuses, or any suitable combination of the foregoing, and the storage is used to store program codes or instructions, and the program codes include computer operating instructions.

[0104] For the definitions of memory and processor, please refer to the description of the aforementioned computer device embodiment and will not be repeated here.

[0105] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0106] Each functional unit or module in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0107] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.). The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0108] In the claims, any reference symbols placed between brackets shall not be construed as limiting the claims. The word "comprising" described in the present application does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application can be implemented with the aid of hardware comprising several different elements and with the aid of a suitably programmed computer. In a unit claim that lists a number of devices, several units of these devices may be embodied by the same hardware item. The use of first, second, and third, etc. does not indicate any order, and these words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.

[0109] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A browser-based software interface interactive system, characterized in that: include: Interface design module, interface display module, interface data application module and interface data update module; The interface design module is connected to the interface display module, the interface display module is connected to the interface data application module, and the interface data application module is connected to the interface data update module; The interface design module is used to design interface display elements corresponding to the function requirement library, and the interface display elements include: a plurality of data triggerable objects, each of which is associated with application description data with a triggerable triggering state; The interface display module is used to display a plurality of data triggerable objects corresponding to the function requirement library and application description data associated with each data triggerable object in a corresponding encapsulated browser page in response to a triggering operation of the user device on the function requirement library; The interface data application module is used to generate trigger application information of the data description information associated with the data triggerable object in response to the trigger operation of the user equipment on the application description data associated with the data triggerable object; The interface data updating module is used to update the application description data associated with the data-triggerable object based on the triggering application information of the application description data associated with the data-triggerable object.

2. The system according to claim 1, characterized in that When the application description data associated with the data triggerable object is the number of object applications, the triggering application information of the application description data associated with the data triggerable object is the application number change value; The interface data updating module is specifically used for: Based on the application count change value of the application description data associated with the data-triggerable object, the application description data associated with the data-triggerable object is updated.

3. The system according to claim 1, characterized in that When the application description data associated with the data triggerable object is a data download indication, the triggering application information of the application description data associated with the data triggerable object is a data download completion flag; The interface data updating module is specifically used for: Based on a data download completion flag of the application description data associated with the data-triggerable object, the application description data associated with the data-triggerable object is updated.

4. The system according to claim 2, characterized in that Also includes: Interface data monitoring module; The interface data monitoring module is used to monitor the application description data associated with each of the data triggerable objects corresponding to the functional requirement library, and when it is determined that the application description data associated with the target triggerable object does not meet the preset conditions, send a trigger state adjustment indication of the application description data associated with the target triggerable object to the interface display module; The interface display module is further configured to adjust the trigger state of the application description data associated with the target triggerable object in response to the trigger state adjustment instruction.

5. The system according to claim 4, characterized in that The interface data application module is further configured to send a data trigger prompt to the user device in response to a trigger operation of the user device on the application description data associated with the target triggerable object; The data trigger prompt is used to describe that the application description data associated with the target triggerable object has no corresponding trigger data.

6. The system according to claim 5, characterized in that The interface data application module is further used to obtain other triggerable objects associated with the target triggerable object, and send data display indications corresponding to the other triggerable objects to the interface display module; The interface display module is further configured to display the other triggerable objects and application description data associated with the other triggerable objects in response to the data display indication.

7. The system according to claim 1, characterized in that The interface display element also includes: a plurality of interface display objects, each of which is not associated with application description data whose triggering state is triggerable; The interface display module is also used to display each of the interface display objects.

8. The system according to claim 1, characterized in that Each of the data-triggerable objects has a corresponding area display mark; The interface display module is specifically used for: In response to a triggering operation of the function requirement library by a user device, obtaining a region display identifier corresponding to each of the data-triggerable objects; Determine the page display area corresponding to each of the data-triggerable objects based on the area display identifier corresponding to each of the data-triggerable objects; In the corresponding encapsulated browser page, a plurality of the data-triggerable objects and application description data associated with each of the data-triggerable objects are displayed based on the page display area corresponding to each of the data-triggerable objects.

9. The system according to claim 1, characterized in that The interface design module is also used to design first display objects and second display objects corresponding to other requirement libraries; The interface display module is further configured to display the first display object and the second display object in a browser page that displays data of the functional requirement library in response to a triggering operation of the user device on the other requirement library.

10. The system according to claim 9, characterized in that The interface display module is further used to display the first display object and the second display object in a browser page encapsulated corresponding to the other demand library in response to a triggering operation of the user device on the other demand library.

Images