Vixen Plugin Development: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:Vixen]] | |||
Although [[Vixen]] provides a standard set of [[Vixen_Plugins|plugins]] for a variety of hardware, individuals with different or custom hardware will need to develop their own plugin. Plugin development requires Microsoft Visual Studio, or another development environment for coding and compilation using Microsoft's .NET framework. | Although [[Vixen]] provides a standard set of [[Vixen_Plugins|plugins]] for a variety of hardware, individuals with different or custom hardware will need to develop their own plugin. Plugin development requires Microsoft Visual Studio, or another development environment for coding and compilation using Microsoft's .NET framework. | ||
Revision as of 03:06, 13 August 2008
Although Vixen provides a standard set of plugins for a variety of hardware, individuals with different or custom hardware will need to develop their own plugin. Plugin development requires Microsoft Visual Studio, or another development environment for coding and compilation using Microsoft's .NET framework.
Example Source Code
Source code for the Parallel 12 plugin is available to assist plugin developers. The plugin is written in C# and works with Vixen 1.*.
Modifications are required for the plugin to work with Vixen 2.0:
- Change the
Parallel12class to implement theIEventDrivenOutputPlugIn,IOutputPlugIn,IPlugIninterfaces instead of thePlugIninterface. - Change the first parameter of the the
InitializetoIExecutable executable. TheList<Channels> Channelsproperty ofIExecutablecan be used in place of theChannel[] channelsparameter. - In the
getmethod for theHardwareMapproperty, change the call tonew HardwareMapto pass the string constant"Parallel"as its first parameter. The enumerationPortTypeno longer exists.
Resources
- Programmer's Guide (Only for Vixen 1.*)
- Example Source Code (Only for Vixen 1.*)