Plugin Creation - Revision history

LabRPS at 21:57, 19 January 2025

2025-01-19T21:57:23Z

← Older revision		Revision as of 14:57, 19 January 2025
Line 20:		Line 20:
	You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode\|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode\|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, or a .dylib on Mac, or .so on Linux. In order to create this library you need to add a .cpp ({{incode\|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode\|CMakeLists.txt}} to the folder.		You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode\|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode\|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, or a .dylib on Mac, or .so on Linux. In order to create this library you need to add a .cpp ({{incode\|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode\|CMakeLists.txt}} to the folder.

	The ~~plugin~~ directory is a sub-directory of the application ~~installation~~ directory: {{FileName\|<LabRPS ~~Folder~~>/~~Plugins~~/~~WindLabWorkbench~~/}}.		The user Mod directory is a sub-directory of the user application data directory (you can find the latter by typing {{incode\|App.getUserAppDataDir()}} in the [[Python_console\|Python console]]):
			* On Linux it is usually {{FileName\|/home/<username>/.local/share/LabRPS/Mod/}}.
			* On Windows it is {{FileName\|%APPDATA%\LabRPS\Mod\}}, which is usually {{FileName\|C:\Users\<username>\Appdata\Roaming\LabRPS\Mod\}}.
			* On macOS it is usually {{FileName\|/Users/<username>/Library/Application Support/LabRPS/Mod/}}.

	Your plugin folder should look like this on windows:		Your plugin folder should look like this on windows:

	{{Code\|code=		{{Code\|code=
	/~~Plugins~~/		/Mod/
	+-- ~~WindLabWorkbench~~/		+-- WindLabPlugins/
	+-- MyFirstPlugin/		+-- MyFirstPlugin/
	+-- MyFirstPlugin.txt		+-- MyFirstPlugin.txt
	+-- MyFirstPlugin.cpp		+-- MyFirstPlugin.cpp
	+-- CMakeLists.txt		+-- CMakeLists.txt
	}}		}}

Line 137:		Line 140:

	== Adding new feature ==		== Adding new feature ==
	An object that is created for example to add some functionalities to LabRPS for the simulation of random wind velocity is called ~~WindLabFeature~~ which is a class derived from RPSFeature. A WindLabFeature must belong to a feature group and must have a feature type. We can also say that, a feature type of a given feature group is required to create a feature. Multiple features of same feature group and feature type can be created.		An object that is created for example to add some functionalities to LabRPS for the simulation of random wind velocity is called WindLab Feature which is a class derived from RPSFeature. A WindLabFeature must belong to a feature group and must have a feature type. We can also say that, a feature type of a given feature group is required to create a feature. Multiple features of same feature group and feature type can be created.

	{\| class="wikitable sortable"		{\| class="wikitable sortable"
Line 162:		Line 165:
	\|}		\|}

	MyFirstSpectrum and MySecondFeature from the same feature group and type but may have different properties and parameters values. In fact, your plugin adds new feature type. In order to do this, you need to implement the corresponding API interface based on your feature group. Meaning your have to derive a C++ class from an API interface as follows assuming that your feature group is Location Distribution.		MyFirstSpectrum and MySecondFeature are from the same feature group and type but may have different properties and parameters values. In fact, your plugin adds new feature type. In order to do this, you need to implement the corresponding API interface based on your feature group. Meaning your have to derive a C++ class from an API interface as follows assuming that your feature group is Location Distribution.

	{{code\|code=		{{code\|code=

LabRPS at 21:48, 19 January 2025

2025-01-19T21:48:24Z

← Older revision		Revision as of 14:48, 19 January 2025
Line 14:		Line 14:

	In LabRPS, a plugin is a dynamic library that is discovered and loaded at run time as opposed to a dynamic library that an application is linked against at build time. LabRPS Plugins can therefore be written by users, using the well-defined plugin API that LabRPS provides. This allows the users to extend the functionality of the API in designated ways.		In LabRPS, a plugin is a dynamic library that is discovered and loaded at run time as opposed to a dynamic library that an application is linked against at build time. LabRPS Plugins can therefore be written by users, using the well-defined plugin API that LabRPS provides. This allows the users to extend the functionality of the API in designated ways.
	LabRPS plugin system consists of three major features: The [~~[Plugin_API\|~~Plugin API]] which is the API that users must compile and link against in order to create a plugin, the Plugin Manager which is an object (a singleton) in the LabRPS code that manages the life cycle of all plugins, that is, loading, registration, and unloading. This object can also be called the Plugin Registry and finally the [[Std_DlgRPSFeatures\|Feature Manager]] which allows the user to manage, install and uninstall the RPS features contained inside the plugins.		LabRPS plugin system consists of three major features: The [https://api.labrps.com/ Plugin API] which is the API that users must compile and link against in order to create a plugin, the Plugin Manager which is an object (a singleton) in the LabRPS code that manages the life cycle of all plugins, that is, loading, registration, and unloading. This object can also be called the Plugin Registry and finally the [[Std_DlgRPSFeatures\|Feature Manager]] which allows the user to manage, install and uninstall the RPS features contained inside the plugins.

	== The plugin structure, required files, and locations ==		== The plugin structure, required files, and locations ==

	You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode\|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode\|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, or a .dylib on Mac, or .so on Linux. In order to create ~~thise~~ library you need to add a .cpp ({{incode\|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode\|CMakeLists.txt}} to the folder.		You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode\|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode\|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, or a .dylib on Mac, or .so on Linux. In order to create this library you need to add a .cpp ({{incode\|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode\|CMakeLists.txt}} to the folder.

	The ~~user Mod~~ directory is a sub-directory of the ~~user~~ application ~~data~~ directory ~~(you can find the latter by typing {{incode\|App.getUserAppDataDir()}} in the [[Python_console\|Python console]])~~:		The plugin directory is a sub-directory of the application installation directory: {{FileName\|<LabRPS Folder>/Plugins/WindLabWorkbench/}}.
	* On Linux it is usually {{FileName\|~~/home/~~<~~username>/.local/share/LabRPS/Mod/}}.~~
	* On Windows it is {{FileName\|%APPDATA%\LabRPS~~\Mod\}}, which is usually {{FileName\|C:\Users\<username>\Appdata\Roaming\LabRPS\Mod\}}.~~
	* On macOS it is usually {{FileName\|/Users/<username>/~~Library/Application Support/LabRPS~~/~~Mod~~/}}.

	Your plugin folder should look like this on windows:		Your plugin folder should look like this on windows:

	{{Code\|code=		{{Code\|code=
	/~~Mod~~/		/Plugins/
	+-- ~~WindLabPlugins~~/		+-- WindLabWorkbench/
	+-- MyFirstPlugin/		+-- MyFirstPlugin/
	+-- MyFirstPlugin.txt		+-- MyFirstPlugin.txt
	+-- MyFirstPlugin.cpp		+-- MyFirstPlugin.cpp
	+-- CMakeLists.txt		+-- CMakeLists.txt
	}}		}}

Line 140:		Line 137:

	== Adding new feature ==		== Adding new feature ==
	~~There are two main types of object in LabRPS: geometrical representation and 3D visualization object (GeoFeature) and random phenomenon simulation object (RPSFeature).~~ An object that is created for example to add some functionalities to LabRPS for the simulation of random wind velocity is called WindLabFeature which is a class derived from RPSFeature. A WindLabFeature must belong to a feature group and must have a feature type. We can also say that, a feature type of a given feature group is required to create a feature. Multiple features of same feature group and feature type can be created.		An object that is created for example to add some functionalities to LabRPS for the simulation of random wind velocity is called WindLabFeature which is a class derived from RPSFeature. A WindLabFeature must belong to a feature group and must have a feature type. We can also say that, a feature type of a given feature group is required to create a feature. Multiple features of same feature group and feature type can be created.

	{\| class="wikitable sortable"		{\| class="wikitable sortable"

LabRPS: /* LabRPS Plugins */

2024-10-30T01:57:35Z

LabRPS Plugins

← Older revision		Revision as of 18:57, 29 October 2024
Line 14:		Line 14:

	In LabRPS, a plugin is a dynamic library that is discovered and loaded at run time as opposed to a dynamic library that an application is linked against at build time. LabRPS Plugins can therefore be written by users, using the well-defined plugin API that LabRPS provides. This allows the users to extend the functionality of the API in designated ways.		In LabRPS, a plugin is a dynamic library that is discovered and loaded at run time as opposed to a dynamic library that an application is linked against at build time. LabRPS Plugins can therefore be written by users, using the well-defined plugin API that LabRPS provides. This allows the users to extend the functionality of the API in designated ways.
	LabRPS plugin system consists of ~~two~~ major features: The [[Plugin_API\|Plugin API]] which is the API that users must compile and link against in order to create a plugin ~~and~~ the ~~[[PPlugin_Manager\|~~Plugin Manager]] which is an object (a singleton) in the LabRPS code that manages the life cycle of all plugins, that is, loading, registration, and unloading. This object can also be called the Plugin Registry.		LabRPS plugin system consists of three major features: The [[Plugin_API\|Plugin API]] which is the API that users must compile and link against in order to create a plugin, the Plugin Manager which is an object (a singleton) in the LabRPS code that manages the life cycle of all plugins, that is, loading, registration, and unloading. This object can also be called the Plugin Registry and finally the [[Std_DlgRPSFeatures\|Feature Manager]] which allows the user to manage, install and uninstall the RPS features contained inside the plugins.

	== The plugin structure, required files, and locations ==		== The plugin structure, required files, and locations ==

LabRPS at 22:26, 4 August 2024

2024-08-04T22:26:36Z

@@ Line 226: / Line 226: @@
+{
 	return true;
+}

LabRPS at 18:40, 4 August 2024

2024-08-04T18:40:27Z

← Older revision		Revision as of 11:40, 4 August 2024
Line 214:		Line 214:
	for (int loop = 0; loop < Data.numberOfSpatialPosition.getValue(); loop++)		for (int loop = 0; loop < Data.numberOfSpatialPosition.getValue(); loop++)
	{		{
	dLocCoord(loop, 0) = loop + 1;		dLocCoord(loop, 0) = loop + 1;
	dLocCoord(loop, 1) = 5 * loop;		dLocCoord(loop, 1) = 5 * loop;
	dLocCoord(loop, 2) = 0;		dLocCoord(loop, 2) = 0;
	dLocCoord(loop, 3) = 0;		dLocCoord(loop, 3) = 0;

	}		}

LabRPS at 18:26, 4 August 2024

2024-08-04T18:26:23Z

@@ Line 18: / Line 18: @@
 == The plugin structure, required files, and locations ==
-You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, .dylib on Mac, or .so on Linux. In order to create thise library you need to add a .cpp ({{incode|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode|CMakeLists.txt}} to the folder.
+You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, or a .dylib on Mac, or .so on Linux. In order to create thise library you need to add a .cpp ({{incode|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode|CMakeLists.txt}} to the folder.
 The user Mod directory is a sub-directory of the user application data directory (you can find the latter by typing {{incode|App.getUserAppDataDir()}} in the [[Python_console|Python console]]):
@@ Line 59: / Line 59: @@
 }}
 === The MyFirstPlugin.cpp file ===
@@ Line 135: / Line 136: @@
 }}
-You can choose any license you like for your plugin, but be aware that if you wish to see your plugin integrated into and distributed with the LabRPS source code at some point, it needs to be LGPL2+ like the example above. See [[License|License]].
+|}
 {{Docnav

LabRPS at 11:51, 4 August 2024

2024-08-04T11:51:35Z

@@ Line 9: / Line 9: @@
 == Introduction ==
-Plugins are used to extend the functionality of LabRPS. LabRPS has several types of plugins. For example, WindLab plugin, SeismicLab plugin, SeaLab plugin, and many others. LabRPS is already distributed with many different plugins. You can also search various plugins on the [https://labrps.com/search LabRPS official site] or the [https://github.com/LabRPS/LabRPS-addons/blob/master/README.md LabRPS Addons GitHub repository] to see if someone has already created a plugin that suits your needs. If not, this article will guide you through the process of creating your plugin.This page will show you how to add a new plugin to the LabRPS. [[Plugins|Plugins]] are containers for LabRPS features. They can be coded in C++, or in a mix of C++ and Python, which has the advantage to ally the speed of C++ to the flexibility of Python. They can be installed from the [[Std_AddonMgr|Addon Manager]] or installed manually by downloading from some online repository. For now, plugins cannot be developed in Python-only.
+Plugins are used to extend the functionality of LabRPS. LabRPS has several types of plugins. For example, WindLab plugin, SeismicLab plugin, SeaLab plugin, and many others. LabRPS is already distributed with many different plugins. You can also search various plugins on the [https://labrps.com/search LabRPS official site] or the [https://github.com/LabRPS/LabRPS-addons/blob/master/README.md LabRPS Addons GitHub repository] to see if someone has already created a plugin that suits your needs. If not, this article will guide you through the process of creating your plugin. This page will show you how to add a new plugin to LabRPS. [[Plugins|Plugins]] are containers for LabRPS features. They can be coded in C++, or in a mix of C++ and Python, which has the advantage to ally the speed of C++ to the flexibility of Python. They can be installed from the [[Std_AddonMgr|Addon Manager]] or installed manually by downloading from some online repository. For now, plugins cannot be developed in Python-only. If this is your first coding contribution to LabRPS, make sure you download and [[Compiling|compile]] the [https://github.com/LabRPS/LabRPS LabRPS source code] first.
 == The plugin structure, required files, and locations ==
-You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If you plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin.
+You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If your plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin. Until now, the file that represents your plugin have not been created yet. A plugin in LabRPS is a dynamic library such as a .dll file on Windows, .dylib on Mac, or .so on Linux. In order to create thise library you need to add a .cpp ({{incode|MyFirstPlugin.cpp}}) file to your folder. LabRPS uses CMake as its main build system, as it's available on all major operating systems. Compiling with CMake is usually very simple. So, you need to add the {{incode|CMakeLists.txt}} to the folder.
 The user Mod directory is a sub-directory of the user application data directory (you can find the latter by typing {{incode|App.getUserAppDataDir()}} in the [[Python_console|Python console]]):
@@ Line 20: / Line 25: @@
 * On macOS it is usually {{FileName|/Users/<username>/Library/Application Support/LabRPS/Mod/}}.
-Your plugin folder should look like this:
+Your plugin folder should look like this on windows:
 {{Code|code=
@@ Line 27: / Line 32: @@
                     +-- MyFirstPlugin/
                                      +-- MyFirstPlugin.txt
 }}
@@ Line 33: / Line 40: @@
 {{code|code=
 # -*- coding: utf-8 -*-
-# (c) My Name 2024
+# (c) My Name 2080
 __Name__ = "MyFirstPlugin"
@@ Line 48: / Line 55: @@
 __Files__ = "MyFirstPlugin.dll"
 __Date__ = "25-08-2024"
-__Phenomenon__ = "Wind Velcoity"
+__Phenomenon__ = "Wind Velocity"
 __RPSVersion__ = "0.1"
 }}
 You can choose any license you like for your plugin, but be aware that if you wish to see your plugin integrated into and distributed with the LabRPS source code at some point, it needs to be LGPL2+ like the example above. See [[License|License]].

LabRPS: Created page with " {{Docnav |Localisation |Extra Python modules }} {{TOCright}} == Introduction == Plugins are used to extend the functionality of LabRPS. LabRPS has several types of plugins. For example, WindLab plugin, SeismicLab plugin, SeaLab plugin, and many others. LabRPS is already distributed with many different plugins. You can also search various plugins on the [https://labrps.com/search LabRPS official site] or the [https://github.c..."

2024-07-29T21:22:15Z

Created page with " {{Docnav |Localisation |Extra Python modules }} {{TOCright}} == Introduction == Plugins are used to extend the functionality of LabRPS. LabRPS has several types of plugins. For example, WindLab plugin, SeismicLab plugin, SeaLab plugin, and many others. LabRPS is already distributed with many different plugins. You can also search various plugins on the [https://labrps.com/search LabRPS official site] or the [https://github.c..."

New page

{{Docnav
|[[Localisation|Localisation]]
|[[Extra_python_modules|Extra Python modules]]
}}

{{TOCright}}

== Introduction ==

Plugins are used to extend the functionality of LabRPS. LabRPS has several types of plugins. For example, WindLab plugin, SeismicLab plugin, SeaLab plugin, and many others. LabRPS is already distributed with many different plugins. You can also search various plugins on the [https://labrps.com/search LabRPS official site] or the [https://github.com/LabRPS/LabRPS-addons/blob/master/README.md LabRPS Addons GitHub repository] to see if someone has already created a plugin that suits your needs. If not, this article will guide you through the process of creating your plugin.This page will show you how to add a new plugin to the LabRPS. [[Plugins|Plugins]] are containers for LabRPS features. They can be coded in C++, or in a mix of C++ and Python, which has the advantage to ally the speed of C++ to the flexibility of Python. They can be installed from the [[Std_AddonMgr|Addon Manager]] or installed manually by downloading from some online repository. For now, plugins cannot be developed in Python-only.

== The plugin structure, required files, and locations ==

You need a folder, with any name you like, placed in the user Mod directory. it is recommended to give this folder the name of the plugin. The location you place your plugin folder under the Mod directory depends on the type of plugin you are developing. If you plugin is a WindLab plugin, you should put your plugin folder under /Mod/WindLabPlugins. This folder should contain a {{incode|MyFirstPlugin.txt}} text file. This file contains meta-information describing your plugin. Just copy this file from any other existing plugin and modify it for your needs. The {{incode|MyFirstPlugin.txt}} file is executed when LabRPS scans the directory to discover available plugins. That's all it needs for LabRPS to find your plugin.

The user Mod directory is a sub-directory of the user application data directory (you can find the latter by typing {{incode|App.getUserAppDataDir()}} in the [[Python_console|Python console]]):
* On Linux it is usually {{FileName|/home/<username>/.local/share/LabRPS/Mod/}}.
* On Windows it is {{FileName|%APPDATA%\LabRPS\Mod\}}, which is usually {{FileName|C:\Users\<username>\Appdata\Roaming\LabRPS\Mod\}}.
* On macOS it is usually {{FileName|/Users/<username>/Library/Application Support/LabRPS/Mod/}}.

Your plugin folder should look like this:

{{Code|code=
/Mod/
+-- WindLabPlugins/
+-- MyFirstPlugin/
+-- MyFirstPlugin.txt
}}

=== The MyFirstPlugin.txt file ===

{{code|code=
# -*- coding: utf-8 -*-
# (c) My Name 2024

__Name__ = "MyFirstPlugin"
__Comment__ = "This plugin adds great functionalities to LabRPS"
__License__ = "LGPL v 2.1"
__Web__ = ""
__Wiki__ = "https://wiki.labrps.com/Plugin_MyFirst"
__Icon__ = ""
__Help__ = ""
__Author__ = "My Name"
__Version__ = "1.0"
__Status__ = ""
__Requires__ = ""
__Files__ = "MyFirstPlugin.dll"
__Date__ = "25-08-2024"
__Phenomenon__ = "Wind Velcoity"
__RPSVersion__ = "0.1"
}}

You can choose any license you like for your plugin, but be aware that if you wish to see your plugin integrated into and distributed with the LabRPS source code at some point, it needs to be LGPL2+ like the example above. See [[License|License]].

{{Docnav
|[[Localisation|Localisation]]
|[[Extra_python_modules|Extra Python modules]]
}}

{{Powerdocnavi}}
[[Category:Developer Documentation]]
[[Category:Python Code]]