In the same folder, we have the library that implements all the plug-in logic. Inside the folder, there is the icon file that must be mandatorily named under the form. This directory stores all the assets and components of the extension. On the above schema, the directory named pluginA is located on the root directory used by pgModeler to load plug-ins. + - (lib)*(pluginA.)(so|dylib|dll) (library) Another rule is that the plug-ins in pgModeler must have a basic directory structure in order to be properly loaded when the application starts: The C++ class that implements the plug-in must follow two basic rules: inherit the class PgModelerPlugin overloading all its pure virtual methods and use the macros Q_INTERFACES and Q_PLUGIN_METADATA in its declaration. In the Qt framework, and consequently, in pgModeler, a plug-in is basically a C++ class implemented in a library installed in a path that is accessible by the application. Once provided with the information you can start to create your own plug-in.
#Compile pgmodeler how to
Steps on how to retrieve the source code of pgModeler can be seen at the download page. Once generated the code documentation is stored in the folder docs under to source code directory.ĭetails about configuring and installing doxygen application can be seen at its official website. You can generate the pgModeler's code documentation by using the doxygen utility running the command doxygen nf at pgModeler's source code root. The first step in the development of a plug-in that handles pgModeler objects is to take a good reading on pgModeler's API as well as to the Qt plug-in system. So, pgModeler has a simple structure to provide a form to create third-party plug-ins. Plug-ins are the best way to add a specific set of features to the software without making changes to its core code.
0 kommentar(er)
