Navigation¶

• METAwiki Main
• METAbolt Main
• METAforums Main
  

• Installation Info.
• Quick Start
• Tips & Tricks
• Known Bugs
  

• Plug-ins/Extensions
• LSL API (commands)
  

• Random Page
• Create a new Page
• Categories
  

• Administration
• File Management
  

• Login/Logout
• Language Selection
• Your Profile
• Create Account
  

Search the wiki
»


All Pages

Tweet Follow @METAbolt

Creating plug-ins and extensions

Table of Contents [Hide/Show] SAMPLE Project Downloads Introduction and Development    Developing a METAbolt plugin (compiled application)    Developing a METAbolt extension (uncompiled class) Developing METAbolt LSL plug-ins

Warning

NOTICE: IF YOU ARE PLANNING TO SELL OR GIVEAWAY (FREE OF CHARGE) YOUR PLUG-INS AND/OR EXTENSIONS YOU UNDERSTAND, ACCEPT AND OBEY THE FOLLOWING: 1. BEING A METABOLT PLUG-IN/EXTENSION DOES NOT AND SHOULD MEAN IN ANY SHAPE OR FORM THAT YOUR PLUGIN IS TPV (THIRD PARTY VIEWER) COMPLIANT AND NEITHER SHOULD IT MEAN THAT THE LINDEN AUTHORISED LISTING OF METABOLT COVERS YOUR PLUG-IN/EXTENSION. IT IS YOUR DUTY TO MAKE SURE YOUR PLUG-IN/EXTENSION MEETS THE REQUIREMENTS OF TPV COMPLIANCE AND THAT IT IS ACCEPTED AND/OR REGISTERED OR WHATEVER THE NECESSARY PROCESS MAY BE IN THIS CASE BY LINDEN LAB 2. YOU WILL NOT USE THE METABOLT NAME TO BRAND OR PROMOTE YOUR DEVELOPMENT IN ANY WAY WHATSOEVER (Using the METAbolt brand) 3. YOU WILL MAKE CLEAR THAT YOUR DEVELOPMENT IS NOT AFFILIATED WITH OR SPONSORED BY METABOLT (www.metabolt.net) AND BE IN FULL COMPLIANCE WITH THE METABOLT BRANDING TERMS & CONDITIONS (Using the METAbolt brand) 4. METABOLT WILL ASSUME NO RESPONSIBILITY AND OFFER ABSOLUTELY NO GUARANTEES UNDER ANY CIRCUMSTANCE FOR ANY TYPE OF DAMAGE AND/OR LOSS IN ANY SHAPE OR FORM, TO YOU (THE DEVELOPER OF THE PLUG-IN AND/OR EXTENSION) OR THE USERS OF YOUR PRODUCT REGARDLESS OF THE OUTCOME AND CAUSE OF DAMAGE AND/OR LOSS. 5. YOU TAKE FULL RESPONSIBILITY OF YOUR DEVELOPMENT AND HOLD METABOLT AND/OR ANY AFFILIATE OF METABOLT HARMLESS OF ANY OUTCOME THROUGH THE USAGE OF YOUR PRODUCT AT ANY TIME AND UNDER ANY CONDITION 6. METABOLT WILL NOT OFFER ANY SUPPORT OR HELP TO THE USERS OF YOUR PRODUCT REGARDING YOUR PRODUCT

SAMPLE Project Downloads¶

Introduction and Development¶

We have designed a very powerful and flexible plug-in/extension architecture that will make development of plug-ins and extensions very easy so that developers can leverage on the features and functions of METAbolt to achieve the goals needed quickly and efficiently without having to require too much knowledge of libOpenMV or even the architecture of a complex system needed to perform tasks in SL and/or OpenGrid based SIMs.

The METAbolt plug-in architecture provides full control and functionality. Via a plug-in/extension you can get the avatar to do anything you like independent of METAbolt.

As a developer you have the option to develop plug-ins and/or extensions (uncompiled classes) as descrbided below...

Developing a METAbolt plugin (compiled application)¶

The plugin you develop can be an EXE or a DLL. An EXE project can have a UI or it can be a console application. Regardless of the type of application you are developing you need to import the "METAbolt" namespace as seen in the sample project download. The METAbolt namespace will give you access to all of the METAbolt and libOpenMV features used by the METAbolt application.

Information

You need to observe the following rules for your solution to work: 1. Your compiled EXE/DLL must be placed in the "Extensions" folder, under the folder which METAbolt is installed. 2. Nothing other than your exe/dll file must be placed in the Extensions folder or METAbolt will throw up an error. All such errors can be observed in the "Debug Logs" menu option under the "Log" menu. If your application needs to have additional files such as settings files, XML or other datafiles etc, such files must be placed elsewhere or in the folder where "METAbolt.exe" is installed.

Developing a METAbolt extension (uncompiled class)¶

You are able to develop an uncompiled class which METAbolt will compile in real time and run it as if it is a part of METAbolt. Classses can be developed in C#, VB or JavaScript and dropped into the "Extensions" folder of METAbolt. The class needs to inherit the METAbolt namespace in order to have access to all of the METAbolt features/functions etc.

	Information
	Guidelines to follow: 1. The class (sample.cs, sample.vb, or sample.js) needs to be placed under the "Extension" folder where METAbolt is installed. 2. No other file must be placed in the Extensions folder. If your class needs to have other files such as text or xml files, such files must be placed elsewhere.

As you can see from the sample application code, the METAxCommon namespace also needs to be inherited. The METAxCommon namspace is the bridge between your plugin/class and METAbolt. You should also notice the "Extension.cs" class which needs to be included in your application/class. You must modify the contents of Extension.cs to suit your requriement i.e. the "title", "description", "author" and "version" so that METAbolt knows what to display under the "Plugins" menu which will appear to the right of the "Utilities" menu option.

Note that METAbolt will not pass a response back when your plug-in has started. The idea behind the METAbolt plugin/extension architecture is that your plugins/extensions can run off the back of METAbolt and do whatever it is designed to do without METAbolt supervising, controlling or restricting it in any way and also you as a developer not having to worry about the plumbing of the underlying technologies. So basically METAbolt provides the platform and what you do and how you do it is your choice as the plugin/extension developer.

Developing METAbolt LSL plug-ins¶

Click here for information and instructions