Plugin Terminology - Revision history

DrO: Reverted edits by StacyPark (Talk) to last version by Culix

2011-10-28T07:51:27Z

Reverted edits by StacyPark (Talk) to last version by Culix

StacyPark at 01:44, 28 October 2011

2011-10-28T01:44:57Z

Culix: Reverted edits by Iseficibuw (Talk) to last version by Culix

2010-11-30T03:28:40Z

Reverted edits by Iseficibuw (Talk) to last version by Culix

Iseficibuw at 05:11, 24 November 2010

2010-11-24T05:11:50Z

Culix: add link to Glossary

2009-07-08T14:33:09Z

add link to Glossary

Culix: +cat :Category:Articles

2009-06-10T14:17:23Z

+cat Category:Articles

Tarik: Protected "Plugin Terminology" [edit=autoconfirmed:move=autoconfirmed]

2008-09-25T13:00:16Z

Protected "Plugin Terminology" [edit=autoconfirmed:move=autoconfirmed]

Benski: New page: == winamp plugin filename conventions == Most plugin types are identified by Winamp by the filename * in_.dll - input plugins out_.dll - output plugins gen_*.dll - general purpose pl...

2008-08-28T17:53:36Z

New page: == winamp plugin filename conventions == Most plugin types are identified by Winamp by the filename * in_*.dll - input plugins * out_*.dll - output plugins * gen_*.dll - general purpose pl...

New page

== winamp plugin filename conventions ==
Most plugin types are identified by Winamp by the filename
* in_*.dll - input plugins
* out_*.dll - output plugins
* gen_*.dll - general purpose plugins
* vis_*.dll - visualizer plugins
* dsp_*.dll - audio effects plugins
* ml_*.dll - media library plugins (loaded by gen_ml.dll)
* pmp_*.dll - portable media player plugins (loaded by ml_pmp.dll... a plugin type loaded by a plugin of a plugin. hah!)
* nsvdec_*.dll - NSV decoder plugins
* enc_*.dll - audio encoder plugins
* W5S (Winamp 5 System) plugins located in c:\program files\winamp\system do not have to follow any special filename convention except for the .w5s file extension
* WAC (Winamp Component) plugins located in c:\program files\winamp\plugins\freeform\wacs do not have to follow any special filename conventions, either, except for the .wac file extension. WAC files are loaded by gen_ff.dll

== code naming conventions ==
* IPC: Inter-Plugin Communications. The constants which define the old SendMessage API are prefixed with IPC_
* Wasabi: Winamp Service Architecture Binary Interface. A system to allow sharing of C++ objects between different plugins and components. Think of it as a very lightweight version of COM.
* Agave: project codename for Winamp 5.12 (when the Wasabi service manager was merged into Winamp 5. It may or may not have involved a lot of tequila). The name "Agave" is used in the SDK to refer to Wasabi components that are unique to Winamp's media platform. For example: the Wasabi Language API could be used in other (non-Winamp) Wasabi applications, but the Agave Playlist Manager makes very little sense outside of a media application.

Wasabi interfaces are all built using the Dispatchable base class. A naming convention has been established to help developers understand the intent of the interface.
* ifc: interface. Wasabi interfaces not associated with the service manager are prefixed with this, e.g. ifc_window
* api: Wasabi interfaces which expose a singleton object meant to be used as a global API. e.g. api_application
* svc: service. Wasabi interfaces which define a service are prefixed with this, e.g. svc_playlisthandler
* obj: object. Wasabi interfaces which define an object created by the service manager are prefixed with this. e.g. obj_xml for an instance of an XML parser.

← Older revision		Revision as of 14:17, 10 June 2009
Line 24:		Line 24:
	* svc: service. Wasabi interfaces which define a service are prefixed with this, e.g. svc_playlisthandler		* svc: service. Wasabi interfaces which define a service are prefixed with this, e.g. svc_playlisthandler
	* obj: object. Wasabi interfaces which define an object created by the service manager are prefixed with this. e.g. obj_xml for an instance of an XML parser.		* obj: object. Wasabi interfaces which define an object created by the service manager are prefixed with this. e.g. obj_xml for an instance of an XML parser.
		+
		+	[[Category:Articles]]

@@ Line 22: / Line 22: @@
 * ifc: interface.  Wasabi interfaces not associated with the service manager are prefixed with this, e.g. ifc_window
 * api: Wasabi interfaces which expose a singleton object meant to be used as a global API.  e.g. api_application
-* svc: service.  Wasabi interfaces which define a service <span class="plainlinks">[https://twitter.com/#!/Jhalek73 <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">jason halek</span>] are prefixed with this, e.g. svc_playlisthandler
+* svc: service.  Wasabi interfaces which define a service are prefixed with this, e.g. svc_playlisthandler
 * obj: object.  Wasabi interfaces which define an object created by the service manager are prefixed with this.  e.g. obj_xml for an instance of an XML parser.

@@ Line 1: / Line 1: @@
 == winamp plugin filename conventions ==
 Most plugin types are identified by Winamp by the filename
@@ Line 18: / Line 17: @@
 * IPC: Inter-Plugin Communications.  The constants which define the old SendMessage API are prefixed with IPC_
 * Wasabi: Winamp Service Architecture Binary Interface.  A system to allow sharing of C++ objects between different plugins and components.  Think of it as a very lightweight version of COM.
-* Agave: project codename for Winamp 5.12 (when the Wasabi service manager was merged into Winamp 5.  It may or may not have involved a lot of tequila).  The name &quot;Agave&quot; is used in the SDK to refer to Wasabi components that are unique to Winamp's media platform.  For example: the Wasabi Language API could be used in other (non-Winamp) Wasabi applications, but the Agave Playlist Manager makes very little sense outside of a media application.
+* Agave: project codename for Winamp 5.12 (when the Wasabi service manager was merged into Winamp 5.  It may or may not have involved a lot of tequila).  The name "Agave" is used in the SDK to refer to Wasabi components that are unique to Winamp's media platform.  For example: the Wasabi Language API could be used in other (non-Winamp) Wasabi applications, but the Agave Playlist Manager makes very little sense outside of a media application.
 Wasabi interfaces are all built using the Dispatchable base class.  A naming convention has been established to help developers understand the intent of the interface.

← Older revision	Revision as of 13:00, 25 September 2008
(No difference)