CN103164239B - 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
- CN103164239B CN103164239B CN201210537056.1A CN201210537056A CN103164239B CN 103164239 B CN103164239 B CN 103164239B CN 201210537056 A CN201210537056 A CN 201210537056A CN 103164239 B CN103164239 B CN 103164239B
- 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.)
- Active
Links
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 technical field that the present invention relates to the microgrid Visualization Platform application of electric system, particularly relates to a kind of plug-in unit implementation method based on 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) to recompilate and issue.The function of software is decided by framing program and plug-in unit.Between framing program and plug-in unit, have a specific interface, both must transmit data or control information by this interface for they, to realize software function.
Current plug-in unit mostly is single environment operation, does not provide operating system cross-platform support.Meanwhile, plug-in unit mostly is customized development, 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 mistake, easily appears in development complexity.
Summary of the invention
For the problem existing in above-mentioned background technology, the object of the present invention is to provide a kind of plug-in unit implementation method based on microgrid Visualization Platform, can make plug-in unit that cross-platform support is provided, improve the reusability of program.
A plug-in unit implementation method based on microgrid Visualization Platform, comprises the following steps:
Application program loading of plug-in manager, 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 corresponding plug-in unit;
The plug-in unit that receives described loading messages completes registration in described plugin manager;
Described plugin manager is to the interface class of plug-in unit described in registered plug-in unit acquisition request, and loads described interface class; The component class register list of plug-in unit described in acquisition request, and in described plugin manager, register corresponding component class according to described component class register list;
Load events manager;
Described in each, plug-in unit receives the initial message that described plugin manager sends, and registers corresponding event and response function to described task manager;
In the time that described event is triggered, be directly subject to event driven plug-in unit to send data and notification message to described task manager;
Described task manager is according to described notification message, sends data to registered each plug-in unit, and described in each, plug-in unit receives and carries out corresponding response function after described data and process.
In plug-in unit implementation method based on microgrid Visualization Platform of the present invention, by described plugin manager, each plug-in unit is managed, in the time of 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, multiple plug-in unit loads, the loading of traversal plug-in unit catalogue.And each plug-in unit completes after registration in described plugin manager, described plugin manager is first recorded the interface class of described plug-in unit, reload the component class of described plug-in unit, between each plug-in unit, can complete the interactive function between plug-in unit by described interface class, can be by 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 master program file when releasing software, formed by multiple static library modules in inside, can bring into play so the reusable advantage of plug-in unit, can reduce again program file quantity, can make plug-in unit that cross-platform support is provided, improve the reusability of program.
Brief description of the 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 event driven process flow diagram in the plug-in unit implementation method based on microgrid Visualization Platform of the present invention;
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
Refer to 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.
The described plug-in unit implementation method based on microgrid Visualization Platform, comprises the following steps:
S101, application program loading of plug-in manager, 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 corresponding plug-in unit;
S103, the plug-in unit that receives described loading messages completes registration in described plugin manager;
S104, described plugin manager is to the interface class of plug-in unit described in registered plug-in unit acquisition request, and loads described interface class; The component class register list of plug-in unit described in acquisition request, and in described plugin manager, register corresponding component class according to described component class register list.
The coupling of program frame of the present invention and plug-in unit and realized between each plug-in unit simultaneously, mutually calling between platform and plug-in unit, thereby improve 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 the problem of the coupling that solves microgrid Visualization Platform and each different sub-systems plug-in unit.
Wherein, for step S101, by described plugin manager, the interface function pointer of associated component class ID and component class establishment is managed.Preferably use the intelligent pointer class boost::share_ptr in Boost function library to carry out maintenance management to the life cycle of function.Plug-in unit life cycle comprises the loading (structure) of plug-in unit when program starts, the release of calling plug-in unit while exiting with program (analysing structure) of program plug-in unit in service.In step S101, whether program first verification plug-in management class (PluginManager) loads, if do not loaded, loads described plug-in management class, and obtains such pointer, if loaded, directly gets such pointer.
The mode of described plug-in management class loading of plug-in has multiple, comprises that multiple plug-in units simply load, a plug-in unit simply loads, travels through plug-in unit loading, static library plug-in unit under catalogue and loads 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 corresponding plug-in unit;
Each plug-in unit that receives described loading messages, after receiving described loading messages, sends confirmation to described plugin manager.
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 Interface realization plug-in unit, between platform and plug-in unit.
Preferably, the interface class of described plug-in unit is made up of pure virtual function, and has a constant name being defined by GUID character string as component class ID.
That is when 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, is all made up of pure virtual function.Directly use a constant name of GUID character string definition simultaneously, need to use component class ID time, use this constant name, 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 defining in component class, and the constructed fuction of described component class is protection type.
That is while 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 defining in component class.For the constructed fuction of class being made as to protection type for component programming.A component class can be realized multiple interfaces, and component class can be inherited.
Described plugin manager loads described interface class and corresponding component class, completes plug-in unit is loaded.
Preferably, after the loading that completes 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.
In the time that system is received closing application program message, described plugin manager sends and discharges plug-in unit message to each plug-in unit according to plug-in unit loading sequence backward, each plug-in unit is received releasing memory after described release plug-in unit message, returns to release success message to described plugin manager.Receive all backward platform return messages that return success message when plugin manager, system can be closed.
In the present invention " message " realized platform to a plug-in unit, platform to multiple 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 to proposition " event (Event) ", the function of realizing multiple plug-in units adjusts back to realize a plug-in unit to the calling of multiple plug-in units, and introduces event-based model below:
First: event driven principle.
Definition event type is mainly to define unique character string to distinguish different events, in compilation phase identification format error, has automatically defined internal type simultaneously.Registration response function is that the response function of multiple same format (call back function) is recorded, and is associated with an event type character string simultaneously.Trigger event is exactly to find corresponding response function according to event type character string, calls successively these response functions (synchronization call mode) by registration sequencing, event argument is passed to the parameter of response function.The present invention realizes by Signal2, Function in Boost storehouse and the combination of Bind class libraries.
Second: definition event type.
The multiple event types of definable in a header file, for example:
#include<Triggerevent.h>
//void?login(string?strUser)
DEFINE_EVENT_1(EventLogin,string,"login.plg")；
//void?login(string?strUser,string?strPwd)
DEFINE_EVENT_2(EventLoginEx,string,string,"login.plg")；
//bool?login(string?strUser)
DEFINE_EVENT_1Break(EventLoginDemo,string,"login.plg")；
In this file, first comprise Triggerevent.h, then use each event type of the macro definitions 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);
Event title, by the assisted class (class name starts with Trigger) for defining an inner structure body and Event triggered, will be used this event title in the time of triggering and response events; 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 (for example string &, const MyObj &); Event name identification suffix is for avoiding disparate modules to occur identical event title, and inside is combined to form a unduplicated character string constant, for example " EventAdd.login.plg ", " EventAdd.login.plg " by event title and mark suffix.
The the 3rd: registration response function.
Respond simple event type by static function, the rreturn value type of function must be consistent with the definition of event type with 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){...}
In the InitializePlugin () function of response function place module or other functions, register these response functions to corresponding event type.Use the grand registration response function of REGISTER_OBSERVER, for example:
At the entrance function CPP of response function place module file (module.cpp or main.cpp, comprise pluginimpl.h or realized class createObject function) in, need to comprise observerimpl.h file, in this module, can only in a CPP file, comprise observerimpl.h file: #include<observerimpl.h>.
Therefore, the plug-in unit implementation method based on microgrid Visualization Platform of the present invention, can be further comprising the steps after completing plug-in unit loading, as shown in Figure 2:
S201, load events manager;
S202, described in each, plug-in unit receives the initial message that described plugin manager sends, and registers corresponding event and response function to described task manager;
S203, in the time that described event is triggered, is directly subject to event driven plug-in unit to send data and notification message to described task manager;
S204, described task manager is according to described notification message, sends data to registered each plug-in unit, and described in each, plug-in unit receives and carries out corresponding response function after described data and process.
Plug-in unit implementation method based on 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, plug-in unit load mode comprises that multiple plug-in units simply load, a plug-in unit simply loads, travels through plug-in unit loading, static library plug-in unit under catalogue and loads 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 interface (UI) such as menu (Menu), tool bar (ToolBar) alternately and inter-module funcall by above-mentioned functions.Safeguard component lifecycle by intelligent pointer (SharePtr), ensure 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 being made up of pure virtual function, does not need special base class; The various typess of variables that can use C++ simultaneously, are not subject to the such constraint of com interface.
2) interface is realized and being separated with the plug-in unit based on microgrid Visualization Platform, interface header file is provided to outside, and can realizes one or more interfaces by an assembly in inside, does not need externally to derive such or expose to realize details.Can allow multiple module concurrent developments, module not exist each other compiling to rely on (file such as LIB that does not need other plug-in units).
3) adopting Boost intelligent pointer to carry out the life cycle of maintenance interface, can be another interface from an interface dynamic translation, can distinguish and 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 to class and merge or split, it is distributed in different plug-in units, and 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 microgrid Visualization Platform has been realized identical interface, even if built-in function is not identical.So just realize plug-in unit function replaceable, that combine 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 and reuse and expand.
Below with the concrete process description plug-in unit implementation method based on microgrid Visualization Platform of the present invention:
Refer to 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;
First application A pplication request loading of plug-in manager LoadPlugInManager, after having loaded, send the message LoadPlugIns of loading of plug-in.Described plugin manager PlugInManager sends loading messages LoadPlugaccording to described load request to corresponding A plug-in unit and B plug-in unit; A plug-in unit responds described loading messages and returns to acknowledge message LoadPlugInEx, described plugin manager completes registration RegisterPlugIn to A plug-in unit, the interface class GetModuleInterface of plug-in unit described in acquisition request, and load described interface class AddModule; Component class register list RegisterClassEntryTable, the GetClassEntryTable of plug-in unit described in acquisition request, and in described plugin manager, register corresponding component class RegisterClass according to described component class register list.Complete after 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 C plug-in unit is for being directly subject to event driven plug-in unit, and A plug-in unit and B plug-in unit are the plug-in unit that is subject to C plug-in unit readjustment.After A plug-in unit and B plug-in unit are received described initial message InitPlugIn, register corresponding event and response function RegisterObserver to task manager ChangeManager;
In the time of trigger event, be directly subject 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, described A plug-in unit and B plug-in unit receive to be carried out corresponding response function after described data and processes, and responds described event OnEnventX ().
One of ordinary skill in the art will appreciate that all or part of flow process realizing in above-mentioned embodiment, can carry out the hardware that instruction is relevant by computer program to complete, described program can be stored in a computer read/write memory medium, this program, in the time carrying out, can comprise the flow process as the respective embodiments described above.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.It 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 (7)
1. the plug-in unit implementation method based on microgrid Visualization Platform, is characterized in that, comprises the following steps:
Application program loading of plug-in manager, 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 corresponding plug-in unit;
The plug-in unit that receives described loading messages completes registration in described plugin manager;
Described plugin manager is to the interface class of plug-in unit described in registered plug-in unit acquisition request, and loads described interface class; The component class register list of plug-in unit described in acquisition request, and in described plugin manager, register corresponding component class according to described component class register list;
Load events manager;
Described in each, plug-in unit receives the initial message that described plugin manager sends, and registers corresponding event and response function to described task manager;
In the time that described event is triggered, be directly subject to event driven plug-in unit to send data and notification message to described task manager;
Described task manager is according to described notification message, sends data to registered each plug-in unit, and described in each, plug-in unit receives and carries out corresponding response function after described data and process.
2. the plug-in unit implementation method based on microgrid Visualization Platform as claimed in claim 1, is characterized in that, the interface class of described plug-in unit is made up of pure virtual function, and has a constant name being defined by GUID character string as component class ID.
3. the plug-in unit implementation method based on 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, realizes the interface function defining in component class, and the constructed fuction of described component class is protection type.
4. the plug-in unit implementation method based on 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 inspection plug-in management class loads, if do not loaded, loads described plug-in management class and obtains the pointer of described plug-in management class, if loaded, directly obtains described pointer.
5. the plug-in unit implementation method based on microgrid Visualization Platform as claimed in claim 1, is characterized in that, the mode of described plugin manager loading of plug-in comprises that multiple plug-in units load, single plug-in unit loads; Under 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 microgrid Visualization Platform as claimed in claim 1, is characterized in that, registers corresponding component class and further comprise 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 microgrid Visualization Platform as claimed in claim 6, it is characterized in that, in the time receiving closing application program message, described plugin manager sends and discharges plug-in unit message to each plug-in unit according to plug-in unit loading sequence backward, each plug-in unit is received releasing memory after described release plug-in unit message, return to release success message to described plugin manager, described plugin manager receives that the backward platform of described release success message returns to this message.
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 CN103164239A (en) | 2013-06-19 |
| CN103164239B true 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) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103513990B (en) * | 2013-10-11 | 2017-01-25 | 科大讯飞股份有限公司 | Method for designing high-performance generally-used network framework for distributed processing |
| CN103516595B (en) * | 2013-10-18 | 2016-11-09 | 北京奇虎科技有限公司 | The method and apparatus of a kind of prompting message and system |
| CN103645919A (en) * | 2013-12-18 | 2014-03-19 | 用友软件股份有限公司 | Method for extending functions of management information system through plugins |
| 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 |
| 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 |
| CN107423101B (en) * | 2017-08-01 | 2020-07-14 | 武大吉奥信息技术有限公司 | Application plug-in gridding release and management method and system |
| CN108446141B (en) * | 2018-02-28 | 2021-01-12 | 武汉智博创享科技股份有限公司 | Web front-end plug-in and method for scheduling and communicating based on same |
| 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 |
| 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 |
| 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 |
| CN112235639B (en) * | 2020-08-31 | 2023-04-14 | 北京智象信息技术有限公司 | Extensible Linux smart television operating system easy to upgrade |
| CN112068898B (en) * | 2020-09-01 | 2024-04-19 | 上海熙菱信息技术有限公司 | Configurable plug-in service integration system and method |
| CN114296718A (en) * | 2021-12-28 | 2022-04-08 | 珠海豹趣科技有限公司 | Setting method and device of Windows system component |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100593156C (en) * | 2005-09-02 | 2010-03-03 | 北京灵图软件技术有限公司 | Control-based insert management system and method for secondary development platform |
-
2012
- 2012-12-11 CN CN201210537056.1A patent/CN103164239B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN103164239A (en) | 2013-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103164239B (en) | Plug-in implement method based on micro network visual platform | |
| CN105511911B (en) | The generation method and device of system firmware upgrade package | |
| CN101901150B (en) | Universal distributed airborne equipment health management simulation platform and implementation method thereof | |
| CN102724356B (en) | The information synchronization method and device of access device | |
| CN110032392A (en) | Service administering method and device, storage medium and electronic equipment | |
| CN108958708A (en) | A kind of software system architecture component-based and software implementation method | |
| CN106484464B (en) | Tuner chip driving method and electronic equipment | |
| CN101221504A (en) | Test script processing method and its scheduling and executing system | |
| CN108984161A (en) | The software installation packet construction method and device of a kind of unification and the expansion that can classify | |
| Butzin et al. | A model based development approach for building automation systems | |
| US20140304716A1 (en) | Software framework for a storage device | |
| Cetina et al. | Using feature models for developing self-configuring smart homes | |
| Wenger et al. | Transformation of IEC 61131-3 to IEC 61499 based on a model driven development approach | |
| Henrio et al. | Verifying the correct composition of distributed components: Formalisation and Tool | |
| CN108228266A (en) | Start the method and apparatus of Fragment components under a kind of Android card cages between different plug-in units | |
| CN109542447A (en) | A kind of OTX program file execution method and device | |
| CN115776501A (en) | Block chain system architecture, management method, electronic equipment and readable storage medium | |
| CN108170760A (en) | Intelligent hardware manages system and equipment | |
| Vepsäläinen et al. | Tool support for the UML automation profile-for domain-specific software development in manufacturing | |
| CN109086048A (en) | Multiple modules individually issue the implementation method of AAR under a kind of Android client project | |
| Kaegi et al. | Modular java web applications | |
| CN106778301A (en) | Reliable cross-platform data storage method and system based on cocos2d x | |
| Tronel et al. | Compositional verification using CADP of the ScalAgent deployment protocol for software components | |
| CN102202017A (en) | Support platform for digital media interactive service intelligent gateway | |
| CN108491193A (en) | Eclipse RCP products construction method, device, terminal and medium |
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 |