CN116382720A - Plug-in processing method, device, computer equipment and storage medium - Google Patents

Plug-in processing method, device, computer equipment and storage medium Download PDF

Info

Publication number
CN116382720A
CN116382720A CN202310404125.XA CN202310404125A CN116382720A CN 116382720 A CN116382720 A CN 116382720A CN 202310404125 A CN202310404125 A CN 202310404125A CN 116382720 A CN116382720 A CN 116382720A
Authority
CN
China
Prior art keywords
plug
package
page
loading
module
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310404125.XA
Other languages
Chinese (zh)
Inventor
赵港阳
林煌东
兰锦
彭振聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Fulin Technology Co Ltd
Original Assignee
Shenzhen Fulin Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Fulin Technology Co Ltd filed Critical Shenzhen Fulin Technology Co Ltd
Priority to CN202310404125.XA priority Critical patent/CN116382720A/en
Publication of CN116382720A publication Critical patent/CN116382720A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the application belongs to the technical field of plug-ins, and relates to a plug-in processing method, which comprises the following steps: obtaining a plug-in package; checking the plug-in type of the plug-in package to obtain a checking result; when the verification result shows that the plug-in realized by the plug-in package is an independent application in a software operation service platform, installing the plug-in at the rear end based on the plug-in package, and uploading front-end resources in the plug-in package to a preset storage position; receiving a plug-in page loading request aiming at the plug-in; generating plug-in routing information based on the plug-in page loading request; and acquiring the front-end resource from the preset storage position according to the plug-in routing information, and loading the plug-in page of the plug-in through the front-end according to the front-end resource to finish plug-in loading. The application also provides a plug-in processing device, computer equipment and a storage medium. The method and the device realize the addition of the plugin serving as the third party application in the software operation service platform.

Description

Plug-in processing method, device, computer equipment and storage medium
Technical Field
The present disclosure relates to the field of plugins, and in particular, to a plugin processing method, device, computer device, and storage medium.
Background
The software operation service (Software as a Service, saaS) refers to a form of obtaining a software service by a user, the SaaS platform is provided with some standard services provided by a provider, and the user can obtain a service with corresponding software functions required by the user from the SaaS platform through a network. However, when a user wants to customize some function applications or wants to add some independent applications, the current SaaS platform cannot do so.
Disclosure of Invention
The embodiment of the application aims to provide a plug-in processing method, a device, computer equipment and a storage medium, so that a plug-in serving as a third party application is added in a software operation service platform.
In order to solve the above technical problems, the embodiments of the present application provide a processing method for a plug-in unit, which adopts the following technical scheme:
obtaining a plug-in package;
checking the plug-in type of the plug-in package to obtain a checking result;
when the verification result shows that the plug-in realized by the plug-in package is an independent application in a software operation service platform, installing the plug-in at the rear end based on the plug-in package, and uploading front-end resources in the plug-in package to a preset storage position;
Receiving a plug-in page loading request aiming at the plug-in;
generating plug-in routing information based on the plug-in page loading request;
and acquiring the front-end resource from the preset storage position according to the plug-in routing information, and loading the plug-in page of the plug-in through the front-end according to the front-end resource to finish plug-in loading.
In order to solve the above technical problems, the embodiments of the present application further provide a card processing device, which adopts the following technical scheme:
the plug-in package acquisition module is used for acquiring plug-in packages;
the type verification module is used for verifying the plug-in type of the plug-in package to obtain a verification result;
the back-end installation module is used for installing the plug-in on the back-end based on the plug-in package and uploading front-end resources in the plug-in package to a preset storage position when the verification result shows that the plug-in realized by the plug-in package is an independent application in a software operation service platform;
the request receiving module is used for receiving a plug-in page loading request aiming at the plug-in;
the route generation module is used for generating plug-in route information based on the plug-in page loading request;
the front-end loading module is used for acquiring the front-end resources from the preset storage position according to the plug-in routing information, and loading plug-in pages of the plug-ins according to the front-end resources through the front end to finish plug-in loading.
To solve the above technical problem, embodiments of the present application further provide a computer device, where the computer device includes a memory and a processor, where the memory stores computer readable instructions, and the processor executes the computer readable instructions to implement the steps of the plug-in processing method as described above.
To solve the above technical problem, embodiments of the present application further provide a computer readable storage medium, where computer readable instructions are stored on the computer readable storage medium, where the computer readable instructions implement the steps of the plug-in processing method as described above when being executed by a processor.
Compared with the prior art, the embodiment of the application has the following main beneficial effects: obtaining a plug-in package, wherein the plug-in package is installed to obtain a plug-in, and the plug-in is an independent and third-party application in a software operation service platform; based on the plug-in package, installing the plug-in at the rear end, and uploading front-end resources in the plug-in package to a preset storage position, wherein the front-end resources are used for loading the plug-in at the front end; receiving a plug-in page loading request aiming at a plug-in, wherein the plug-in page loading request records the plug-in page of which plug-in is to be loaded at the front end, so that plug-in routing information of the plug-in can be generated; the preset storage position for storing the front-end resource of the plugin can be accessed according to the plugin routing information, so that the front-end loads the plugin page of the plugin according to the acquired front-end resource, the plugin loading is completed, and the independent plugin serving as a third-party application is added into the software operation service platform.
Drawings
For a clearer description of the solution in the present application, a brief description will be given below of the drawings that are needed in the description of the embodiments of the present application, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow chart of one embodiment of a plug-in processing method according to the present application;
FIG. 3 is a schematic diagram of an embodiment of a card processing device according to the present application;
FIG. 4 is a schematic structural diagram of one embodiment of a computer device according to the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the applications herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In order to better understand the technical solutions of the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the terminal devices 101, 102, 103.
It should be noted that, the plug-in processing method provided in the embodiments of the present application is generally executed by a server, and accordingly, the plug-in processing device is generally disposed in the server.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continued reference to FIG. 2, a flow chart of one embodiment of a plug-in processing method according to the present application is shown. The plug-in processing method comprises the following steps:
Step S201, obtaining a plug-in package.
In this embodiment, the electronic device (for example, the server shown in fig. 1) on which the plug-in processing method operates may communicate with the terminal device through a wired connection manner or a wireless connection manner. It should be noted that the wireless connection may include, but is not limited to, 3G/4G/5G connection, wiFi connection, bluetooth connection, wiMAX connection, zigbee connection, UWB (ultra wideband) connection, and other now known or later developed wireless connection.
Specifically, the server obtains a package of plugins, which may be an installation package of plugins, and the package of plugins obtains plugins after being installed in a software operation service platform (SaaS platform).
Step S202, checking the plug-in type of the plug-in package to obtain a checking result.
Specifically, the package of plug-ins may be installed to obtain plug-ins. The plug-in package is firstly subjected to plug-in type verification to determine the type of the application obtained after the plug-in package is installed, namely, whether the plug-in package is actually an installation package of the plug-in application is verified, and a verification result is obtained.
The application in the application includes two kinds, including a system application and a plug-in application, and the plug-in application is a plug-in; the native application of the software operation service platform is a system application, and the application realized by the plug-in can be an independent application from a third party.
In the application, the plug-in can be an independent application program, and has a complete front-end page and complete back-end support, and has own middleware such as an operation environment, a database and the like.
Step S203, when the verification result shows that the plug-in realized by the plug-in package is an independent application in the software operation service platform, the plug-in is installed at the rear end based on the plug-in package, and front-end resources in the plug-in package are uploaded to a preset storage position.
Specifically, when the verification result indicates that the plug-in implemented by the plug-in package is an independent application in the software operation service platform, an installation procedure of the plug-in application may be executed. The installation of the plug-in involves a front end and a back end, wherein the front end may be a client used by a user and the back end is located in a server. The installation flow of the plug-in unit is that firstly, based on a plug-in package, the plug-in unit is installed at the rear end; the package of plug-ins also contains front-end resources, which are resources required for loading plug-ins at the front end, for example, html, css, javascript and other types of resources. Some storage positions are preset in the server, and front-end resources in the plug-in package can be uploaded to the preset storage positions.
In one embodiment, the front-end resources required by the system applications and the front-end resources required by the plug-ins are stored in different storage locations.
Step S204, receiving a plug-in page loading request for the plug-in.
Specifically, the plug-in has a plug-in page in the software operation service platform, and the size or the display range of the plug-in page may not be limited. The plug-in is intended to be used by the user, and the plug-in needs to complete loading at the front end and display the plug-in page at the front end.
The loading of the front end of the plugin is performed based on the received plugin page loading request. In one embodiment, after a user logs into the software operating service platform, the software operating service platform triggers a plug-in page load request for a plug-in.
Step S205, based on the plug-in page loading request, plug-in routing information is generated.
Specifically, the plug-in page loading request includes the plug-in page of which plug-in to be loaded, and plug-in routing information can be generated according to the plug-in, and the plug-in routing information of different plug-ins has uniqueness.
Step S206, obtaining front-end resources from a preset storage position according to the plug-in routing information, and loading plug-in pages of the plug-ins according to the front-end resources through the front end to finish plug-in loading.
Specifically, the plug-in routing information is used to indicate that the front-end resource is obtained from the server, and it can be understood that, according to the plug-in routing information, a preset storage location storing the front-end resource can be accessed, so that the front-end resource at the preset storage location is obtained. And the front end loads the plug-in page of the plug-in according to the front end resource to finish plug-in loading. The user may use the plug-in to implement the functionality of the plug-in.
In the embodiment, a plug-in package is obtained, and the plug-in package is installed to obtain a plug-in, wherein the plug-in is an independent and third-party application in a software operation service platform; based on the plug-in package, installing the plug-in at the rear end, and uploading front-end resources in the plug-in package to a preset storage position, wherein the front-end resources are used for loading the plug-in at the front end; receiving a plug-in page loading request aiming at a plug-in, wherein the plug-in page loading request records the plug-in page of which plug-in is to be loaded at the front end, so that plug-in routing information of the plug-in can be generated; the preset storage position for storing the front-end resource of the plugin can be accessed according to the plugin routing information, so that the front-end loads the plugin page of the plugin according to the acquired front-end resource, the plugin loading is completed, and the independent plugin serving as a third-party application is added into the software operation service platform.
Further, the step S202 may include: reading configuration information in a plug-in package; extracting the verification table identification of the plug-in from the configuration information; obtaining a pre-configured plug-in checking table, and inquiring a slot identifier corresponding to the checking table identifier in the plug-in checking table; and when the slot mark is a preset character string, checking the plug-in package, and generating a checking result indicating that the checking is passed, so as to indicate that the plug-in package realized plug-in is an independent application in the software operation service platform.
Specifically, the package of plug-ins is checked prior to installation. The plug-in package is provided with a plug-in configuration file plugin.yaml, configuration information is arranged in the plug-in configuration file plugin, and information related to plug-in declaration and plug-in configuration is arranged in the configuration information.
The back end reads configuration information in the plug-in package and extracts the verification table identification of the plug-in therefrom; the verification table identifier is an identifier in a plug-in package used when the plug-in package is verified. In this application, the plug-in is composed of a plurality of functional modules, the modules have an identification code (moduleUUID), or called module id, which is unique within the plug-in; the plug-in also has an identification code (pluginuid), which is written in the plug-in package for both the plug-in and the module. A main module exists in the functional modules of the plug-in, and the identification code of the main module is called as a main module identification code. In the application, the identification code of the main module can be used as a verification table identification, or the identification code of the plug-in unit and the identification code of the main module are spliced together to be used as the verification table identification.
The page of the software operation service platform is provided with a slot, which is a occupation space on the page of the platform, and indicates that UI (User Interface) and interaction can support plug-in expansion. The slots have a slot identification moduleType, which has different specific values or strings, corresponding to slots of different page capabilities.
The server stores a plug-in check table in advance, and records slot identifiers corresponding to different check table identifiers. And inquiring the slot identification corresponding to the check table identification in the plug-in check table, if the inquired slot identification is a preset character string (the preset character string is a specific value of the slot identification moduleType, a specific slot can be uniquely identified, for example, the preset character string can be one: app: new, which means that the slot to be used by the plug-in package supports independent and third party applications, and plug-in expansion can be performed through the slot), at this time, checking the plug-in package passes, and generating a check result which means that the check passes, wherein the check result means that the plug-in realized by the plug-in package is an independent application in a software operation service platform, and the installation flow of the plug-in application can be executed.
In this embodiment, a verification table identifier of the plug-in is extracted from configuration information of the plug-in package, and a slot identifier corresponding to the verification table identifier is queried in the plug-in verification table; when the slot mark is a preset character string, the expansion of the plug-in is supported by the slot, and the package of the plug-in is checked to pass, so that invalid installation is avoided.
Further, the step S203 may include: generating an application object of the plug-in based on the plug-in package, wherein the application object has the same object structure as an application object of a system application in a software operation service platform; injecting the application object of the plug-in into the rear end of the software operation service platform; and uploading the front-end resources in the plug-in package to a preset position in the back-end.
Specifically, the application object of the plug-in is generated according to the plug-in package, and the application object can express the structure and also can be used as a carrier of data. The system application in the software operation service platform also has an application object, and the application object of the plug-in and the application object of the system application have the same object structure, so that the expression form of the plug-in can be kept consistent with the system application in the software operation service platform.
Injecting the application object of the plug-in into the rear end of the software operation service platform, thereby completing the installation of the plug-in at the rear end; and then uploading the front-end resources in the plug-in package to a preset position in the back-end, and preparing data for loading the plug-in pages of the front-end.
In the embodiment, an application object of the plug-in is generated based on the plug-in package, the object structure of the application object is consistent with the system application in the software operation service platform, and the consistency of the expression form of the plug-in and the system application is ensured; injecting the application object of the plug-in into the rear end of the software operation service platform to finish the installation of the plug-in at the rear end; and then uploading the front-end resources in the plug-in package to a preset position in the back-end, and preparing data for loading the plug-in pages of the front-end.
Further, the step S204 may include: receiving a front-end page loading request through the front end; acquiring page loading response information returned by the rear end aiming at the front end page loading request; detecting whether a character string in a preset format exists in the page loading response information; when the character string with the preset format exists in the page loading response information, determining that the front-end page loading request comprises a plug-in page loading request aiming at the plug-in.
Specifically, after a user logs in the software operation service platform, the software operation service platform triggers a front-end page loading request, where the front-end page loading request is used for requesting to load a front-end page of the software operation service platform. In the application, a menu bar is arranged in a front-end page of the software operation service platform, the menu bar can be a side bar or an upper side bar, and the system application and the plug-in application can be positioned in the menu bar; the front page load request may also be a request to load a menu bar.
And the back end returns page loading response information according to the front end page loading request, wherein the page loading response information comprises relevant data of all applications in the menu bar. Because the system application and the plug-in application use different loading modes, the front end needs to identify which menu items are injected by the plug-in application.
In the application, a character string key with a preset format is set, and the key can be generated together when the back end generates an application object of the plug-in. When the plugin in the back end generates page loading response information, the character string key in the preset format is added into the page loading response information. If the character string key in the preset format exists in the page loading response information, determining that a plug-in page loading request aiming at the plug-in is included in the front-end page loading request. It will be appreciated that the front-end page load request may be a composite of a variety of requests, such as a request from a system application, or a plug-in page load request from a plug-in application.
If it is determined that the front-end page load request includes a plug-in page load request for a plug-in, logic for plug-in application loading needs to be executed.
In one embodiment, the format of the string key of the preset format is: plug in_application: instanceUUID: moduleiD, wherein plug in_application represents plug-in application, i.e. menu items are injected through plug-in application, instanceUUID is also the identification code of the plug-in, and it is the unique identification code generated by the running environment for the plug-in after the plug-in is enabled; the moduleID, the moduleUUID referred to above, is the identity of the module. In the same software running service platform, an instanceUUID and a moduleiD can uniquely identify one module, so that different plug-ins can be distinguished and applied.
In this embodiment, the front end receives the front end page loading request, acquires the page loading response information returned by the back end for the front end page loading request, and if a character string in a preset format exists in the page loading response information, determines that the front end page loading request includes a plug-in page loading request for a plug-in, and needs to execute logic of plug-in application loading in the front end.
Further, the step S205 may include: extracting main module information of a main module, a unique identification code of the plug-in and a main module identification code of the main module from a plug-in package of the plug-in, wherein the main module is a functional module in the plug-in, and the main module information is used for loading the plug-in; plug-in routing information is generated based on the unique identification code of the plug-in and the master module identification code of the master module.
Specifically, the string key in the preset format in the page loading response information may display a specific plug-in and a module therein, where the plug-in has a main module (typically, the module displayed in the key is the main module). The plug-in is associated with a slot identification moduleType, and the slot identification moduleType has a specific preset string (e.g. Ones: app: new mentioned above), so that the package of plug-ins is obtained through the slot represented by the preset string.
Extracting the main module information of the main module, the unique identification code pluginuid of the plug-in and the main module identification code moduleUUID of the main module from the plug-in package of the plug-in; the information of the main module is information related to the main module in the plug-in package configuration information, and is used for loading the plug-in at the front end. It will be appreciated that when the plug-in application is entered from the front end, the main page of the plug-in is entered first, the main page corresponding to the main module in the plug-in package, and thus the main module information and the main module identification code are acquired here.
Splicing the unique identification code of the plug-in unit and the main module identification code of the main module, and adding a preset prefix character string plugin to obtain plug-in unit routing information, wherein the format of the plug-in unit routing information can be as follows: plugin-pluginUUID-moduleuuuid.
In this embodiment, from a plug-in package of a plug-in, main module information of a main module, a unique identification code of the plug-in, and a main module identification code of the main module are extracted, where the main module information is used to load the plug-in; and generating plug-in routing information based on the unique identification code of the plug-in and the identification code of the main module, wherein the plug-in routing information can uniquely identify one module, so that the required front-end resource can be accurately acquired according to the plug-in routing information.
Further, the step S206 may include: accessing a preset storage position corresponding to the plug-in routing information to obtain front-end resources at the preset storage position; based on the front-end resource and the main module information, loading the plug-in page of the plug-in through the front-end, and completing plug-in loading, wherein the plug-in page obtained by loading is a page related to the main module information.
Specifically, a preset storage position corresponding to the plug-in routing information is accessed, and front-end resources at the preset storage position are obtained. Based on the front-end resource and the main module information, loading the plug-in page of the plug-in through the front-end, and completing plug-in loading; it will be appreciated that the master module information is involved in the loading, and that the resulting plug-in page is the page associated with the master module information, i.e., the main page of the plug-in application is loaded.
In one embodiment, the routing process is performed by a preset component (such as a plugin topbar component), and the component may also assemble and render the page of the plugin application according to the main module information and the front-end resource.
Each module in the plug-in package has a title configuration, and menu item titles are made with the title configuration value. The master module information needs to contain the title of the master module.
In this embodiment, a preset storage location corresponding to the plug-in routing information is accessed to obtain a front-end resource; based on the front-end resource and the main module information, loading the plug-in page of the plug-in, wherein the plug-in page is a page related to the main module information, and loading and starting of the plug-in at the front end are completed.
Further, the above plug-in processing method may further include: receiving menu bar modification information, wherein a plug-in is carried in the menu bar; calling a preset modification interface to modify the menu bar according to the menu bar modification information, wherein the modification comprises modification of the plug-in; the modifications made are saved to the database.
Specifically, the software running service platform provides modification and adjustment functions for the title of a menu item in a menu bar, the sequence adjustment of the menu item, whether the menu item is displayed or not, and the like. The user can modify the menu item according to the functions to generate menu bar modification information. Then, calling a modification interface (such as a side bar_setting/menu interface) provided by the software operation service platform, and injecting menu bar modification information into the interface so as to modify the menu bar; it will be appreciated that the modification may be to a plug-in application in the menu bar. Meanwhile, the modification interface is monitored, and when the menu bar is monitored to be modified through the modification interface, the modification is required to be persisted to the database; wherein modifications to the plug-in application need to be persisted to the plug-in related database.
In this embodiment, the modification information of the menu bar is received, and a preset modification interface is called to modify the menu bar according to the modification information of the menu bar, so as to modify the plug-in application in the menu bar, and save the modification to the database, so as to ensure the consistency of information and interaction.
In the application, the plug-in application has a level, and the installation ranges of the plug-in applications of different levels are different. For example, the levels include individuals, projects, organizations, and the scope is becoming increasingly large; when the level is a project, a certain plug-in application is required to be installed on the clients of all personnel in the project; when the level is organization, a certain plug-in application needs to be installed on the client side of all personnel in all items under the organization, so that consistency of interaction is ensured.
The plug-in has a lifecycle that when it is reached and the plug-in needs to be uninstalled, removal operations need to be performed on the previously injected data (including front-end and back-end). The application data synthesized at the time of the previous installation is cleared.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by computer readable instructions stored in a computer readable storage medium that, when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a random access Memory (Random Access Memory, RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.
With further reference to fig. 3, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a card processing apparatus, where an embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus is specifically applicable to various electronic devices.
As shown in fig. 3, the card processing apparatus 300 according to the present embodiment includes: a package obtaining module 301, a type checking module 302, a back-end installation module 303, a request receiving module 304, a route generating module 305 and a front-end loading module 306, wherein:
The package obtaining module 301 is configured to obtain a package.
And the type verification module 302 is configured to perform plug-in type verification on the plug-in package to obtain a verification result.
And the back-end installation module 303 is configured to install, based on the plug-in package, the plug-in when the verification result indicates that the plug-in implemented by the plug-in package is an independent application in the software operation service platform, and upload front-end resources in the plug-in package to a preset storage location.
The request receiving module 304 is configured to receive a plug-in page loading request for a plug-in.
The route generation module 305 is configured to generate plug-in routing information based on the plug-in page loading request.
The front loading module 306 is configured to obtain front resources from a preset storage location according to the package routing information, and load a package page of the package according to the front resources through the front end, so as to complete package loading.
In the embodiment, a plug-in package is obtained, and the plug-in package is installed to obtain a plug-in, wherein the plug-in is an independent and third-party application in a software operation service platform; based on the plug-in package, installing the plug-in at the rear end, and uploading front-end resources in the plug-in package to a preset storage position, wherein the front-end resources are used for loading the plug-in at the front end; receiving a plug-in page loading request aiming at a plug-in, wherein the plug-in page loading request records the plug-in page of which plug-in is to be loaded at the front end, so that plug-in routing information of the plug-in can be generated; the preset storage position for storing the front-end resource of the plugin can be accessed according to the plugin routing information, so that the front-end loads the plugin page of the plugin according to the acquired front-end resource, the plugin loading is completed, and the independent plugin serving as a third-party application is added into the software operation service platform.
In some alternative implementations of the present embodiment, the type verification module 302 may include: the method comprises the steps of configuring a reading sub-module, an identification extraction sub-module, an identification query sub-module and a result generation sub-module, wherein:
and the configuration reading sub-module is used for reading the configuration information in the plug-in package.
The identification extraction sub-module is used for extracting the check list identification of the plug-in from the configuration information.
The identification inquiring sub-module is used for acquiring a pre-configured plug-in check table and inquiring a slot identification corresponding to the check table identification in the plug-in check table.
And the result generation sub-module is used for checking the package of the plug-in module to pass when the slot mark is a preset character string, and generating a checking result indicating that the checking is passed so as to indicate that the plug-in module realized by the package of the plug-in module is an independent application in the software operation service platform.
In this embodiment, a verification table identifier of the plug-in is extracted from configuration information of the plug-in package, and a slot identifier corresponding to the verification table identifier is queried in the plug-in verification table; when the slot mark is a preset character string, the expansion of the plug-in is supported by the slot, and the package of the plug-in is checked to pass, so that invalid installation is avoided.
In some alternative implementations of the present embodiment, the back-end installation module 303 may include: an object generation sub-module, an object injection sub-module, and a resource uploading sub-module, wherein:
The object generation sub-module is used for generating an application object of the plug-in based on the plug-in package, and the application object has the same object structure as an application object of the system application in the software operation service platform.
And the object injection sub-module is used for injecting the application object of the plug-in into the rear end of the software operation service platform.
And the resource uploading sub-module is used for uploading the front-end resources in the plug-in package to a preset position in the back-end.
In the embodiment, an application object of the plug-in is generated based on the plug-in package, the object structure of the application object is consistent with the system application in the software operation service platform, and the consistency of the expression form of the plug-in and the system application is ensured; injecting the application object of the plug-in into the rear end of the software operation service platform to finish the installation of the plug-in at the rear end; and then uploading the front-end resources in the plug-in package to a preset position in the back-end, and preparing data for loading the plug-in pages of the front-end.
In some alternative implementations of the present embodiment, the request receiving module 304 may include: the system comprises a request receiving sub-module, a response obtaining sub-module, a character string detecting sub-module and a request determining sub-module, wherein:
and the request receiving sub-module is used for receiving the front-end page loading request through the front end.
The response acquisition sub-module is used for acquiring page loading response information returned by the rear end aiming at the front-end page loading request.
And the character string detection sub-module is used for detecting whether the character string with the preset format exists in the page loading response information.
The request determining submodule is used for determining that a front-end page loading request comprises a plug-in page loading request aiming at a plug-in when a character string in a preset format exists in the page loading response information.
In this embodiment, the front end receives the front end page loading request, acquires the page loading response information returned by the back end for the front end page loading request, and if a character string in a preset format exists in the page loading response information, determines that the front end page loading request includes a plug-in page loading request for a plug-in, and needs to execute logic of plug-in application loading in the front end.
In some alternative implementations of the present embodiment, the route generation module 305 may include: the method comprises the steps of extracting a sub-module and a route generation sub-module, wherein:
and the extraction submodule is used for extracting the main module information of the main module, the unique identification code of the plugin and the main module identification code of the main module from the plugin package of the plugin, wherein the main module is a functional module in the plugin, and the main module information is used for loading the plugin.
And the route generation sub-module is used for generating the plug-in route information based on the unique identification code of the plug-in and the identification code of the main module.
In this embodiment, from a plug-in package of a plug-in, main module information of a main module, a unique identification code of the plug-in, and a main module identification code of the main module are extracted, where the main module information is used to load the plug-in; and generating plug-in routing information based on the unique identification code of the plug-in and the identification code of the main module, wherein the plug-in routing information can uniquely identify one module, so that the required front-end resource can be accurately acquired according to the plug-in routing information.
In some alternative implementations of the present embodiment, the front-end loading module 306 may include: the system comprises a resource acquisition sub-module and a page loading sub-module, wherein:
the resource acquisition sub-module is used for accessing a preset storage position corresponding to the plug-in routing information to acquire front-end resources at the preset storage position.
And the page loading sub-module is used for loading plug-in pages of the plug-ins through the front end based on the front end resources and the main module information and completing the plug-in loading, wherein the plug-in pages obtained by loading are pages related to the main module information.
In this embodiment, a preset storage location corresponding to the plug-in routing information is accessed to obtain a front-end resource; based on the front-end resource and the main module information, loading the plug-in page of the plug-in, wherein the plug-in page is a page related to the main module information, and loading and starting of the plug-in at the front end are completed.
In some alternative implementations of the present embodiment, the card processing apparatus 300 may include: modification receiving module, modification module and save module, wherein:
the modification receiving module is used for receiving the menu bar modification information, and the menu bar is loaded with the plug-in unit.
The modification module is used for calling a preset modification interface to modify the menu bar according to the menu bar modification information, wherein the modification comprises modification of the plug-in.
And the storage module is used for storing the modifications to the database.
In this embodiment, the modification information of the menu bar is received, and a preset modification interface is called to modify the menu bar according to the modification information of the menu bar, so as to modify the plug-in application in the menu bar, and save the modification to the database, so as to ensure the consistency of information and interaction.
In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 4, fig. 4 is a basic structural block diagram of a computer device according to the present embodiment.
The computer device 4 comprises a memory 41, a processor 42, a network interface 43 communicatively connected to each other via a system bus. It should be noted that only computer device 4 having components 41-43 is shown in the figures, but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead. It will be appreciated by those skilled in the art that the computer device herein is a device capable of automatically performing numerical calculations and/or information processing in accordance with predetermined or stored instructions, the hardware of which includes, but is not limited to, microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASICs), programmable gate arrays (fields-Programmable Gate Array, FPGAs), digital processors (Digital Signal Processor, DSPs), embedded devices, etc.
The computer equipment can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing equipment. The computer equipment can perform man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.
The memory 41 includes at least one type of readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the storage 41 may be an internal storage unit of the computer device 4, such as a hard disk or a memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the computer device 4. Of course, the memory 41 may also comprise both an internal memory unit of the computer device 4 and an external memory device. In this embodiment, the memory 41 is typically used to store an operating system and various application software installed on the computer device 4, such as computer readable instructions of a plug-in processing method, and the like. Further, the memory 41 may be used to temporarily store various types of data that have been output or are to be output.
The processor 42 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is configured to execute computer readable instructions stored in the memory 41 or process data, such as computer readable instructions for executing the plug-in processing method.
The network interface 43 may comprise a wireless network interface or a wired network interface, which network interface 43 is typically used for establishing a communication connection between the computer device 4 and other electronic devices.
The computer device provided in this embodiment may perform the above-described plug-in processing method. The plug-in processing method may be the plug-in processing method of each of the above embodiments.
In the embodiment, a plug-in package is obtained, and the plug-in package is installed to obtain a plug-in, wherein the plug-in is an independent and third-party application in a software operation service platform; based on the plug-in package, installing the plug-in at the rear end, and uploading front-end resources in the plug-in package to a preset storage position, wherein the front-end resources are used for loading the plug-in at the front end; receiving a plug-in page loading request aiming at a plug-in, wherein the plug-in page loading request records the plug-in page of which plug-in is to be loaded at the front end, so that plug-in routing information of the plug-in can be generated; the preset storage position for storing the front-end resource of the plugin can be accessed according to the plugin routing information, so that the front-end loads the plugin page of the plugin according to the acquired front-end resource, the plugin loading is completed, and the independent plugin serving as a third-party application is added into the software operation service platform.
The present application also provides another embodiment, namely, a computer-readable storage medium storing computer-readable instructions executable by at least one processor to cause the at least one processor to perform the steps of the plug-in processing method as described above. The computer readable storage medium may be either a nonvolatile storage medium or a volatile storage medium.
In the embodiment, a plug-in package is obtained, and the plug-in package is installed to obtain a plug-in, wherein the plug-in is an independent and third-party application in a software operation service platform; based on the plug-in package, installing the plug-in at the rear end, and uploading front-end resources in the plug-in package to a preset storage position, wherein the front-end resources are used for loading the plug-in at the front end; receiving a plug-in page loading request aiming at a plug-in, wherein the plug-in page loading request records the plug-in page of which plug-in is to be loaded at the front end, so that plug-in routing information of the plug-in can be generated; the preset storage position for storing the front-end resource of the plugin can be accessed according to the plugin routing information, so that the front-end loads the plugin page of the plugin according to the acquired front-end resource, the plugin loading is completed, and the independent plugin serving as a third-party application is added into the software operation service platform.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
It is apparent that the embodiments described above are only some embodiments of the present application, but not all embodiments, the preferred embodiments of the present application are given in the drawings, but not limiting the patent scope of the present application. This application may be embodied in many different forms, but rather, embodiments are provided in order to provide a more thorough understanding of the present disclosure. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described in the foregoing, or equivalents may be substituted for elements thereof. All equivalent structures made by the specification and the drawings of the application are directly or indirectly applied to other related technical fields, and are also within the protection scope of the application.

Claims (10)

1. A method of processing a card, comprising the steps of:
obtaining a plug-in package;
checking the plug-in type of the plug-in package to obtain a checking result;
when the verification result shows that the plug-in realized by the plug-in package is an independent application in a software operation service platform, installing the plug-in at the rear end based on the plug-in package, and uploading front-end resources in the plug-in package to a preset storage position;
receiving a plug-in page loading request aiming at the plug-in;
generating plug-in routing information based on the plug-in page loading request;
and acquiring the front-end resource from the preset storage position according to the plug-in routing information, and loading the plug-in page of the plug-in through the front-end according to the front-end resource to finish plug-in loading.
2. The card processing method according to claim 1, wherein the step of performing card type verification on the card package to obtain a verification result includes:
reading configuration information in the plug-in package;
extracting the verification table identification of the plug-in from the configuration information;
obtaining a pre-configured plug-in verification table, and inquiring a slot identifier corresponding to the verification table identifier in the plug-in verification table;
And when the slot mark is a preset character string, checking the plug-in package to pass, and generating a checking result indicating that the checking is passed so as to indicate that the plug-in realized by the plug-in package is an independent application in the software operation service platform.
3. The card processing method according to claim 1, wherein the step of installing the card at a back end based on the card package and uploading front-end resources in the card package to a preset storage location includes:
generating an application object of the plug-in based on the plug-in package, wherein the application object and an application object of a system application in a software operation service platform have the same object structure;
injecting the application object of the plug-in into the rear end of the software operation service platform;
and uploading the front-end resources in the plug-in package to a preset position in the back-end.
4. The plug-in processing method according to claim 1, wherein the step of receiving a plug-in page load request for the plug-in includes:
receiving a front-end page loading request through the front end;
acquiring page loading response information returned by the rear end aiming at the front end page loading request;
Detecting whether a character string in a preset format exists in the page loading response information;
when the character string with the preset format exists in the page loading response information, determining that the front-end page loading request comprises a plug-in page loading request aiming at the plug-in.
5. The plug-in processing method of claim 4, wherein the step of generating plug-in routing information based on the plug-in page load request comprises:
extracting main module information of a main module, a unique identification code of the plug-in and a main module identification code of the main module from a plug-in package of the plug-in, wherein the main module is a functional module in the plug-in, and the main module information is used for loading the plug-in;
plug-in routing information is generated based on the unique identification code of the plug-in and the master module identification code of the master module.
6. The method for processing a plug-in according to claim 5, wherein the step of obtaining the front-end resource from the preset storage location according to the plug-in routing information, and loading the plug-in page of the plug-in according to the front-end resource through the front-end, and completing plug-in loading comprises:
Accessing a preset storage position corresponding to the plug-in routing information to obtain front-end resources at the preset storage position;
and loading the plug-in page of the plug-in through the front end based on the front end resource and the main module information, and completing plug-in loading, wherein the plug-in page obtained by loading is a page related to the main module information.
7. The card processing method according to claim 1, characterized in that the method further comprises:
receiving menu bar modification information, wherein the plug-in is carried in the menu bar;
calling a preset modification interface to modify the menu bar according to the menu bar modification information, wherein the modification comprises modification of the plug-in;
the modifications made are saved to the database.
8. A card processing apparatus, comprising:
the plug-in package acquisition module is used for acquiring plug-in packages;
the type verification module is used for verifying the plug-in type of the plug-in package to obtain a verification result;
the back-end installation module is used for installing the plug-in on the back-end based on the plug-in package and uploading front-end resources in the plug-in package to a preset storage position when the verification result shows that the plug-in realized by the plug-in package is an independent application in a software operation service platform;
The request receiving module is used for receiving a plug-in page loading request aiming at the plug-in;
the route generation module is used for generating plug-in route information based on the plug-in page loading request;
the front-end loading module is used for acquiring the front-end resources from the preset storage position according to the plug-in routing information, and loading plug-in pages of the plug-ins according to the front-end resources through the front end to finish plug-in loading.
9. A computer device comprising a memory having stored therein computer readable instructions which when executed by a processor implement the steps of the plug-in processing method of any of claims 1 to 7.
10. A computer readable storage medium having stored thereon computer readable instructions which when executed by a processor implement the steps of the plug-in processing method according to any of claims 1 to 7.
CN202310404125.XA 2023-04-07 2023-04-07 Plug-in processing method, device, computer equipment and storage medium Pending CN116382720A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310404125.XA CN116382720A (en) 2023-04-07 2023-04-07 Plug-in processing method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310404125.XA CN116382720A (en) 2023-04-07 2023-04-07 Plug-in processing method, device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116382720A true CN116382720A (en) 2023-07-04

Family

ID=86965489

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310404125.XA Pending CN116382720A (en) 2023-04-07 2023-04-07 Plug-in processing method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116382720A (en)

Similar Documents

Publication Publication Date Title
CN104049986B (en) plug-in loading method and device
CN110162408B (en) Data processing method, device, equipment and machine-readable medium
CN111695156A (en) Service platform access method, device, equipment and storage medium
CN107528718B (en) Method, device and system for acquiring resources
CN108418797B (en) Webpage access method and device, computer equipment and storage medium
CN112631924A (en) Automatic testing method and device, computer equipment and storage medium
CN113536185A (en) Application page loading method, storage medium and related equipment thereof
CN112835808A (en) Interface testing method and device, computer equipment and storage medium
CN116304403A (en) Webpage access method and device, computer equipment and storage medium
CN113282591A (en) Authority filtering method and device, computer equipment and storage medium
CN111488286B (en) Method and device for independently developing Android modules
CN112363814A (en) Task scheduling method and device, computer equipment and storage medium
CN111475468A (en) Log access method, device, equipment and storage medium of newly added system
CN116382720A (en) Plug-in processing method, device, computer equipment and storage medium
CN112416875B (en) Log management method, device, computer equipment and storage medium
US9189633B2 (en) Download management method and device based on android browser
CN116136760B (en) Method, device, equipment and storage medium for replacing native selector of browser
CN117667668A (en) Application analysis method, device, equipment and storage medium based on application upgrading
CN113806372B (en) New data information construction method, device, computer equipment and storage medium
CN116467145A (en) Page performance data acquisition method and device, computer equipment and storage medium
CN115756630A (en) Plug-in processing method and device, computer equipment and storage medium
CN117435267A (en) Form loading method and device based on configuration file, computer equipment and medium
CN117009201A (en) Application cold start test method, device, equipment, medium and program product
CN116541417A (en) Batch data processing method, device, computer equipment and storage medium
CN116382719A (en) Plug-in processing method, device, computer equipment and storage medium

Legal Events

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