CN112416345A - Universal client software integration system - Google Patents
Universal client software integration system Download PDFInfo
- Publication number
- CN112416345A CN112416345A CN202011276055.7A CN202011276055A CN112416345A CN 112416345 A CN112416345 A CN 112416345A CN 202011276055 A CN202011276055 A CN 202011276055A CN 112416345 A CN112416345 A CN 112416345A
- Authority
- CN
- China
- Prior art keywords
- plug
- interface
- ins
- style
- user
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Abstract
The invention provides a universal client software integration system, which is a client software integration system based on OSGI standards, adopts bundle mechanism for integration and can integrate various plug-ins such as Web pages, executable programs, dynamic libraries and the like; providing a plurality of common functions such as single sign-on and user sign-on management, interface display style management and style one-key switching, signal lamps and the like; the two-dimensional earth, the time system, various business applications and the like can be integrated in a plug-in mode, and a user can compile and integrate the client application according to the use requirement to form a customized client application system. The invention adopts cross-platform language development, can be compiled across different operating system platforms, realizes one-time compiling and anywhere running, can run on various operating systems such as Windows, the winning symbol kylin, the silver river kylin and the like, and has better expansibility and compatibility.
Description
Technical Field
The invention belongs to the field of information systems, and particularly relates to a universal client software integration system.
Background
At present, most information system client software integrated systems are mainly integrated in a Web page mode, and the mode also limits that integrated functional application plug-in developers can only adopt Web language development and cannot integrate and use the functions developed by the existing non-Web language; part of the information system client software integrated system developed by C + + can integrate various types of plug-ins such as Web pages, executable programs, dynamic libraries and the like, but has defects in the aspects of display effect, interface display style, information prompt and the like, and has some defects in mechanism and function.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to provide a client software integration system which is developed by using QT language as a main part and JAVA language as an auxiliary part, can integrate various plug-ins and provides a plurality of common functions of user login management, interface style management, one-key switching, signal lamps and the like; the user can flexibly compile the client application according to the use requirement to form a customized client application system. The method is suitable for developing information system clients with multiple language types and mixed C/S and B/S frameworks, in particular to a command information system client.
The invention particularly provides a universal client software integration system which comprises a basic functional layer, a framework extension functional layer and an application support functional layer;
the basic function layer is used for providing integration of various plugins based on Poco modules for the universal client software integration system, and comprises integration and related functions of executable program plugins, dynamic library plugins and Web page plugins; meanwhile, the system has the functions of full life cycle management, process keep-alive and the like of executable program plug-ins and dynamic library plug-ins;
the framework extension functional layer is used for providing extension of functions for the universal client software integrated system, wherein the functions comprise plug-in message management, plug-in state monitoring, display layout customization, shortcut button and menu arrangement, display resolution adaptation, interface style management, one-key switching and the like, and providing a network transmission interface and a data access interface to support secondary development;
the application support function layer is used for providing support capacity for application plug-ins and application systems, including signal lamps and user login management, and can be expanded according to application requirements.
The executable program plug-in, the dynamic library plug-in and the Web page plug-in are used for packaging various types of plug-ins of a client based on a Poco component, and plug-in integration is carried out by adopting a bundle mechanism based on an OSGI standard, so that the plug-ins are provided for exiting from the full life cycle management from the starting, running and updating to the closing, the process keep-alive function is provided, and the message interaction management among the similar plug-ins and the different plug-ins is provided;
the message interaction between the dynamic library plug-ins is realized based on an in-process broadcasting mechanism;
and the information interaction among the plug-ins of other types is realized by an information transmission mode based on a TCP protocol.
The dynamic library plug-in integration and related functions comprise dynamic library plug-in integration, dynamic library plug-in full life cycle management, dynamic library plug-in message management and dynamic library plug-in state monitoring;
the Web page plug-in integration and related functions comprise Web page plug-in integration, browser control, Web page plug-in message management and Web page plug-in state monitoring.
The user login management of the application support function layer comprises the functions of single-user login, single-point login, heartbeat detection and login state management;
the single-user login means that: the same user can only log in on the universal client software integrated system on one client at the same time, when the same user name is used for logging in again on the universal client software integrated system on the other client, the logged prompt information is given, if the user selects to continue logging in, the user of the previous client is forced to be offline, the universal client software integrated system is closed to log out, and the logging operation of the user of the client is continued; if the user selects to cancel the login, returning to a login interface;
the single sign-on is as follows: when a user uses the universal client software integration system to log in and authenticate identity for the first time at a client, after a user name and a password pass verification at a server, the server returns user information and an identity authentication token to the universal client software integration system at the client, and the universal client software integration system caches the token locally; if the plug-in started by the universal client software integration system is an executable program or a dynamic library plug-in, the universal client software integration system transmits information such as a user name, a password and the like to the executable program or the dynamic library plug-in according to an agreed format; if the Web page plug-in is started, the Web page plug-in acquires a user name, a password and an identity token from the universal client software integration system through an interface, submits the identity token to a server for verification, and starts the plug-in after the verification is successful; secondary identity authentication is not needed in the use process of each subsequent plug-in, so that the single sign-on capability is realized;
the heartbeat detection means: after the user logs in successfully, a heartbeat detection mechanism is established between the server and the client universal client software integration system, the server sends heartbeat messages to the client universal client software integration system at regular time, and if the client universal client software integration system returns the heartbeat messages, the client universal client software integration system operates normally; if the server side does not acquire the heartbeat message of the client-side general client software integration system for three times continuously, the client-side general client software integration system is considered to be abnormally quitted, and the login state of the user at the client side is updated;
the login state management means: and functions of managing and inquiring login user names, login roles, login IP addresses, login time and the like are provided through a visual interface.
The framework extension function layer also provides the following functions:
executable program plug-in message management: supporting message interaction among executable program plug-ins, between the executable program plug-ins and the dynamic library plug-ins, and between the executable program plug-ins and the Web page plug-ins, and managing messages;
dynamic library plug-in message management: supporting message interaction among dynamic library plug-ins, between the dynamic library plug-ins and executable program plug-ins, and between the dynamic library plug-ins and Web page plug-ins, and managing messages;
web page plug-in message management: supporting message interaction between Web page plug-ins, between the Web page plug-ins and dynamic library plug-ins, between the Web page plug-ins and executable program plug-ins, and possibly managing messages;
customizing a display layout: supporting layout customization of frequently displayed interfaces such as a system main interface menu, a shortcut button bar, a signal lamp and the like;
monitoring the plug-in state: supporting the state monitoring of the executable program and the dynamic library type plug-in;
shortcut button and menu arrangement: the shortcut button and the menu on the frame main interface are arranged according to roles, and the shortcut button and the menu can be associated with various integrated plug-ins;
display resolution adaptation: the system main interface is provided with the capability of automatically adapting to various resolutions of the display, and particularly three common resolution adaptation capabilities of 1920 × 1080, 1280 × 1024 and 1024 × 768 are provided;
interface style management and one-key switching;
a network transmission interface: providing a unified interface for information interaction between the support system and the integrated plug-in;
a data access interface: and a unified interface for supporting the system and the integrated plug-in to access the database is provided.
The framework extension functional layer provides interface style management and one-key switching, and the interface style management and the one-key switching are composed of interface resource file reading, main interface bottom plate construction, unified interface display style display and interface display style switching, and the framework extension functional layer comprises the following steps:
reading an interface resource file: reading a pre-designed interface style sheet file, a main interface icon and a font file to form an interface display style scheme;
constructing a main interface bottom plate: reading interface display style scheme information and constructing a main interface bottom plate control;
displaying the unified interface display style: performing display control on the main interface and the related functional components;
interface display style switching: all the displayed plug-in interfaces can be switched into a specified display style according to requirements under the condition of not restarting the running plug-in and the universal client software integrated system, and the plug-in interfaces of the QT development and the plug-in of the JAVA development can be switched into the specified display style.
The application support function layer provides a signal lamp function, the signal lamp function is composed of signal lamp compiling, signal lamp client plug-in components and signal lamp secondary development kits, wherein the client plug-in components comprise signal lamp display plug-in components and signal lamp message plug-in components:
signal lamp assembly: maintaining the mapping relation between the application plug-in and the signal lamp; after the system is deployed, compiling the mapping relation between the application plug-in and the signal lamp according to the use requirement;
signal lamp client plug-in components: when the signal lamp client plug-in is started, reading a corresponding compiling result from the compiling table according to user or role information, displaying signal lamps in sequence by combining a function menu in the client application compiling information, receiving the signal in real time to light the signal lamp, and starting or activating the corresponding plug-in after the user clicks the signal lamp;
secondary signal lamp development kit: providing a secondary development interface of two development languages of C + +, JAVA for an application software developer needing integration to develop; when the integrated application plug-in runs, the signals needing to be notified are transmitted to a secondary development kit according to a specified format, the secondary development kit searches the current online role or user and sends the signals to one or more signal lamp client plug-ins where the role or user is located.
The signal lamp compiling function of the application support functional layer provides a man-machine interaction interface, and the mapping relation between the signal lamp and the application software is recorded;
reading the compiling result when the signal lamp client plug-in is started, identifying a function menu with signal lamps from a preset configuration file, and displaying the function menu in sequence; if the compiled signal lamp is not in the configuration file, the signal lamp does not display;
the application plug-in calls an interface of the signal lamp secondary development kit or sends a signal corresponding to the application to the secondary development kit;
the signal lamp secondary development kit acquires IP address information of a current login user corresponding to a receiving role according to the user role and the user login state;
the signal lamp secondary development kit sends a signal corresponding to the application plug-in to a signal lamp client plug-in of a specified client according to the IP address;
the signal lamp client plug-in receives the signal, changes the state of the signal lamp and gives out prompt information;
and clicking a signal lamp, starting a corresponding plug-in by the general client software integration system through a starting script configured by the signal lamp, opening a corresponding webpage if the plug-in is a Web page plug-in, and starting a corresponding executable program or a dynamic library if the plug-in is an executable program or a dynamic library plug-in.
The basic functional layer also provides the following functions:
(1) executable program plug-in integration: the system is responsible for the management, integration and scheduling of the executable program plug-in based on the process;
(2) and (3) executable program plug-in full life cycle management: the method has the full life cycle management capability of the executable program plug-in, including starting, stopping and uninstalling;
(3) executable program plug-in attribute management: providing the display and editing functions of the attributes of the executable program plug-ins, managing the starting parameters of the executable program plug-ins, displaying the control parameters and configuring the parameter attributes of the system required by the executable program plug-ins;
(4) dynamic library plug-in integration: the dynamic library plug-in is responsible for providing the management, integration and scheduling functions of the dynamic library plug-in;
(5) dynamic library plug-ins into lifecycle management: the method has the full life cycle management capability of the dynamic library plug-in, including loading, analyzing, starting, updating, stopping and unloading;
(6) process keep-alive: for the process needing to keep the running state, the state of the process is mastered in real time, and if the process is found to be absent, the processes can be restarted, wherein the two modes comprise a process starting mode for starting the process and recovering the initial state, and a process starting mode for recovering the last state;
(7) web page integration and browser control: the method is used for integrating the Web pages into the frame, controlling the browser of the operating system to open the specified Web page and controlling the size and display of the browser on the specified display.
The system executes the following steps to complete the switching process of the display styles of the interfaces of the executable file and the dynamic library plug-in:
a1, preparing interface display style resource files, designing more than two sets of interface display style schemes in advance, manufacturing a plurality of sets of interface resource files according to the common resolution of the system and each set of style schemes, and compiling QSS files according to the design;
a2, loading interface display style, loading interface resource files and QSS files by the universal client software integration system, generating an interface display style scheme, automatically identifying the resolution of a display, and selecting the interface display style scheme corresponding to the resolution;
step a3, in the interface display style display stage, the universal client software integration system generates a uniform system display interface according to the selected interface display style scheme, and displays the uniform system display interface after the system is started; when a user needs to switch the system style by one key, calling a c + + style switching interface of the universal client software integration system, sending a style switching message, after receiving the style switching message, the universal client software integration system selects an interface display style scheme corresponding to the current resolution according to the interface display style scheme name selected by the user, completing the generation and display of a new style interface, meanwhile, the universal client software integration system forwards the style switching message to various integrated plug-ins, and after the plug-ins receive the message, the plug-ins complete the style switching of respective display interfaces.
The system executes the following steps to complete the switching process of the display style of the Web page plug-in interface:
b1, designing more than two interface display style schemes in advance in the interface display style design stage, manufacturing a plurality of sets of interface resource files according to the common resolution of the system and each set of style scheme, and then compiling CSS files according to the design;
b2, loading interface display style resource files by the Web service framework, generating a Web interface display style scheme, automatically identifying the resolution of the display, and selecting the interface display style scheme corresponding to the resolution;
step b3, in the Web page display stage, the Web service frame generates a Web page according to the interface display style scheme and displays the Web page in the browser; when a user needs to switch the system style by one key, the Web page plug-in receives style switching information from the universal client software integration system and calls a style switching interface; and the Web service framework selects an interface display style scheme to be switched according to the parameters, then completes Web page generation and display in the browser, and completes Web page display style switching.
The universal client software integration system is a client software integration method adopting QT and JAVA mixed programming. The method provides a plug-in integration system based on OSGI standard, adopts bundle mechanism for integration, and can integrate various types of plug-ins such as executable program, dynamic library, Web page and the like; and a plurality of shared functions are provided, and a better human-computer interaction effect is realized.
Has the advantages that: 1) the integration of various plug-ins is supported, the plug-ins comprise plug-ins such as an executable program, a dynamic library, a Web page and the like, and the display of the integrated dynamic effect of the interface is realized;
2) single-user login and single-point login are realized, the repeated login of the same user on a plurality of clients at the same time is avoided, and secondary identity authentication is avoided within a certain time limit;
3) the interface display style is switched by one key, and the style switching of all display interfaces of the whole system is quickly realized by adopting a unified mechanism, wherein the style switching comprises the display interface of a universal client software integration system and the display interface of an integrated QT and JAVA developed application plug-in;
4) and providing a plug-in information prompt function to remind a user to check information and process application in time.
Drawings
The foregoing and/or other advantages of the invention will become further apparent from the following detailed description of the invention when taken in conjunction with the accompanying drawings.
FIG. 1 is an overall architecture diagram of the present invention.
Fig. 2 is a schematic diagram of the login management function.
Fig. 3 is a schematic diagram of a single user login implementation.
Fig. 4 is a schematic diagram of a single sign-on implementation.
Fig. 5 is a schematic diagram of the login heartbeat detection principle.
FIG. 6 is a schematic diagram of interface style management and one-touch switch function.
FIG. 7 is a schematic diagram illustrating a C + + development interface display style one-key switch using process.
Fig. 8 is a schematic diagram of the interface display style one-key switching use flow of JAVA development.
Fig. 9 is a schematic diagram of the functional components of the signal lamp.
Fig. 10 is a schematic diagram of the operation of the signal lamp.
Fig. 11 is a schematic diagram of a signal lamp using process.
Detailed Description
The invention provides a universal client software integration system, which adopts QT language and is assisted by JAVA language to develop a universal client software integration framework and support the integration of three types of plug-ins including an executable program, a dynamic library and a Web page, wherein the interface display style, the interface layout and the positions of all elements can be customized as required, and the integrated plug-ins can be flexibly compiled;
the user login management is realized, the user login information is stored through the system, and the user login information is pushed to the plug-in unit in time when the plug-in unit is started within a certain time limit, so that the secondary identity authentication of the user is avoided; meanwhile, the logging-in and logging-out actions of the user are recorded, the repeated logging-in of the user is detected, prompted or forcibly logged-out, and the user can only log in one client at the same time; in addition, a heartbeat mechanism is adopted to detect the online condition of the user, so that the condition that the login information is inconsistent with the actual login condition when the user abnormally logs out is avoided;
the method comprises the steps of realizing interface style management and one-key switching, wherein a universal client software integration system provides style switching buttons, switching styles according to style information selected by a user based on a preset QSS file and a CSS file, and realizing switching of a started plug-in to a specified style in an interface or message mode, so that the interface display styles of all the plug-ins in the whole system are uniform;
the signal lamp function is realized, a unified message receiving and reminding mechanism is provided for the integrated plug-ins, and corresponding prompts of the plug-ins can be displayed on the universal client software integrated system when the client plug-ins are not started or the plug-ins are in an inactive state, so that a user is reminded to open or activate the plug-ins to check messages and perform corresponding operations.
The general architecture of the invention is shown in figure 1, and by relying on QT, Poco and JAVA functional modules, the functional modules such as a basic functional layer, a framework extension functional layer, an application support functional layer and the like are realized, secondary development of various client side plug-ins is supported based on corresponding interfaces, application functions such as signal lamps, user login management and the like are provided, and the system can be directly used by users.
The QT layer includes QT main function modules that the present invention needs to use, including QtCore (QT base module including signal and slot communication, input and output, events, object processing, multithreading, etc.), QtGui (graphical user interface module), QStyle (interface display style module), QtNetwork (cross-platform network module).
Poco is a series of C + + class libraries using the highly efficient, modern standard ANSI/ISO C + +. Based on STL, Poco is modular and extensible, and has high portability, supporting applications that create cross-platforms. Poco is mainly applied to create automation middleware and devices, wrapper applications, and other scenarios.
Foundation and Util modules in Poco are mainly used for integrating various plug-ins by the software. Foundation modules are the Foundation of Poco, the primary function being the underlying encapsulation of the integrated plug-ins. The Util module mainly functions to support command line parameter processing (checking, binding to configuration properties) of the integrated plug-in and manage configuration files (supporting different configuration file formats including an INI file, an XML file, a JAVA class property file, and a Windows registry).
JAVA is a representative object-oriented language and is mainly used for Web page server development in the invention. The JAVA base classes used in the present invention mainly include net (for executing classes related to network, such as URL, Socket, ServerSocket, etc.), io (class providing various input/output functions), util (including some utility classes, such as defining system characteristics, using methods related to date calendar, etc.).
The basic functional layer provides integration of various plugins based on Poco modules for the universal client software integration system, and comprises integration of executable program plugins, dynamic library plugins and Web page plugins; meanwhile, the method has the functions of full life cycle management, process keep-alive and the like of the executable program plug-in and the dynamic library plug-in. The detailed functions are described below.
(1) Executable program plug-in integration: the system is responsible for the management, integration and scheduling of the executable program plug-in based on the process;
(2) and (3) executable program plug-in full life cycle management: the system has the full life cycle management capability of executable program plug-ins, including starting, stopping, uninstalling and the like;
(3) executable program plug-in attribute management: providing the display and editing functions of the attributes of the executable program plug-in, managing the starting parameters of the executable program plug-in, displaying the control parameters, the system configuration parameters required by the executable program plug-in and other attributes;
(4) dynamic library plug-in integration: the dynamic library plug-in is responsible for providing the management, integration and scheduling functions of the dynamic library plug-in;
(5) dynamic library plug-ins into lifecycle management: the method has the full life cycle management capability of the dynamic library plug-in, including loading, analyzing, starting, updating, stopping, unloading and the like;
(6) process keep-alive: for the process needing to keep the running state, the state of the process is mastered in real time, and if the process is found to be absent, the processes can be restarted, wherein the two modes comprise a process starting mode for starting the process and recovering the initial state, and a process starting mode for recovering the last state;
(7) web page integration and browser control: the method is used for integrating the Web pages into the frame, can control the browser of the operating system to open the specified Web page, and can control the size and display of the browser on the specified display.
The frame extension functional layer is used for providing function extension for the universal client software integrated system, and comprises functions of plug-in message management, plug-in state monitoring, display layout customization, shortcut button and menu arrangement, display resolution adaptation, interface style management, one-key switching and the like, and provides a network transmission interface and a data access interface to support secondary development. The detailed functions are described as follows:
executable program plug-in message management: supporting message interaction among executable program plug-ins, between the executable program plug-ins and the dynamic library plug-ins, and between the executable program plug-ins and the Web page plug-ins, and managing messages;
dynamic library plug-in message management: supporting message interaction among the dynamic library plug-ins, between the dynamic library plug-ins and the executable program plug-ins, and between the dynamic library plug-ins and the Web page plug-ins, and managing messages;
web page plug-in message management: supporting message interaction among Web page plug-ins, between the Web page plug-ins and dynamic library plug-ins, between the Web page plug-ins and executable program plug-ins, and managing messages;
customizing a display layout: supporting layout customization of frequently displayed interfaces such as a system main interface menu, a shortcut button bar, a signal lamp and the like;
monitoring the plug-in state: supporting the state monitoring of plug-ins of types such as executable programs, dynamic libraries and the like;
shortcut button and menu arrangement: the shortcut button and the menu on the frame main interface are arranged according to roles, and the shortcut button and the menu can be associated with various integrated plug-ins;
display resolution adaptation: the system main interface is provided with the capability of automatically adapting to various resolutions of a display, and three common resolution adaptation capabilities of 1920 × 1080, 1280 × 1024 and 1024 × 768 are provided at present;
interface style management and one-key switching: this function is described in detail later;
a network transmission interface: providing a unified interface for information interaction between the support system and the integrated plug-in;
a data access interface: providing a unified interface for the support system and the integrated plug-in to access the database;
the application support function layer provides support capability for application plug-ins and application systems, comprises signal lamps and user login management, and can be expanded subsequently according to application requirements. This layer of functionality is described in detail later.
1. Plug-in integration method
The system supports three types of plug-in integration, which is described in detail below.
a) Executable program plug-in integration method
When the user clicks the executable program menu on the universal client software integrated system, the system executes the "/startup. Sh represents a starting script, user represents a user name, and password represents a password.
Sh file format of start script is as follows:
export EXEDIR ═/home/ExeDir/> setting environment variable of system execution path-
export LD _ LIBRARY _ PATH ═/usr/lib/_ sets context variables × _ based on dynamic libraries
CD EXEDIR/Path into executable program or script
Sh,/xxx, or xx/activation software
An export EXEDIR represents an environment variable for setting a system execution path;
the export LD _ LIBRARY _ PATH/usr/lib represents setting the environment variable depending on the dynamic LIBRARY;
cd EXEDIR represents a path into an executable program or script;
sh or xx denotes start-up software ".
b) Dynamic library plug-in integration method
The dynamic library plug-in inherits a Bundle activator class of a Bundle module in the OSGI, realizes corresponding public void start (Bundle context) and public void stop (Bundle context) methods, determines a unique starting command character string of the plug-in (for example, a starting command of the comprehensive information query plug-in is 'InfoSearchPlugin'), and generates the dynamic library plug-in under a specified path by using a Bundle generation tool.
When a user clicks a dynamic library plug-in menu on the universal client software integration system, the plug-in menu generates a starting command character string, and the system responds and starts the dynamic library plug-in (for example, for the comprehensive information query plug-in, the menu directly sends the starting command character string of 'InfSearchPlugin' to the framework, and the framework starts the comprehensive information query plug-in).
c) Web page plug-in integration method
When a user clicks a Web page plug-in menu on the universal client software integrated system, the system opens a browser, transmits an access address, starts a Web page, and has an access address format: protocol:// ip: port/path, wherein protocol represents protocol, ip represents ip address, port represents port number, path represents relative path, and the page acquires identity information through the interface until login service verification.
Such as: and (3) accessing http:// 1.1.1:8080/zzxx/tj by opening a browser, opening a comprehensive information statistics page, and acquiring identity information from the universal client software integrated system through an external interface by the page to finish identity authentication.
2. User login management
The user login management comprises functions of single-user login, single-point login, heartbeat detection, login state management and the like, the software comprises two parts of a server function and a client function, and the server function comprises single-user login service, single-point login service, heartbeat detection service, login state management service and the like; the client functions comprise a login client and a heartbeat detection client, and the function components are shown in fig. 2.
Single user login: the same user can only log in at one client at the same time, when the same user name is used for logging in at another client again, the logged prompt information is given, if the user selects to continue logging in, the previous client user is forced to be offline, and the logging operation of the client is continued; and if the user selects to cancel the login, returning to a login interface.
Single sign-on: after the user login and the identity authentication are carried out by using the universal client software integration system, the plug-in is started and can be started and used without carrying out secondary identity authentication on the user;
heartbeat detection: establishing a heartbeat detection mechanism between a heartbeat monitoring client in a general client software integrated system and heartbeat monitoring service of a server to detect abnormal exit of the client;
and (3) login state management: and management and query of information such as login user name, login role, login IP address, login time and the like are provided through a visual interface.
a) Single user login
When logging in for the first time, the user can log in after the user passes the user name and password verification; when logging in again, after the user name and the password are verified, the login service inquires the current user login state, prompts the current login information of the user, and the user selects whether to continue logging in, if so, the previous machine is forced to be offline, and the current machine is successfully logged in; and if the login is cancelled, returning to a login interface. The usage flow is shown in fig. 3.
b) Single sign-on
When a user uses the universal client software integration system to log in and authenticate identity for the first time at a client, after a user name and a password pass verification at a server, the server returns user information and an identity authentication token to the universal client software integration system at the client, and the universal client software integration system caches the token locally; if the plug-in started by the universal client software integration system is an executable program or a dynamic library plug-in, the universal client software integration system transmits information such as a user name, a password and the like to the executable program or the dynamic library plug-in according to an agreed format; if the Web page plug-in is started, the Web page plug-in acquires a user name, a password and an identity token from the universal client software integration system through an interface, submits the identity token to a server for verification, and starts the plug-in after the verification is successful; each plug-in does not need secondary identity authentication, thereby realizing single sign-on. The specific implementation principle is shown in fig. 4.
c) Heartbeat detection
After the user logs in successfully, a heartbeat detection mechanism is established between the server and the client universal client software integration system, the server sends heartbeat messages to the client universal client software integration system at regular time, and if the client universal client software integration system returns the heartbeat messages, the client universal client software integration system operates normally; if the server side does not acquire the heartbeat message of the client-side general client software integration system for three times continuously, the client-side general client software integration system is considered to be abnormally quitted, and the login state of the user at the client side is updated, and the specific flow is shown in fig. 5.
d) Login state management
The login state management is composed of login state records and login state displays.
The login state record is used for recording login user name, login role, login time, login IP, logout time and the like.
And the login state display displays information such as login user name, login role, login time, login IP (Internet protocol), logout time and the like through a visual interface.
The method for providing various plug-ins with identity information by the universal client software integration system comprises the following steps:
a) c + + interface: QString getUserInfo ()
Name: interface for obtaining identity information
The functions are as follows: obtaining user name, password, identity token information and the like
Inputting: none.
And (3) outputting: and returning a user name, a password and an identity token by using the character string in the JSON format.
The format is { user: userVal, passswd: passswdVal, token: token Val }', and the format comprises three key value pairs, wherein the key value pairs are used in different directions and separated from each other, and the key value pairs are used in different directions and separated from each other; wherein, "user", "passsd" and "token" are fixed character strings, and "key", "userVal", "passdVal" and "token Val" of a key-value pair represent "values" of the key-value pair, respectively represent a user name, a password and an identity token.
b) A JAVA interface: getUserInfo ()
Name: interface for obtaining identity information
The functions are as follows: obtaining user name, password, identity token information and the like
Inputting: none.
And (3) outputting: and returning a user name, a password and an identity token by using the character string in the JSON format.
The format is { user: userVal, passswd: passswdVal, token: token Val }', and the format comprises three key value pairs, wherein the key value pairs are used in different directions and separated from each other, and the key value pairs are used in different directions and separated from each other; wherein, "user", "passsd" and "token" are fixed character strings, and "key", "userVal", "passdVal" and "token Val" of a key-value pair represent "values" of the key-value pair, respectively represent a user name, a password and an identity token.
3. Interface style management and one-key switching
1) Functional composition
The interface style management and the one-key switching are composed of interface resource file reading, main interface bottom plate construction, unified interface display style display and interface display style switching, and the function components are shown in fig. 6.
Reading an interface resource file: reading a pre-designed interface style sheet file, a main interface icon, a font file and the like to form a typical interface display style scheme;
constructing a main interface bottom plate: reading interface display style scheme information and constructing a main interface bottom plate control;
displaying the unified interface display style: the display control is carried out on the main interface and relevant functional components (a menu bar, a tool bar, a status bar and the like);
interface display style switching: and under the condition of not restarting the running plug-in and the universal client software integrated system, responding to the style switching command and switching to the specified interface display style as required.
2) Principle of implementation
a) Executable file and dynamic library plug-in interface style management principle
A class QPlastiquestyle derived from QStyle is selected as a style base class of the software, and an SM _ BlackTechStyle class and an SM _ BlueTechStyle class derived from QPlastiquestyle are selected as style implementation classes. Constructing an SM _ GenericStyleManage class as a style management class to realize the management of the system style instance;
calling a style management singleton function SM _ GenericStyleMenage in a start () function, inputting a main interface pointer, a default Resolution and a default style name parameter into a style management class Instance, then calling a GenericStyleMenage (QWidget base part, ENUM _ RESOLUTION _ RATIO curRatio _ RATIO, QString StyleMenage) function to read a style resource file such as QSS and icon, generating a display style scheme, selecting a scheme matching the input style parameter, and generating a main interface corresponding to the style display. Then calling a SenderScript (Stylestr) function to send display style parameters to various integrated dynamic libraries, processes and Web pages;
receiving style information in a slotReceiveScript (tmpScript) response function of the integrated dynamic library and the executable file plug-in, and performing display style switching of the response;
the SM _ GenericStyleEmage example calls the policy () function to refresh the client main process interface, so that the display style of all interfaces is uniform.
b) Web page plug-in interface style management principle
And introducing a uniform CSS (cascading style sheets) level style sheet file into the Web page, generating a display style scheme, selecting a scheme matched with the input parameters, and keeping the style consistent with the interface style of the client main process. Sending display style parameters to the integrated Web page plug-in through a switchTheme (themeName) interface, and uniformly switching styles;
the Web page plug-in receives the message of the frame switching style interface through a SlotToSwitchTheme (the themeName) function, switches the display style and keeps consistent with the frame.
c) Principle for realizing one-key switching of interface display style
The interface display style one-key switch is initiated from a style switch button on the universal client software integration system. After a user clicks a style switching button, the universal client software integration system executes a ToShiftStyle (QString newStyleName) function, switches to a main interface with a corresponding style, and calls a SenderScript (StyleStyleSt) function to send interface display style parameters to various integrated dynamic libraries, executable files and Web page plug-ins.
The integrated executable file and the dynamic library plug-in respond through a slottreceivescript (tmpscript) function and execute interface display style switching, and the Web page plug-in responds through a slottwitchname (string the named) function and executes interface display style switching.
3) Style switching related interface function
And providing a C + + language interface and a JAVAScript language interface.
(1) C + + language interface
a) Interface name: style management class constructor
GenericStyleManage(QWidget*baseparent,ENUM_RESOLUTION_RATIO curRatio,QString curStyleName)
Description of the parameters:
QWidget basic parent: parent window pointer
ENUM _ RESOLUTION _ RATIO current RATIO: the resolution parameters can be 1920 × 1080, 1280 × 1024 or 1024 × 768
QString currstylename: initializing style names
b) Interface name: switching interface display resolution (switchable a certain style to display at different resolutions)
void SlottoShiftRatio(ENUM_RESOLUTION_RATIO newRatio)
Description of the parameters:
ENUM _ RESOLUTION _ RATIO newRatio: the new resolution parameters can be selected from 1920 × 1080, 1280 × 1024 and 1024 × 768
c) Interface name: display component initialization
void SlottoSetInitShowGeometry()
d) Interface name: interface display style switching initiating interface
void ToShiftStyle(QString newStyleName)
Description of the parameters:
QString newStyleName: new switched style names
e) Interface name: interface display style switching response interface
void SlottoShiftStyle(QString newStyleName＝QString("DefaultStyle"))
Description of the parameters:
QString newStyleName: new switched style names
f) Interface name: interface display style switching message sending interface
void SendScript(QString StyleStr)
Description of the parameters:
QString StyleSttr is the style information content;
g) interface name: interface display style switching message receiving response interface
void slotReceiveScript(QString tmpSrcipt)
Description of the parameters:
QString tmpScript style information content;
(2) JavaScript language interface
a) Interface name: initiating style switching function
switchTheme(String themeName)
Description of the parameters:
string the mename: name of new switching style
b) Interface name: interface display style switching response interface
SlotToSwitchTheme(String themeName)
Description of the parameters:
string the mename: name of newly switched style
4) Flow of use
a) Executable file and dynamic library plug-in interface display style switching process
Step one
Preparing interface display style resource files, designing a plurality of sets of interface display style schemes in advance, manufacturing a plurality of sets of interface resource files according to the common resolution of the system and each set of style schemes, and then compiling QSS files according to the design.
Step two
And in the interface display style loading stage, loading an interface resource file and a QSS file by the universal client software integration system, generating an interface display style scheme, automatically identifying the resolution of the display, and selecting the interface display style scheme corresponding to the resolution.
Step three
And in the interface display style display stage, the universal client software integration system generates a uniform system display interface according to the selected interface display style scheme and displays the uniform system display interface after the system is started. When a user needs to switch the system style by one key, a c + + style switching interface of the universal client software integration system can be called to send style switching information, after the universal client software integration system receives the style switching information, an interface display style scheme corresponding to the current resolution ratio is selected according to the interface display style scheme name selected by the user, the generation and display of a new style interface are completed, meanwhile, the universal client software integration system forwards the style switching information to various integrated plug-ins, and after the plug-ins receive the information, the plug-ins complete the style switching of respective display interfaces.
b) Web page plug-in interface display style switching process
Step one
And in the interface display style design stage, a plurality of sets of interface display style schemes are designed in advance, a plurality of sets of interface resource files are manufactured according to the common resolution of the system and each set of style scheme, and then CSS files are compiled according to the design.
Step two
And in the interface display style loading stage, loading an interface display style resource file by the Web service framework, generating a Web interface display style scheme, automatically identifying the resolution of the display, and selecting the interface display style scheme corresponding to the resolution.
Step three
And in the Web page display stage, the Web service frame generates a Web page according to the interface display style scheme and displays the Web page in the browser. When a user needs to switch the system style by one key, the Web page plug-in receives style switching information from the universal client software integration system and calls a style switching interface. And the Web service framework selects an interface display style scheme to be switched according to the parameters, then completes Web page generation and display in the browser, and completes Web page display style switching.
4. Signal lamp
1) Functional composition
The signal lamp is composed of signal lamp compiling, signal lamp client plug-in, signal lamp secondary development kit and other functions, wherein the client plug-in comprises signal lamp display plug-in and signal lamp message plug-in, and the function composition is as shown in fig. 9.
Signal lamp assembly: maintaining the mapping relation between the application plug-in and the signal lamp; after the system is deployed, compiling the mapping relation between the application plug-in and the signal lamp according to the use requirement;
signal lamp client plug-in components: when the signal lamp client plug-in is started, reading a corresponding editing result from the editing table according to user or role information, displaying signal lamps in sequence by combining a function menu in client application editing information, receiving the signals in real time, lighting the signal lamps, and responding to the clicking operation of the signal lamps;
secondary signal lamp development kit: providing a secondary development interface of two development languages of C + +, JAVA for an application software developer needing integration to develop; when the integrated application plug-in runs, the signals needing to be notified are transmitted to a secondary development kit according to a specified format, the secondary development kit searches the current online role or user and sends the signals to one or more signal lamp client plug-ins where the role or user is located.
2) Principle of implementation
The signal lamp operating principle is shown in fig. 10.
A signal lamp compiling function on the server side provides a man-machine interaction interface, and the mapping relation between the signal lamp and the application plug-in is recorded;
reading an editing result when a signal lamp client plug-in on a client is started, identifying a function menu with a signal lamp from a preset configuration file, and displaying the function menu in sequence; if the compiled signal lamp is not in the configuration file, the signal lamp is not displayed;
an application plug-in (distinguishing two development languages of C + + and JAVA) calls an interface of the signal lamp secondary development package or sends a signal corresponding to the application to the signal lamp secondary development package;
the signal lamp secondary development kit acquires information such as an IP address of a current login user corresponding to a receiving role according to the user role and the user login state;
the signal lamp secondary development kit sends the signal to a signal lamp client plug-in unit of the designated client according to the IP address;
the signal lamp client plug-in receives the signal, changes the state of the signal lamp and gives out prompt information;
and clicking a corresponding signal lamp, starting a corresponding plug-in (setting the plug-in if the software is started) by the universal client software integrated system through a starting script configured by the signal lamp, opening a corresponding webpage if the software is a Web page plug-in, and starting a corresponding executable program or a dynamic library if the software is an executable program plug-in or a dynamic library plug-in.
3) Signal lamp dependent interface function
Interface name: and the signal sending interface sends a message to the designated role and the application.
The specific function is as follows: sendSignal (Array < String > roleIDs, String appID, String message)
Description of the parameters:
and if the role IDs are null, the role IDs are sent to all the clients provided with the application.
appID: using signal light identification
message: specific message content
4) The usage flow is shown in fig. 11.
And (3) a compiling stage: establishing a mapping relation between the application plug-in and the signal lamp through a signal lamp compiling function;
a loading stage: loading and displaying the signal lamp by the signal lamp client side plug-in according to the signal lamp compiling result and combining a preset function menu;
a sending stage: the application plug-in calls a message interface provided by the signal lamp to send a message; and the signal lamp software of the logged-in user corresponding to all the receivers lights the signal lamp.
If the system integrates 10 application plug-ins, wherein only 4 application plug-ins need to integrate and use the signal lamp function, only one-to-one mapping relation between the 4 application plug-ins and the signal lamp is established in the compiling stage, and only 4 signal lamps are displayed at the signal lamp position in the loading stage; and after the signal lamp receives the signal state change, clicking the signal lamp to start or activate the corresponding application plug-in.
The present invention provides a general client software integration system, and a method and a way for implementing the technical solution are many, and the above description is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, a plurality of modifications and embellishments can be made without departing from the principle of the present invention, and these modifications and embellishments should also be regarded as the protection scope of the present invention. All the components not specified in the present embodiment can be realized by the prior art.
Claims (10)
1. A universal client software integration system is characterized by comprising a basic functional layer, a framework extension functional layer and an application support functional layer;
the basic function layer is used for providing integration of various plugins based on Poco modules for the universal client software integration system, and comprises integration and related functions of executable program plugins, dynamic library plugins and Web page plugins;
the framework extension functional layer is used for providing function extension for the universal client software integrated system, and comprises plug-in message management, plug-in state monitoring, display layout customization, shortcut button and menu arrangement, display resolution adaptation, interface style management and one-key switching functions, and providing a network transmission interface and a data access interface to support secondary development;
the application support function layer is used for providing support capacity for application plug-ins and application systems, including signal lamps and user login management, and can be expanded according to application requirements.
2. The system of claim 1, wherein the executable program plug-in, the dynamic library plug-in, and the Web page plug-in are based on a Poco component to package various types of plug-ins of the client, and based on OSGI standard, adopt bundle mechanism to integrate the plug-ins, provide full life cycle management of the plug-ins from start, operation, update to close exit, provide process keep-alive function, provide message interaction management between the same type of plug-ins and different types of plug-ins;
the message interaction between the dynamic library plug-ins is realized based on an in-process broadcasting mechanism;
and the information interaction among the plug-ins of other types is realized by an information transmission mode based on a TCP protocol.
3. The system of claim 2, wherein the user login management of the application support function layer comprises single user login, single login, heartbeat detection, login status management functions;
the single-user login means that: the same user can only log in on the universal client software integrated system on one client at the same time, when the same user name is used for logging in again on the universal client software integrated system on the other client, the logged prompt information is given, if the user selects to continue logging in, the user of the previous client is forced to be offline, the universal client software integrated system is closed to log out, and the logging operation of the user of the client is continued; if the user selects to cancel the login, returning to a login interface;
the single sign-on is as follows: the user uses the universal client software integration system to log in and authenticate the identity for the first time at the client, after the user name and the password pass the verification at the server, the server returns the user information and the identity authentication token to the universal client software integration system of the client, and the universal client software integration system caches the token locally; if the plug-in started by the universal client software integration system is an executable program or a dynamic library plug-in, the universal client software integration system transmits a user name and a password to the executable program or the dynamic library plug-in according to an agreed format; if the Web page plug-in is started, the Web page plug-in acquires a user name, a password and an identity token from the universal client software integration system through an interface, submits the identity token to a server for verification, and starts the plug-in after the verification is successful; secondary identity authentication is not needed in the use process of each subsequent plug-in, so that the single sign-on capability is realized;
the heartbeat detection means: after the user logs in successfully, a heartbeat detection mechanism is established between the server and the client universal client software integration system, the server sends heartbeat messages to the client universal client software integration system at regular time, and if the client universal client software integration system returns the heartbeat messages, the client universal client software integration system operates normally; if the server side does not acquire the heartbeat message of the client-side general client software integration system for three times continuously, the client-side general client software integration system is considered to be abnormally quitted, and the login state of the user at the client side is updated;
the login state management means: and the management and query functions of login user name, login role, login IP address and login time are provided through a visual interface.
4. The system of claim 3, wherein the framework extension functional layer further provides the following functionality:
executable program plug-in message management: supporting message interaction among executable program plug-ins, between the executable program plug-ins and the dynamic library plug-ins, and between the executable program plug-ins and the Web page plug-ins, and managing messages;
dynamic library plug-in message management: supporting message interaction among dynamic library plug-ins, between the dynamic library plug-ins and executable program plug-ins, and between the dynamic library plug-ins and Web page plug-ins, and managing messages;
web page plug-in message management: supporting message interaction between Web page plug-ins, between the Web page plug-ins and dynamic library plug-ins, between the Web page plug-ins and executable program plug-ins, and possibly managing messages;
customizing a display layout: supporting layout customization of frequently displayed interfaces such as a system main interface menu, a shortcut button bar, a signal lamp and the like;
monitoring the plug-in state: supporting the state monitoring of the executable program and the dynamic library type plug-in;
shortcut button and menu arrangement: the shortcut button and the menu on the frame main interface are arranged according to roles, and the shortcut button and the menu can be associated with various integrated plug-ins;
display resolution adaptation: the system main interface is provided with the capability of automatically adapting to various resolutions of the display, and particularly three common resolution adaptation capabilities of 1920 × 1080, 1280 × 1024 and 1024 × 768 are provided;
interface style management and one-key switching;
a network transmission interface: providing a unified interface for information interaction between the support system and the integrated plug-in;
a data access interface: and a unified interface for supporting the system and the integrated plug-in to access the database is provided.
5. The system of claim 4, wherein the framework extension functional layer provides interface style management and one-key switching, the interface style management and the one-key switching are composed of interface resource file reading, main interface backplane construction, unified interface display style presentation and interface display style switching, and the method comprises:
reading an interface resource file: reading a pre-designed interface style sheet file, a main interface icon and a font file to form an interface display style scheme;
constructing a main interface bottom plate: reading interface display style scheme information and constructing a main interface bottom plate control;
displaying the unified interface display style: performing display control on the main interface and the related functional components;
interface display style switching: all the displayed plug-in interfaces can be switched into a specified display style according to requirements under the condition of not restarting the running plug-in and the universal client software integrated system, and the plug-in interfaces of the QT development and the plug-in of the JAVA development can be switched into the specified display style.
6. The system of claim 5, wherein the application support function layer provides a signaling light function, the signaling light function consisting of a signaling light orchestration, a signaling light client plug-in, and a signaling light secondary development kit, wherein the client plug-ins include a signaling light display plug-in, a signaling light message plug-in:
signal lamp assembly: maintaining the mapping relation between the application plug-in and the signal lamp; after the system is deployed, compiling the mapping relation between the application plug-in and the signal lamp according to the use requirement;
signal lamp client plug-in components: when the signal lamp client plug-in is started, reading a corresponding compiling result from the compiling table according to user or role information, displaying signal lamps in sequence by combining a function menu in the client application compiling information, receiving the signal in real time to light the signal lamp, and starting or activating the corresponding plug-in after the user clicks the signal lamp;
secondary signal lamp development kit: providing a secondary development interface of two development languages of C + +, JAVA for an application software developer needing integration to develop; when the integrated application plug-in runs, the signals needing to be notified are transmitted to a secondary development kit according to a specified format, the secondary development kit searches the current online role or user and sends the signals to one or more signal lamp client plug-ins where the role or user is located.
7. The system according to claim 6, wherein the signal lamp configuration function of the application support function layer provides a human-computer interaction interface for inputting the mapping relation between the signal lamp and the application software;
reading the compiling result when the signal lamp client plug-in is started, identifying a function menu with signal lamps from a preset configuration file, and displaying the function menu in sequence; if the compiled signal lamp is not in the configuration file, the signal lamp does not display;
the application plug-in calls an interface of the signal lamp secondary development kit or sends a signal corresponding to the application to the signal lamp secondary development kit;
the signal lamp secondary development kit acquires IP address information of a current login user corresponding to a receiving role according to the user role and the user login state;
the signal lamp secondary development kit sends a signal corresponding to the application plug-in to a signal lamp client plug-in of a specified client according to the IP address;
the signal lamp client plug-in receives the signal, changes the state of the signal lamp and gives out prompt information;
and clicking a signal lamp, starting a corresponding plug-in by the general client software integration system through a starting script configured by the signal lamp, opening a corresponding webpage if the plug-in is a Web page plug-in, and starting a corresponding executable program or a dynamic library if the plug-in is an executable program or a dynamic library plug-in.
8. The system of claim 7, wherein the base functional layer further provides the following functions:
(1) executable program plug-in integration: the system is responsible for the management, integration and scheduling of the executable program plug-in based on the process;
(2) and (3) executable program plug-in full life cycle management: the method has the full life cycle management capability of the executable program plug-in, including starting, stopping and uninstalling;
(3) executable program plug-in attribute management: providing the display and editing functions of the attributes of the executable program plug-ins, managing the starting parameters of the executable program plug-ins, displaying the control parameters and configuring the parameter attributes of the system required by the executable program plug-ins;
(4) dynamic library plug-in integration: the dynamic library plug-in is responsible for providing the management, integration and scheduling functions of the dynamic library plug-in;
(5) dynamic library plug-ins into lifecycle management: the method has the full life cycle management capability of the dynamic library plug-in, including loading, analyzing, starting, updating, stopping and unloading;
(6) process keep-alive: for the process needing to keep the running state, the state of the process is mastered in real time, and if the process is found to be absent, the processes can be restarted, wherein the two modes comprise a process starting mode for starting the process and recovering the initial state, and a process starting mode for recovering the last state;
(7) web page integration and browser control: the method is used for integrating the Web pages into the frame, controlling the browser of the operating system to open the specified Web page and controlling the size and display of the browser on the specified display.
9. The system of claim 8, wherein the system performs the following steps to complete the executable file and dynamic library plug-in interface display style switching process:
a1, preparing interface display style resource files, designing more than two sets of interface display style schemes in advance, manufacturing a plurality of sets of interface resource files according to the common resolution of the system and each set of style schemes, and compiling QSS files according to the design;
a2, loading interface display style, loading interface resource files and QSS files by the universal client software integration system, generating an interface display style scheme, automatically identifying the resolution of a display, and selecting the interface display style scheme corresponding to the resolution;
step a3, in the interface display style display stage, the universal client software integration system generates a uniform system display interface according to the selected interface display style scheme, and displays the uniform system display interface after the system is started; when a user needs to switch the system style by one key, calling a c + + style switching interface of the universal client software integration system, sending a style switching message, after receiving the style switching message, the universal client software integration system selects an interface display style scheme corresponding to the current resolution according to the interface display style scheme name selected by the user, completing the generation and display of a new style interface, meanwhile, the universal client software integration system forwards the style switching message to various integrated plug-ins, and after the plug-ins receive the message, the plug-ins complete the style switching of respective display interfaces.
10. The system of claim 9, wherein the system performs the following steps to complete the Web page plug-in interface display style switching process:
b1, designing more than two interface display style schemes in advance in the interface display style design stage, manufacturing a plurality of sets of interface resource files according to the common resolution of the system and each set of style scheme, and then compiling CSS files according to the design;
b2, loading interface display style resource files by the Web service framework, generating a Web interface display style scheme, automatically identifying the resolution of the display, and selecting the interface display style scheme corresponding to the resolution;
step b3, in the Web page display stage, the Web service frame generates a Web page according to the interface display style scheme and displays the Web page in the browser; when a user needs to switch the system style by one key, the Web page plug-in receives style switching information from the universal client software integration system and calls a style switching interface; and the Web service framework selects an interface display style scheme to be switched according to the parameters, then completes Web page generation and display in the browser, and completes Web page display style switching.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011276055.7A CN112416345B (en) | 2020-11-16 | 2020-11-16 | Universal client software integration system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011276055.7A CN112416345B (en) | 2020-11-16 | 2020-11-16 | Universal client software integration system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112416345A true CN112416345A (en) | 2021-02-26 |
| CN112416345B CN112416345B (en) | 2022-10-21 |
Family
ID=74832715
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011276055.7A Active CN112416345B (en) | 2020-11-16 | 2020-11-16 | Universal client software integration system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416345B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113110895A (en) * | 2021-03-19 | 2021-07-13 | 深圳震有科技股份有限公司 | IPC-based method, terminal and storage medium for setting single application program |
| CN113568765A (en) * | 2021-08-03 | 2021-10-29 | 北京数码视讯技术有限公司 | Development method and system for client |
| CN113569180A (en) * | 2021-07-28 | 2021-10-29 | 中国电子科技集团公司第二十八研究所 | Universal browser extension system |
| CN115941656A (en) * | 2022-12-29 | 2023-04-07 | 南京维拓科技股份有限公司 | Integration method of design software in industrial design |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101699393A (en) * | 2009-10-09 | 2010-04-28 | 中国电子科技集团公司第二十八研究所 | Intelligent software interface dynamic generation method facing network |
| CN102638454A (en) * | 2012-03-14 | 2012-08-15 | 武汉理工大学 | Plug-in type SSO (single signon) integration method oriented to HTTP (hypertext transfer protocol) identity authentication protocol |
| WO2014000281A1 (en) * | 2012-06-29 | 2014-01-03 | 华为技术有限公司 | Identity authentication method and device |
| WO2018014657A1 (en) * | 2016-07-20 | 2018-01-25 | 中兴通讯股份有限公司 | Unified portal method, apparatus and system |
-
2020
- 2020-11-16 CN CN202011276055.7A patent/CN112416345B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101699393A (en) * | 2009-10-09 | 2010-04-28 | 中国电子科技集团公司第二十八研究所 | Intelligent software interface dynamic generation method facing network |
| CN102638454A (en) * | 2012-03-14 | 2012-08-15 | 武汉理工大学 | Plug-in type SSO (single signon) integration method oriented to HTTP (hypertext transfer protocol) identity authentication protocol |
| WO2014000281A1 (en) * | 2012-06-29 | 2014-01-03 | 华为技术有限公司 | Identity authentication method and device |
| WO2018014657A1 (en) * | 2016-07-20 | 2018-01-25 | 中兴通讯股份有限公司 | Unified portal method, apparatus and system |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113110895A (en) * | 2021-03-19 | 2021-07-13 | 深圳震有科技股份有限公司 | IPC-based method, terminal and storage medium for setting single application program |
| CN113569180A (en) * | 2021-07-28 | 2021-10-29 | 中国电子科技集团公司第二十八研究所 | Universal browser extension system |
| CN113569180B (en) * | 2021-07-28 | 2024-01-26 | 中国电子科技集团公司第二十八研究所 | Universal browser expansion system |
| CN113568765A (en) * | 2021-08-03 | 2021-10-29 | 北京数码视讯技术有限公司 | Development method and system for client |
| CN113568765B (en) * | 2021-08-03 | 2023-12-26 | 北京数码视讯技术有限公司 | Development method and system of client |
| CN115941656A (en) * | 2022-12-29 | 2023-04-07 | 南京维拓科技股份有限公司 | Integration method of design software in industrial design |
| CN115941656B (en) * | 2022-12-29 | 2023-09-08 | 南京维拓科技股份有限公司 | Integration method of design software in industrial design |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112416345B (en) | 2022-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112416345B (en) | Universal client software integration system | |
| US7617459B2 (en) | Apparatus, system, and method for automatically generating a web interface for an MFS-based IMS application | |
| CA2777443C (en) | Automated enterprise software development | |
| US7770151B2 (en) | Automatic generation of solution deployment descriptors | |
| US7546298B2 (en) | Software, devices and methods facilitating execution of server-side applications at mobile devices | |
| US7865528B2 (en) | Software, devices and methods facilitating execution of server-side applications at mobile devices | |
| US7031798B2 (en) | Event management systems and methods for the distribution of motion control commands | |
| US8850388B2 (en) | Controlling application features | |
| US20020046240A1 (en) | Web server framework | |
| US8438418B2 (en) | Simplifying automated software maintenance of data centers | |
| Vincent | Django for Beginners: Build websites with Python and Django | |
| AU2013213683B2 (en) | A method and system of application development for multiple device client platforms | |
| CN110928625A (en) | Application program operation control method and device, electronic equipment and storage medium | |
| CN112988165A (en) | Kubernetes-based interactive modeling method and device, electronic equipment and storage medium | |
| CN115658529A (en) | Automatic testing method for user page and related equipment | |
| Shepherd | Microsoft ASP. NET 4 Step by Step | |
| CN114661375A (en) | Application integration method and device | |
| Kasemir et al. | Control system studio guide | |
| Cisco | 3 - Creating Access Policy Modules | |
| CN105049338A (en) | Interface generating method and device of smart device based on instant communication | |
| Petelj et al. | Web based solution for smart home functionality extension and control | |
| WO2022137647A1 (en) | Information processing device, information processing system, and user interface providing method | |
| US20230111113A1 (en) | Page loading method and display apparatus | |
| Newton | The Definitive Guide to the Microsoft Enterprise Library | |
| Eaves et al. | Apache Tomcat Bible |
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 | ||
| CB02 | Change of applicant information |
Address after: 210000 No.1, Lingshan South Road, Qixia District, Nanjing City, Jiangsu Province Applicant after: THE 28TH RESEARCH INSTITUTE OF CHINA ELECTRONICS TECHNOLOGY Group Corp. Address before: 210007 No. 1 East Street, alfalfa garden, Jiangsu, Nanjing Applicant before: THE 28TH RESEARCH INSTITUTE OF CHINA ELECTRONICS TECHNOLOGY Group Corp. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |