CN103164239A - Plug-in implement method based on micro network visual platform - Google Patents
Plug-in implement method based on micro network visual platform Download PDFInfo
- Publication number
- CN103164239A CN103164239A CN2012105370561A CN201210537056A CN103164239A CN 103164239 A CN103164239 A CN 103164239A CN 2012105370561 A CN2012105370561 A CN 2012105370561A CN 201210537056 A CN201210537056 A CN 201210537056A CN 103164239 A CN103164239 A CN 103164239A
- Authority
- CN
- China
- Prior art keywords
- plug
- unit
- loading
- class
- manager
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a plug-in implement method based on a micro network visual platform. Plug-ins are loaded through a plug-in management class. The plug-in loading mode comprises simple loading of a plurality of plug-ins, simple loading of a plug-in, loading of plug-ins under walking contents, loading of static library plug-ins and loading of plug-ins through configuration files. Each plug-in comprises functions of information, an order, an event and an interface. Through the functions, interface interaction of menus, toolbars and the like, and functional call among components are achieved. Life cycles of the components can be maintained through an intelligent indicator, and robustness, safety and uniqueness of data can be ensured. The function of the loading of the static library plug-ins is provided, when software is published, only one main program file is needed, a plurality of static library modules are arranged in the interior, thus, not only are the advantages that the plug-ins can be reusable played, but also the number of program files can be reduced, the plug-ins are enabled to provide cross-platform support, and reusability of the program can be improved. The method is suitable for solving the coupling problem between the micro network visual platform and each plug-in of different sub systems.
Description
Technical field
The present invention relates to the technical field of the microgrid Visualization Platform application of electric system, particularly relate to a kind of plug-in unit implementation method based on the microgrid Visualization Platform.
Background technology
The starting point of plug-in part technology is mainly in order to make software can carry out neatly expanded function, and does not need master routine (framing program) is recompilated and issues.The function of software is decided by framing program and plug-in unit.Have a specific interface between framing program and plug-in unit, both must transmit data or control information by this interface for they, to realize software function.
Present plug-in unit mostly is the single environment operation, does not provide operating system cross-platform support.Simultaneously, plug-in unit mostly is customized development, and is high with the framework degree of coupling, is unfavorable for the multiplexing of program, function, and between each plug-in unit, communication modes is loaded down with trivial details simultaneously, and development is complicated, mistake easily occurs.
Summary of the invention
For the problem that exists in the above-mentioned background technology, the object of the present invention is to provide a kind of plug-in unit implementation method based on the microgrid Visualization Platform, can make plug-in unit that cross-platform support is provided, improve the reusability of program.
A kind of plug-in unit implementation method based on the microgrid Visualization Platform comprises the following steps:
Application program loading of plug-in manager is to the load request of described plugin manager transmission plug-in unit;
Described plugin manager is sent loading messages according to described load request to the plug-in unit of correspondence;
The plug-in unit that receives described loading messages is completed registration in described plugin manager;
Described plugin manager is to the interface class of the described plug-in unit of registered plug-in unit acquisition request, and loads described interface class; The component class register list of the described plug-in unit of acquisition request, and register corresponding component class in described plugin manager according to described component class register list.
In plug-in unit implementation method based on the microgrid Visualization Platform of the present invention, by described plugin manager, each plug-in unit is managed, when the application program loading of plug-in, can carry out by described plugin manager the multiple plug-in unit load modes such as a plug-in unit loads, a plurality of plug-in unit loads, the loading of traversal plug-in unit catalogue.And each plug-in unit is completed registration in described plugin manager after, described plugin manager is first put down in writing the interface class of described plug-in unit, reload the component class of described plug-in unit, can complete interactive function between plug-in unit by described interface class between each plug-in unit, can be by the ad hoc fashion communication between plug-in unit, call, alternately.Static library plug-in unit value-added tax function is provided, only need like this a master program file during releasing software, formed by a plurality of static library modules in inside, can bring into play so the reusable advantage of plug-in unit, can reduce program file quantity again, can make plug-in unit that cross-platform support is provided, improve the reusability of program.
Description of drawings
Fig. 1 is the schematic flow sheet that the present invention is based on the plug-in unit implementation method of microgrid Visualization Platform;
Fig. 2 is of the present invention based on event driven process flow diagram in the plug-in unit implementation method of microgrid Visualization Platform;
Fig. 3 is the schematic flow sheet of plug-in unit loading procedure in one embodiment of the present of invention;
Fig. 4 is event driven execution flow process in one embodiment of the present of invention.
Embodiment
See also Fig. 1, Fig. 1 is the schematic flow sheet that the present invention is based on the plug-in unit implementation method of microgrid Visualization Platform.
Described plug-in unit implementation method based on the microgrid Visualization Platform comprises the following steps:
S101, application program loading of plug-in manager is to the load request of described plugin manager transmission plug-in unit;
S102, described plugin manager is sent loading messages according to described load request to the plug-in unit of correspondence;
S103, the plug-in unit that receives described loading messages is completed registration in described plugin manager;
S104, described plugin manager is to the interface class of the described plug-in unit of registered plug-in unit acquisition request, and loads described interface class; The component class register list of the described plug-in unit of acquisition request, and register corresponding component class in described plugin manager according to described component class register list.
The coupling of program frame of the present invention and plug-in unit and realized simultaneously between each plug-in unit, mutually calling between platform and plug-in unit, thereby improved the reusability of robustness, stability, extendability and the program of system, reduce code development quantity, facilitated multiplexing, the expansion of system.Be particularly suitable for solving the problem of the coupling of microgrid Visualization Platform and each different sub-systems plug-in unit.
Wherein, for step S101, manage by the interface function pointer of described plugin manager to associated component class ID and component class establishment.Intelligent pointer class boost::share_ptr in preferred use Boost function library carries out maintenance management to the life cycle of function.The loading of plug-in unit (structure) when the plug-in unit life cycle comprises program start, the release of calling plug-in unit when withdrawing from program (analysing structure) of program plug-in unit in service.In step S101, whether program at first verification plug-in management class (PluginManager) loads, if do not load load described plug-in management class, and obtains such pointer, if loaded directly got such pointer.
The mode of described plug-in management class loading of plug-in has multiple, comprises that a plurality of plug-in units simply load, a plug-in unit simply loads, travels through plug-in unit loading under catalogue, the loading of static library plug-in unit and by configuration file, plug-in unit loaded.For example:
For step S102, the load request that described plugin manager sends according to described application program is sent loading messages to the plug-in unit of correspondence;
Each plug-in unit that receives described loading messages sends confirmation to described plugin manager after receiving described loading messages.
For step S103, described plugin manager is registered the plug-in unit that receives described loading messages.
For step S104, it is the core of whole card cage that plug-in unit creates, and each plug-in unit and platform can be by funcalls between the Interface realization plug-in unit, between platform and plug-in unit.
Preferably, the interface class of described plug-in unit is comprised of pure virtual function, and has a constant name that is defined by the GUID character string as component class ID.
That is during definition card i/f class, described card i/f class does not have base class, there is no explicit interface function, there is no member variable, all is comprised of pure virtual function.Directly use simultaneously constant name of GUID character string definition, use this constant name in the time of need to using component class ID, do not rely on translation and compiling environment; For example:
The component class of described plug-in unit is preferably inherited from described interface class, realize the interface function that defines in component class, and the constructed fuction of described component class is protection type.
That is when defining the component class of described plug-in unit, the component class of described plug-in unit is inherited from interface class, realizes the interface function that defines in component class.In order for component programming, the constructed fuction of class to be made as the protection type.A component class can be realized a plurality of interfaces, and component class can be inherited.
Described plugin manager loads described interface class and corresponding component class, completes that plug-in unit is loaded.
Preferably, after the loading of completing plug-in unit, further comprise an initialized step, specifically comprise:
Initial message, order, interface and event, and by system definition message expanded menu (Menu) and toolbar (ToolBar) in platform.
When closing application program message is received by system, described plugin manager sends to each plug-in unit according to plug-in unit loading sequence backward and discharges plug-in unit message, each plug-in unit is received releasing memory after described release plug-in unit message, returns to the release success message to described plugin manager.Receive all when plugin manager and return success message backward platform return messages, system can close.
In the present invention " message " realized platform to a plug-in unit, platform to a plurality of plug-in units, a plug-in unit to calling between platform, the employing " interface " of mutually calling between plug-in unit is carried out.In the present invention, " interface " is expanded proposition " event (Event) ", the function of realizing a plurality of plug-in units adjusts back to realize a plug-in unit to the calling of a plurality of plug-in units, and the below introduces event-based model:
First: event driven principle.
The definition event type is mainly to define unique character string in order to distinguish different events, in compilation phase identification format error, has automatically defined internal type simultaneously.The registration response function is that the response function (call back function) of a plurality of same format is recorded, and is associated with simultaneously an event type character string.Trigger event is exactly to find corresponding response function according to the event type character string, calls successively these response functions (synchronization call mode) by the registration sequencing, event argument is passed to the parameter of response function.The present invention realizes by Signal2, Function in the Boost storehouse and the combination of Bind class libraries.
Second: the definition event type.
A plurality of event types of definable in a header file, for example:
At first comprise Triggerevent.h in this document, then use each event types of macro definition such as DEFINE_EVENT_1, using form is as follows:
DEFINE_EVENT_0, _ 1, _ the rreturn value type of the response function of 2 correspondences is void, each response function will call successively.
DEFINE_EVENT_0 (event title, event name identification suffix);
DEFINE_EVENT_1 (event title, parameter type, event name identification suffix);
DEFINE_EVENT_2 (event title, parameter Class1, parameter type 2, event name identification suffix);
The event title will for the assisted class (class name starts with Trigger) of inner structure body of definition and Event triggered, will be used this event title when triggering and response events; The parameter type is the parameter type of response function, and maximum two parameters can be used general type (for example char*, int), or reference type (string﹠amp for example; , const MyObj﹠amp; ); Event name identification suffix is used for avoiding disparate modules identical event title to occur, and inside is combined to form a unduplicated character string constant with event title and sign suffix, for example " EventAdd.login.plg ", " EventAdd.login.plg ".
The the 3rd: the registration response function.
Respond the simple event type with static function, the rreturn value type of function must be consistent with the definition of event type with the parameter list.Can use the static function of common overall situation function or class, for example:
void?InsertNodeFunc(int&?result){...}
void?MyClass::InsertNode(int&?result){...}
These response functions of registration are to the event type of correspondence in the InitializePlugin () function of response function place module or other functions.Use the grand registration response function of REGISTER_OBSERVER, for example:
Entrance function CPP file (module.cpp or main.cpp in response function place module, comprised pluginimpl.h or realized class createObject function) in, need to comprise the observerimpl.h file, can only comprise observerimpl.h file: #include＜observerimpl.h in a CPP file in this module 〉.
Therefore, the plug-in unit implementation method based on the microgrid Visualization Platform of the present invention is completed after plug-in unit loads, can be further comprising the steps, as shown in Figure 2:
S201, the load events manager;
S202, each described plug-in unit receives the initial message that described plugin manager sends, to the described task manager corresponding event of registration and response function;
S203 when described event is triggered, directly is subjected to event driven plug-in unit to send data and notification message to described task manager;
S204, described task manager send data according to described notification message to registered each plug-in unit, and after each described plug-in unit receives described data, the corresponding response function of execution is processed.
Plug-in unit implementation method based on the microgrid Visualization Platform of the present invention is applicable to solve the coupling of electric system microgrid Visualization Platform and each different sub-systems plug-in unit.By plug-in management class loading of plug-in, the plug-in unit load mode comprises that a plurality of plug-in units simply load, a plug-in unit simply loads, travels through plug-in unit loading under catalogue, the loading of static library plug-in unit and by configuration file, plug-in unit loaded.Plug-in unit comprises message (Message), order (Command), event (Event) and interface (Interface) function, and realizes the interfaces (UI) such as menu (Menu), tool bar (ToolBar) by above-mentioned functions alternately and the inter-module funcall.(SharePtr) safeguards component lifecycle by intelligent pointer, guarantees robustness, security and the uniqueness of data.
Therefore, have the following advantages:
1) interface definition simple and flexible adopts common C++ interface, and the structure that namely is comprised of pure virtual function does not need special base class; Can use simultaneously the various typess of variables of C++, not be subjected to the such constraint of com interface.
2) interface with realize separating based on the plug-in unit of microgrid Visualization Platform, the interface header file is provided to the outside, and can realizes one or more interfaces by an assembly in inside, do not need externally to derive such or expose and realize details.Can allow a plurality of module concurrent developments, module not exist each other compiling to rely on (files such as LIB that do not need other plug-in units).
3) adopting the Boost intelligent pointer to come the life cycle of maintenance interface, can be another interface from an interface dynamic translation, can distinguish to come from quoting or coming from quoting of plug-in unit inside of external plug-in.
4) the transparent deployment of assembly, an assembly only need to use the interface of other assemblies, does not need to be concerned about this interface is realized in which plug-in unit.Can as required each be realized that class merges or splits, it is distributed in different plug-in units, and the interface user be unaffected.In addition, which catalogue plug-in unit is deployed in does not affect the use of card i/f yet.
5) module replaceable, can expand.Can replace as required certain plug-in unit, as long as this plug-in unit based on the microgrid Visualization Platform has been realized identical interface, even built-in function is not identical.So just realized that plug-in unit is replaceable, function that make up as required.By support more interface in new plug-in unit, can expand more function.Can be in new plug-in unit local some interface or the partial function of replacing original plug-in unit, realize reusing and expanding.
The below is with the concrete process description plug-in unit implementation method based on the microgrid Visualization Platform of the present invention:
See also Fig. 3 and Fig. 4, Fig. 3 is the schematic flow sheet of plug-in unit loading procedure in one embodiment of the present of invention;
At first application A pplication request and loading of plug-in manager LoadPlugInManager, after loading is completed, send the message LoadPlugIns of loading of plug-in.Described plugin manager PlugInManager sends loading messages LoadPlugaccording to described load request to A plug-in unit and the B plug-in unit of correspondence; The described loading messages of A plug-in unit response returns to acknowledge message LoadPlugInEx, described plugin manager is completed registration RegisterPlugIn to the A plug-in unit, the interface class GetModuleInterface of the described plug-in unit of acquisition request, and load described interface class AddModule; Component class register list RegisterClassEntryTable, the GetClassEntryTable of the described plug-in unit of acquisition request, and register corresponding component class RegisterClass in described plugin manager according to described component class register list.After completing loading, send initial message InitPlugIn, carry out initialization.
Fig. 4 is event driven execution flow process in one embodiment of the present of invention.
Described plugin manager sends initial message InitPlugIn to each plug-in unit, and wherein the C plug-in unit is for directly being subjected to event driven plug-in unit, and A plug-in unit and B plug-in unit are the plug-in unit that is subjected to C plug-in unit readjustment.After A plug-in unit and B plug-in unit are received described initial message InitPlugIn, to the task manager ChangeManager corresponding event of registration and response function RegisterObserver;
When trigger event, directly be subjected to event driven C plug-in unit to send data and notification message Data::Notify (), ChangeNotify to described task manager; Described task manager is according to described notification message, send data Updata () to registered A plug-in unit and B plug-in unit, after described A plug-in unit and B plug-in unit receive described data, the corresponding response function of execution is processed, and responds described event OnEnventX ().
One of ordinary skill in the art will appreciate that all or part of flow process that realizes in above-mentioned embodiment, to come the relevant hardware of instruction to complete by computer program, described program can be stored in a computer read/write memory medium, this program can comprise the flow process as the respective embodiments described above when carrying out.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-Only Memory, ROM) or random store-memory body (Random Access Memory, RAM) etc.
The above embodiment has only expressed several embodiment of the present invention, and it describes comparatively concrete and detailed, but can not therefore be interpreted as the restriction to the scope of the claims of the present invention.Should be pointed out that for the person of ordinary skill of the art, without departing from the inventive concept of the premise, can also make some distortion and improvement, these all belong to protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (8)
1. the plug-in unit implementation method based on the microgrid Visualization Platform, is characterized in that, comprises the following steps:
Application program loading of plug-in manager is to the load request of described plugin manager transmission plug-in unit;
Described plugin manager is sent loading messages according to described load request to the plug-in unit of correspondence;
The plug-in unit that receives described loading messages is completed registration in described plugin manager;
Described plugin manager is to the interface class of the described plug-in unit of registered plug-in unit acquisition request, and loads described interface class; The component class register list of the described plug-in unit of acquisition request, and register corresponding component class in described plugin manager according to described component class register list.
2. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 1, is characterized in that, the interface class of described plug-in unit is comprised of pure virtual function, and have a constant name that is defined by the GUID character string as component class ID.
3. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 2, is characterized in that, the component class of described plug-in unit is inherited from described interface class, realize the interface function that defines in component class, and the constructed fuction of described component class is protection type.
4. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 1, is characterized in that, the step of described application program loading of plug-in manager comprises:
Whether described application program check plug-in management class loads, if do not load, loads described plug-in management class and obtains the pointer of described plug-in management class, if loaded directly obtained described pointer.
5. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 1, is characterized in that, the mode of described plugin manager loading of plug-in comprises that a plurality of plug-in units load, single plug-in unit loads; Under the traversal catalogue, all plug-in units loadings, static library plug-in unit load and by configuration file, plug-in unit are loaded.
6. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 1, is characterized in that, component class corresponding to registration further comprises an initialized step afterwards in described plugin manager, specifically comprises:
Initial message, order, interface and event, and by system definition message expanded menu and toolbar in platform.
7. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 6, it is characterized in that, when receiving closing application program message, described plugin manager sends to each plug-in unit according to plug-in unit loading sequence backward and discharges plug-in unit message, each plug-in unit is received releasing memory after described release plug-in unit message, return to the release success message to described plugin manager, described plugin manager receives that the backward platform of described release success message returns to this message.
8. the plug-in unit implementation method based on the microgrid Visualization Platform as claimed in claim 1, is characterized in that, and is further comprising the steps:
The load events manager;
Each described plug-in unit receives the initial message that described plugin manager sends, to the described task manager corresponding event of registration and response function;
When described event is triggered, directly be subjected to event driven plug-in unit to send data and notification message to described task manager;
Described task manager sends data according to described notification message to registered each plug-in unit, and after each described plug-in unit receives described data, the corresponding response function of execution is processed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210537056.1A CN103164239B (en) | 2012-12-11 | 2012-12-11 | Plug-in implement method based on micro network visual platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210537056.1A CN103164239B (en) | 2012-12-11 | 2012-12-11 | Plug-in implement method based on micro network visual platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103164239A true CN103164239A (en) | 2013-06-19 |
| CN103164239B CN103164239B (en) | 2014-11-19 |
Family
ID=48587358
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210537056.1A Active CN103164239B (en) | 2012-12-11 | 2012-12-11 | Plug-in implement method based on micro network visual platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103164239B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103513990A (en) * | 2013-10-11 | 2014-01-15 | 安徽科大讯飞信息科技股份有限公司 | Method for designing high-performance generally-used network framework for distributed processing |
| CN103645919A (en) * | 2013-12-18 | 2014-03-19 | 用友软件股份有限公司 | Method for extending functions of management information system through plugins |
| CN103927180A (en) * | 2014-04-21 | 2014-07-16 | 广州市久邦数码科技有限公司 | Implementation method for functional plug-ins based on Android system and system of functional plug-ins based on Android system |
| WO2015055073A1 (en) * | 2013-10-18 | 2015-04-23 | 北京奇虎科技有限公司 | Method, apparatus and system for reminding message |
| CN106873972A (en) * | 2016-12-30 | 2017-06-20 | 中国电力科学研究院 | Electric Power Network Planning emulation platform computing module cut-in method and system based on plug-in unit |
| CN107203419A (en) * | 2016-03-17 | 2017-09-26 | 阿里巴巴集团控股有限公司 | Intermodule call method, apparatus and system in application program |
| CN107423101A (en) * | 2017-08-01 | 2017-12-01 | 武大吉奥信息技术有限公司 | A kind of application plug gridding issue and management method and system |
| CN108446141A (en) * | 2018-02-28 | 2018-08-24 | 武汉智博创享科技股份有限公司 | A kind of web front end plug-in unit and the method for being scheduled and communicating based on web front end plug-in unit |
| CN108628739A (en) * | 2018-03-19 | 2018-10-09 | 北京奇艺世纪科技有限公司 | A kind of method that Lua scripts are debugged, client, server and debugger |
| CN110109713A (en) * | 2019-04-18 | 2019-08-09 | 北京四方继保自动化股份有限公司 | A method of realizing that secondary device visualizes plug-in unit |
| CN110704124A (en) * | 2019-09-19 | 2020-01-17 | 国云科技股份有限公司 | Stream data structuralization processing system and method |
| CN110908726A (en) * | 2018-09-14 | 2020-03-24 | 广州神马移动信息科技有限公司 | Data management method, device, equipment and computer readable storage medium |
| CN111596969A (en) * | 2020-05-09 | 2020-08-28 | 中国电子科技集团公司第二十八研究所 | Software architecture method based on microkernel plus plug-in |
| CN111736922A (en) * | 2020-07-23 | 2020-10-02 | 平安国际智慧城市科技股份有限公司 | Plug-in calling method and device, electronic equipment and storage medium |
| CN112068898A (en) * | 2020-09-01 | 2020-12-11 | 上海熙菱信息技术有限公司 | Configurable plug-in type service integration system and method |
| CN112235639A (en) * | 2020-08-31 | 2021-01-15 | 福州智象信息技术有限公司 | Extensible Linux smart television operating system easy to upgrade |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1924800A (en) * | 2005-09-02 | 2007-03-07 | 北京灵图软件技术有限公司 | Control-based insert management system and method for secondary development platform |
-
2012
- 2012-12-11 CN CN201210537056.1A patent/CN103164239B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1924800A (en) * | 2005-09-02 | 2007-03-07 | 北京灵图软件技术有限公司 | Control-based insert management system and method for secondary development platform |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103513990A (en) * | 2013-10-11 | 2014-01-15 | 安徽科大讯飞信息科技股份有限公司 | Method for designing high-performance generally-used network framework for distributed processing |
| CN103513990B (en) * | 2013-10-11 | 2017-01-25 | 科大讯飞股份有限公司 | Method for designing high-performance generally-used network framework for distributed processing |
| WO2015055073A1 (en) * | 2013-10-18 | 2015-04-23 | 北京奇虎科技有限公司 | Method, apparatus and system for reminding message |
| CN103645919A (en) * | 2013-12-18 | 2014-03-19 | 用友软件股份有限公司 | Method for extending functions of management information system through plugins |
| CN103927180A (en) * | 2014-04-21 | 2014-07-16 | 广州市久邦数码科技有限公司 | Implementation method for functional plug-ins based on Android system and system of functional plug-ins based on Android system |
| CN103927180B (en) * | 2014-04-21 | 2017-02-15 | 广州市久邦数码科技有限公司 | Implementation method for functional plug-ins based on Android system and system of functional plug-ins based on Android system |
| CN107203419B (en) * | 2016-03-17 | 2021-03-02 | 阿里巴巴集团控股有限公司 | Method, device and system for calling among modules in application program |
| CN107203419A (en) * | 2016-03-17 | 2017-09-26 | 阿里巴巴集团控股有限公司 | Intermodule call method, apparatus and system in application program |
| CN106873972A (en) * | 2016-12-30 | 2017-06-20 | 中国电力科学研究院 | Electric Power Network Planning emulation platform computing module cut-in method and system based on plug-in unit |
| CN107423101A (en) * | 2017-08-01 | 2017-12-01 | 武大吉奥信息技术有限公司 | A kind of application plug gridding issue and management method and system |
| CN107423101B (en) * | 2017-08-01 | 2020-07-14 | 武大吉奥信息技术有限公司 | Application plug-in gridding release and management method and system |
| CN108446141A (en) * | 2018-02-28 | 2018-08-24 | 武汉智博创享科技股份有限公司 | A kind of web front end plug-in unit and the method for being scheduled and communicating based on web front end plug-in unit |
| CN108628739A (en) * | 2018-03-19 | 2018-10-09 | 北京奇艺世纪科技有限公司 | A kind of method that Lua scripts are debugged, client, server and debugger |
| CN110908726A (en) * | 2018-09-14 | 2020-03-24 | 广州神马移动信息科技有限公司 | Data management method, device, equipment and computer readable storage medium |
| CN110109713A (en) * | 2019-04-18 | 2019-08-09 | 北京四方继保自动化股份有限公司 | A method of realizing that secondary device visualizes plug-in unit |
| CN110109713B (en) * | 2019-04-18 | 2022-06-03 | 北京四方继保自动化股份有限公司 | Method for realizing secondary equipment visual plug-in |
| CN110704124A (en) * | 2019-09-19 | 2020-01-17 | 国云科技股份有限公司 | Stream data structuralization processing system and method |
| CN111596969A (en) * | 2020-05-09 | 2020-08-28 | 中国电子科技集团公司第二十八研究所 | Software architecture method based on microkernel plus plug-in |
| CN111596969B (en) * | 2020-05-09 | 2022-11-25 | 中国电子科技集团公司第二十八研究所 | Software architecture method based on microkernel plus plug-in mode |
| CN111736922B (en) * | 2020-07-23 | 2020-11-13 | 平安国际智慧城市科技股份有限公司 | Plug-in calling method and device, electronic equipment and storage medium |
| CN111736922A (en) * | 2020-07-23 | 2020-10-02 | 平安国际智慧城市科技股份有限公司 | Plug-in calling method and device, electronic equipment and storage medium |
| CN112235639A (en) * | 2020-08-31 | 2021-01-15 | 福州智象信息技术有限公司 | Extensible Linux smart television operating system easy to upgrade |
| CN112235639B (en) * | 2020-08-31 | 2023-04-14 | 北京智象信息技术有限公司 | Extensible Linux smart television operating system easy to upgrade |
| CN112068898A (en) * | 2020-09-01 | 2020-12-11 | 上海熙菱信息技术有限公司 | Configurable plug-in type service integration system and method |
| CN112068898B (en) * | 2020-09-01 | 2024-04-19 | 上海熙菱信息技术有限公司 | Configurable plug-in service integration system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103164239B (en) | 2014-11-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103164239B (en) | Plug-in implement method based on micro network visual platform | |
| CN109117119B (en) | Multi-state assembly fusion method | |
| CN105511911B (en) | The generation method and device of system firmware upgrade package | |
| CN106990952B (en) | Form verification method and system based on Vue | |
| CN102724356B (en) | The information synchronization method and device of access device | |
| CN102541638A (en) | Resource deployment based on conditions | |
| CN110032392A (en) | Service administering method and device, storage medium and electronic equipment | |
| CN102292736A (en) | Collaborative environment project extensibility with composition containers | |
| CN105022630A (en) | Component management system and component management method | |
| CN103177210A (en) | Method of implanting dynamic stain analysis module in Android | |
| CN108958708A (en) | A kind of software system architecture component-based and software implementation method | |
| CN105144085B (en) | For the software frame of storage device | |
| CN102929680A (en) | Method, device and system for converting a testing and test control notation version 3 (TTCN-3) script into a Java source code | |
| CN101221504A (en) | Test script processing method and its scheduling and executing system | |
| CN101980546B (en) | Intelligent network platform, service execution method and method for analyzing service abnormality | |
| CN104317559A (en) | Visual modeling platform based on GMF | |
| CN109240733A (en) | A kind of method and terminal updating advertisement SDK based on Android system | |
| WO2009017550A1 (en) | Programming system for occasionally-connected mobile business applications | |
| Wenger et al. | Transformation of IEC 61131-3 to IEC 61499 based on a model driven development approach | |
| CN103020071B (en) | Method of data synchronization and device | |
| CN102193802A (en) | Method for converting models with model subsets of same base class structure | |
| CN101917509A (en) | Linux-based telephone system under MID platform and implementation method thereof | |
| CN108228266A (en) | Start the method and apparatus of Fragment components under a kind of Android card cages between different plug-in units | |
| CN105243141A (en) | APP resource management method and mobile terminal | |
| CN108170760A (en) | Intelligent hardware manages system and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |