Vixen Plugin Development - Revision history

Ravinglunatic at 07:04, 29 January 2011

2011-01-29T07:04:36Z

← Older revision		Revision as of 07:04, 29 January 2011
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.

Line 74:		Line 73:
	[http://www.vixenlights.com/downloads.html Programmer's Guide] (Only for Vixen 1.)		[http://www.vixenlights.com/downloads.html Programmer's Guide] (Only for Vixen 1.)
	[http://www.vixenlights.com/downloads.html Example Source Code] (Only for Vixen 1.)		[http://www.vixenlights.com/downloads.html Example Source Code] (Only for Vixen 1.)


			[[Category:Vixen]]
			[[Category:DIYC Index]]

JonathonReinhart: /* Interface Definition */

2009-12-14T08:04:07Z

Interface Definition

← Older revision		Revision as of 08:04, 14 December 2009
Line 9:		Line 9:
	===Interface Definition===		===Interface Definition===
	IEventDrivenOutputPlugin (Combined into one definition for clarity):		IEventDrivenOutputPlugin (Combined into one definition for clarity):

			''Note:'' The return type for Startup() has changed from Vixen 2.0 to 2.5. See notes below:
	<code>		<code>
	public interface IEventDrivenOutputPlugIn : IOutputPlugIn, IHardwarePlugin, IPlugIn, ISetup		public interface IEventDrivenOutputPlugIn : IOutputPlugIn, IHardwarePlugin, IPlugIn, ISetup

JonathonReinhart at 08:02, 14 December 2009

2009-12-14T08:02:52Z

@@ Line 2: / Line 2: @@
 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.
-==Example Source Code==
+==Vixen 2.0 & 2.5==
 [http://www.vixenlights.com/downloads.html Source code] for the Parallel 12 plugin is available to assist plugin developers.  The plugin is written in C# and works with Vixen 1.*.

Matt at 03:06, 13 August 2008

2008-08-13T03:06:43Z

← Older revision		Revision as of 03:06, 13 August 2008
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.

Agember at 13:44, 12 July 2008

2008-07-12T13:44:52Z

← Older revision		Revision as of 13:44, 12 July 2008
Line 1:		Line 1:
	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.

			==Example Source Code==
			[http://www.vixenlights.com/downloads.html 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 <code>Parallel12</code> class to implement the <code>IEventDrivenOutputPlugIn</code>, <code>IOutputPlugIn</code>, <code>IPlugIn</code> interfaces instead of the <code>PlugIn</code> interface.
			* Change the first parameter of the the <code>Initialize</code> to <code>IExecutable executable</code>. The <code>List<Channels> Channels</code> property of <code>IExecutable</code> can be used in place of the <code>Channel[] channels</code> parameter.
			* In the <code>get</code> method for the <code>HardwareMap</code> property, change the call to <code>new HardwareMap</code> to pass the string constant <code>"Parallel"</code> as its first parameter. The enumeration <code>PortType</code> no longer exists.

	==Resources==		==Resources==
	[http://www.vixenlights.com/~~files/Vixen%20Programmer%27s%20Guide~~.~~zip~~ Programmer's Guide] (Only for Vixen 1.)		[http://www.vixenlights.com/downloads.html Programmer's Guide] (Only for Vixen 1.)
	[http://www.vixenlights.com/~~files/Parallel12~~.~~zip~~ Example Source Code] (Only for Vixen 1.)		[http://www.vixenlights.com/downloads.html Example Source Code] (Only for Vixen 1.)

Agember at 13:29, 12 July 2008

2008-07-12T13:29:44Z

← Older revision		Revision as of 13:29, 12 July 2008
Line 1:		Line 1:
	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.

	==Resources==		==Resources==
	[http://www.vixenlights.com/files/Vixen%20Programmer%27s%20Guide.zip Programmer's Guide] (Only for Vixen 1.)		[http://www.vixenlights.com/files/Vixen%20Programmer%27s%20Guide.zip Programmer's Guide] (Only for Vixen 1.)
	[http://www.vixenlights.com/files/Parallel12.zip Example Source Code] (Only for Vixen 1.)		[http://www.vixenlights.com/files/Parallel12.zip Example Source Code] (Only for Vixen 1.)

Agember: New page: 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. Plu...

2008-07-12T13:28:34Z

New page: 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. Plu...

New page

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.

==Resources==
*[http://www.vixenlights.com/files/Vixen%20Programmer%27s%20Guide.zip Programmer's Guide] (Only for Vixen 1.*)
*[http://www.vixenlights.com/files/Parallel12.zip Example Source Code] (Only for Vixen 1.*)