| Revision as of 01:21, 14 February 2009 editTothwolf (talk | contribs)Autopatrolled, Extended confirmed users, File movers, Pending changes reviewers, Rollbackers10,326 edits Added {{IRC footer}} template footer← Previous edit | Latest revision as of 23:41, 25 July 2010 edit undoMiami33139 (talk | contribs)6,175 edits I have merge to article instead of delete content. | ||
| (6 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| #REDIRECT ] | |||
| '''Versus''' is a ] originally developed for the ] ] ], and currently used with ]. It is similar in many ways to the scripting languages used by ] and ], as well as ] and ]. | |||
| The name "Versus" was chosen because it could be shortened to "VS", which was a common abbreviation for ], the language used by Visual IRC '96 through '98. Versus remained mostly ] with ViRCScript, so existing documentation and commentary that mentioned "VS" remained mostly accurate when applied to Versus. The name also alluded to BIRC's origins as a replacement for ViRC. | |||
| '''Object Versus''', or OVS, refers to the ] features of Versus. Scripts can define ] and work with objects and methods instead of textual data and ]; however, in practice, OVS is mostly used to manipulate the ] objects that make up ViRC's interface. | |||
| == Script storage == | |||
| Scripts are stored in files, usually with a .vsc ], though the .lib extension is sometimes used. A Versus script file simply contains ]s to be interpreted when the script is loaded; any blocks defined in a script (see below) will replace blocks defined with the same name by previous scripts. | |||
| == Blocks that can be defined in a script == | |||
| *'''Aliases''' are ]s. They can be called from the command entry line of any window, or from other parts of the script. Aliases that return a value are called functions; an alias can determine whether it's expected to return a value, and then act as a function or a command appropriately. | |||
| *'''Classes''' are used in object-oriented scripting (OVS). Each class may contain ], ]s, a ], and a ]. | |||
| *'''Events''' are used to ] messages from the IRC ], as well as certain system- or client-level occurrences, such as completing a ] or opening a new window. | |||
| **Server events use ]s or Versus's own ]s to match messages from the server. If multiple server events match a particular message, only the one with the highest priority (calculated from the length of the pattern and the relative "value" of the wildcards therein) will be executed. | |||
| **Client events are identified by name: for example, <OnCreateWindow_foo> and <OnCreateWindow_bar> will both run when a new window is opened. They can also include patterns, which limit the particular occurrences that can trigger that event (for example, to only run when a new ''channel'' window is created). | |||
| *'''Menu trees''' and '''menu items''' define the ]s that can appear for various elements of the client's interface, as well as the main menu which is always visible. Menu tree blocks define the menu's layout and set captions for each item; menu item blocks define the script code to be executed when an item is clicked. | |||
| *'''Toolbars''' and '''toolbar items''' are similar to menu tree and menu item blocks, but they define the ]s associated with each window. New toolbars can be added to the interface simply by choosing a unique name. | |||
| Aliases, methods (including constructors and destructors), events, menu items, and toolbar items are referred to as '''routines''' or code blocks. | |||
| == Data storage == | |||
| ===Files=== | |||
| *Scripts can access files with the functions $RandomRead() and $ReadLine(), and the commands CreateFile and AppendText. | |||
| *Scripts can also use the TStringList ] class to read an entire text file into memory, manipulate it, and save it. | |||
| ===Variables=== | |||
| *All variables may contain up to 4 ] of data. | |||
| *Variable names begin with a dollar sign ($) and an uppercase letter, lowercase letter, or underscore. | |||
| *Variables may contain any characters, although they are usually used for printable text. | |||
| *'''Local variables''' are set with the <code>@L</code> command and only exist in the context of the routine that created them. They are deleted when the routine ends. Some local variables are predefined, such as $C for the current channel's name. | |||
| *'''Global variables''' are set with the <code>@</code> command and can be accessed from any routine. They are deleted when the client exits. Aliases may return a value by setting the global variable $fresult. | |||
| *'''Stored variables''' are set with the <code>@S</code> command and, like global variables, can be accessed anywhere. Their values are saved to persistent storage immediately, and restored the next time the client starts. | |||
| ===Associative arrays=== | |||
| *]s map keys to values. | |||
| *Keys and values can contain up to 4 GiB of data with no limits on the allowed characters. | |||
| *Local, global, and stored array values can be set using the <code>@L</code>, <code>@</code>, and <code>@S</code> commands, and they behave just like the corresponding variables. When a stored array value is set, the entire array is saved. | |||
| *The syntax <code>$arrayname</code> is used to set or retrieve the value for a particular key. | |||
| *The syntax <code>$arrayname</code> alone treats an array as a list of key-value pairs, allowing a script to set the entire contents of an array at once, or iterate through the keys that are already present. | |||
| ===Pseudovariables=== | |||
| *Pseudovariables (or pvars) are similar in syntax to variables, but their values cannot be changed. | |||
| *The pvars $0 through $9 contain the parameters that were passed to the current routine, in order. $0 contains the routine's name, $1 contains the first word of the parameter string, and so on. | |||
| *The pvars $0- through $9- contain the parameters that were passed to the current routine, plus all following parameters. $0- contains the routine's name and the entire parameter string, $1- contains all parameters, $2- contains all parameters after the first, and so on. | |||
| *The special sequence <code>$?="PROMPT STRING"</code> causes a dialog box to appear, prompting the user to enter a value. | |||
| == Code examples == | |||
| Here is the ] code example: | |||
| <pre>Alias HELLO | |||
| TextOut > $C clBlack Hello, world! | |||
| EndAlias</pre> | |||
| Here is an example to count to ten: | |||
| <pre>Alias TEN | |||
| for (@l $i = 1; $i <= 10; $i++) | |||
| TextOut > $C clBlack $i | |||
| endfor | |||
| EndAlias</pre> | |||
| Here is an example to make everyone in the current channel an ]: | |||
| <pre>Alias MASSOP | |||
| foreach ($a,$b,$c,$d; $nicklist($C)) | |||
| Mode $C +oooo $a $b $c $d | |||
| endforeach | |||
| EndAlias</pre> | |||
| ==External links== | |||
| * | |||
| {{IRC footer}} | |||
| ] | |||
| ] | |||
Latest revision as of 23:41, 25 July 2010
Redirect to: