aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md449
1 files changed, 392 insertions, 57 deletions
diff --git a/README.md b/README.md
index b2bcad9..328bfe1 100644
--- a/README.md
+++ b/README.md
@@ -6,17 +6,116 @@ IRC::Client - Extendable Internet Relay Chat client
# SYNOPSIS
+## Client script
+
```perl6
use IRC::Client;
use IRC::Client::Plugin::Debugger;
IRC::Client.new(
- :host('localhost'),
- :debug,
- plugins => [ IRC::Client::Plugin::Debugger.new ]
+ :host<localhost>
+ :channels<#perl6bot #zofbot>
+ :debug
+ :plugins( IRC::Client::Plugin::Debugger.new )
).run;
```
+## Custom plugins
+
+### Basic response to an IRC command:
+
+The plugin chain handling the message will stop after this plugin.
+
+```perl6
+unit class IRC::Client::Plugin::PingPong is IRC::Client::Plugin;
+method irc-ping ($irc, $msg) { $irc.ssay("PONG {$irc.nick} $msg<params>[0]") }
+```
+
+### More involved handling
+
+On startup, start sending message `I'm an annoying bot` to all channels
+every five seconds. We also subscribe to all events and print some debugging
+info. By returning a special constant, we tell other plugins to continue
+processing the data.
+
+```perl6
+use IRC::Client::Plugin; # import constants
+unit class IRC::Client::Plugin::Debugger is IRC::Client::Plugin;
+
+method register($irc) {
+ Supply.interval( 5, 5 ).tap({
+ $irc.privmsg($_, "I'm an annoying bot!")
+ for $irc.channels;
+ })
+}
+
+method all-events ($irc, $e) {
+ say "We've got a private message"
+ if $e<command> eq 'PRIVMSG' and $e<params>[0] eq $irc.nick;
+
+ # Store arbitrary data in the `pipe` for other plugins to use
+ $e<pipe><respond-to-notice> = True
+ if $e<command> eq 'PRIVMSG';
+
+ say $e, :indent(4);
+ return IRC_NOT_HANDLED;
+}
+
+```
+
+# TABLE OF CONTENTS
+- [NAME](#name)
+- [SYNOPSIS](#synopsis)
+ - [Client script](#client-script)
+ - [Custom plugins](#custom-plugins)
+ - [Basic response to an IRC command:](#basic-response-to-an-irc-command)
+ - [More involved handling](#more-involved-handling)
+- [TABLE OF CONTENTS](#table-of-contents)
+- [DESCRIPTION](#description)
+- [BLEED BRANCH](#bleed-branch)
+- [METHODS](#methods)
+ - [`new`](#new)
+ - [`debug`](#debug)
+ - [`host`](#host)
+ - [`port`](#port)
+ - [`nick`](#nick)
+ - [`username`](#username)
+ - [`userhost`](#userhost)
+ - [`userreal`](#userreal)
+ - [`channels`](#channels)
+ - [`plugins`](#plugins)
+ - [`plugins-essential`](#plugins-essential)
+ - [`run`](#run)
+- [METHODS FOR PLUGINS](#methods-for-plugins)
+ - [`.ssay`](#ssay)
+ - [`.privmsg`](#privmsg)
+- [INCLUDED PLUGINS](#included-plugins)
+ - [IRC::Client::Plugin::Debugger](#ircclientplugindebugger)
+ - [IRC::Client::Plugin::PingPong](#ircclientpluginpingpong)
+- [EXTENDING IRC::Client / WRITING YOUR OWN PLUGINS](#extending-ircclient--writing-your-own-plugins)
+ - [Overview of the plugin system](#overview-of-the-plugin-system)
+ - [Return value constants](#return-value-constants)
+ - [`IRC_HANDLED`](#irc_handled)
+ - [`IRC_NOT_HANDLED`](#irc_not_handled)
+ - [Subscribing to IRC events](#subscribing-to-irc-events)
+ - [Standard IRC commands](#standard-irc-commands)
+ - [Special Events](#special-events)
+ - [`irc-start-up`](#irc-start-up)
+ - [`irc-connected`](#irc-connected)
+ - [`irc-all-events`](#irc-all-events)
+ - [`irc-privmsg-me`](#irc-privmsg-me)
+ - [`irc-notice-me`](#irc-notice-me)
+ - [`irc-unhandled`](#irc-unhandled)
+ - [Contents of the parsed IRC message](#contents-of-the-parsed-irc-message)
+ - [`command`](#command)
+ - [`params`](#params)
+ - [`pipe`](#pipe)
+ - [`who`](#who)
+- [REPOSITORY](#repository)
+- [BUGS](#bugs)
+- [AUTHOR](#author)
+- [LICENSE](#license)
+
# DESCRIPTION
***Note: this is a preview dev release. Things might change and new things
@@ -28,6 +127,13 @@ This modules lets you create
in Perl 6. The plugin system lets you work on the behaviour, without worrying
about IRC layer.
+# BLEED BRANCH
+
+The master branch of this repository contains the latest working version
+of the module. To get the bleeding-edge version, you can install from the
+[bleed branch](https://github.com/zoffixznet/perl6-IRC-Client/tree/bleed), but
+that code is not always guaranteed to be in working order.
+
# METHODS
## `new`
@@ -142,94 +248,323 @@ working order of any IRC client. **Defaults to:**
Takes no arguments. Starts the IRC client. Exits when the connection
to the IRC server ends.
-# PLUGINS
+# METHODS FOR PLUGINS
+
+You can make use of these `IRC::Client` methods in your plugins:
+
+## `.ssay`
+
+```perl6
+ $irc.ssay("Foo bar!");
+```
+Sends a message to the server, automatically appending `\r\n`. Mnemonic:
+**s**erver **say**.
+
+
+## `.privmsg`
+
+```perl6
+ $irc.privmsg( 'Zoffix', 'Hallo!' );
+```
+Sends a `PRIVMSG` message specified in the second argument
+to the user/channel specified as the first argument.
+
+# INCLUDED PLUGINS
Currently, this distribution comes with two IRC Client plugins:
-## Writing your own
+## IRC::Client::Plugin::Debugger
```perl6
- unit class IRC::Client::Plugin::Foo:ver<1.001001>;
+ use IRC::Client;
+ use IRC::Client::Plugin::Debugger;
- multi method msg () { True }
- multi method msg ($irc, $msg) {
- $irc.privmsg( Zoffix => Dump $msg, :indent(4) );
- }
+ IRC::Client.new(
+ :host('localhost'),
+ :debug,
+ plugins => [ IRC::Client::Plugin::Debugger.new ]
+ ).run;
+```
- multi method interval () { 6 }
- multi method interval ($irc) {
- $irc.privmsg(
- $irc.channels[0], "5 seconds passed. Time is now " ~ now
- );
- }
+When run, it will pretty-print all of the events received by the client. It
+does not stop plugin processing loop after handling a message.
+
+## IRC::Client::Plugin::PingPong
+
+```perl6
+ use IRC::Client;
+ IRC::Client.new.run; # automatically included in plugins-essential
```
-Above is a sample plugin. You can choose to respond either to server
-messages or do things at a specific interval.
+This plugin makes IRC::Client respond to server's C<PING> messages and is
+included in the [`plugins-essential`](#plugins-essential) by default.
+
+# EXTENDING IRC::Client / WRITING YOUR OWN PLUGINS
+
+## Overview of the plugin system
+
+The core IRC::Client receives and parses IRC protocol messages from the
+server that it then passes through a plugin chain. The plugins declared in
+[`plugins-essential`](#plugins-essential) are executed first, followed by
+plugins in [`plugins`](#plugins). The order is the same as the order specified
+in those two lists.
-### Responding to server messages
+A plugin can return a [special constant](#return-value-constants) that
+indicates it handled the message and the plugin chain processing should stop.
+
+To subscribe to handle a particular IRC command, a plugin simply declares a
+method `irc-COMMAND`, where `COMMAND` is the name of the IRC command the
+plugin wishes to handle. There are also a couple of
+[special events](#special-events) the plugin can subscribe to, such as
+intialization during start up or when the client receives a private message
+or notice.
+
+## Return value constants
```perl6
- multi method msg () { True }
- multi method msg ($irc, $msg) {
- $irc.privmsg( Zoffix => Dump $msg, :indent(4) );
- }
+ use IRC::Client::Plugin;
+ unit class IRC::Client::Plugin::Foo is IRC::Client::Plugin;
+ ...
```
-If your plugin can resond to server messages, declare two multi methods
-`msg` as seen above. The one without parameters needs to return `True`
-(or `False`, if your plugin does not respond to messages). The second
-gets the `IRC::Client` object as the first argument and the parsed message
-as the second argument.
+To make the constants available in your class, simply `use` IRC::Client::Plugin
+class.
-### Acting in intervals
+### `IRC_HANDLED`
```perl6
- multi method interval () { 6 }
- multi method interval ($irc) {
- $irc.privmsg(
- $irc.channels[0], "5 seconds passed. Time is now " ~ now
- );
- }
+ # Returned by default
+ method irc-ping ($irc, $e) { $irc.ssay("PONG {$irc.nick} $e<params>[0]") }
+
+ # Explicit return
+ method irc-privmsg ($irc, $e) { return IRC_HANDLED; }
```
-Your plugin can also repsond in intervals. Declare an `interval` multi
-that takes no arguments and returns an interval in seconds that your
-action should happen in (return `0` if your plugin does not handle intervals).
-The other multi method `interval` takes the `IRC::Client` as the argument.
+Specifies that plugin handled the message and the plugin chain processing
+should stop immediatelly. Plugins later in the chain won't know this
+message ever came. Unless you explicitly return
+[`IRC_NOT_HANDLED`](#irc_not_handled) constant, IRC::Client will assume
+`IRC_HANDLED` was returned.
-## Methods for plugins
+### `IRC_NOT_HANDLED`
-You can make use of these `IRC::Client` methods in your plugins:
+```perl6
+ return IRC_NOT_HANDLED;
+```
+Returning this constant indicates to IRC::Client that your plugin did
+not "handle" the message and it should be propagated further down the
+plugin chain for other plugins to handle.
+
+## Subscribing to IRC events
-### `.ssay`
+### Standard IRC commands
```perl6
- $irc.ssay("Foo bar!");
+ method irc-privmsg ($irc, $e) { ... }
+ method irc-notice ($irc, $e) { ... }
+ method irc-353 ($irc, $e) { ... }
```
-Sends a message to the server, automatically appending `\r\n`.
+To subscribe to an IRC event, simply declare a method named `irc-command`,
+where `command` is the IRC command you want to handle, in **lower case**.
+The method takes two positional arguments: an `IRC::Client` object and
+the [parsed IRC message](#contents-of-the-parsed-irc-message).
+
+You'll likely generate a response based on the content of the parsed message
+and use one of the [METHODS FOR PLUGINS](#methods-for-plugins) to send that
+response.
-### `.privmsg`
+## Special Events
```perl6
- $irc.privmsg( Zoffix => "Hallo!" );
+ method irc-start-up ($irc) { ... } # once per client run
+ method irc-connected ($irc) { ... } # once per server connection
+
+ method irc-all-events ($irc, $e) { ... }
+ method irc-privmsg-me ($irc, $e) { ... }
+ method irc-notice-me ($irc, $e) { ... }
+ ... # all other handlers for standard IRC commands
+ method irc-unhandled ($irc, $e) { ... }
```
-Sends a `PRIVMSG` message specified in the second argument
-to the user/channel specified as the first argument.
+In addition to the [standard IRC commands](#standard-irc-commands), you can
+register several special cases. They're handled in the event chain in the order
+shown above (except for [`irc-start-up`](#irc-start-up) and
+[`irc-connected`](#irc-connected) that do not offect command-triggered events).
+That is, if a plugin returns [`IRC_HANDLED`](#irc_handled) after
+processing, say, [`irc-all-events`](#irc-all-events) event, its
+[`irc-notice-me`](#irc-notice-me) handler won't be triggered, even if it would
+otherwise.
-## Included Plugins
+The available special events are as follows:
-### `IRC::Client::Plugin::Debugger`
+### `irc-start-up`
- plugins => [IRC::Client::Plugin::Debugger.new]
+```perl6
+ method irc-start-up ($irc) { ... }
+```
+Passed IRC::Client object as the only argument. Triggered right when the
+IRC::Client is [`.run`](#run), which means most of
+[METHODS FOR PLUGINS](#methods-for-plugins) **cannot** be used, as no connection
+has been made yet. This event will be issued only once per [`.run`](#run)
+and the method's return value is discarded.
-Including this plugin will pretty-print parsed IRC messages on STDOUT.
+### `irc-connected`
+
+```perl6
+ method irc-connected ($irc) { ... }
+```
+Passed IRC::Client object as the only argument. Triggered right when we
+get a connection to the server, identify with it and issue `JOIN` commands
+to enter the channels. Note that at this point it is not guaranteed that the
+client is already in all the channels it's meant to join.
+This event will be issued only once per connection to the server
+and the method's return value is discarded.
-### `IRC::Client::Plugin::PingPong`
+### `irc-all-events`
- plugins-essential => [IRC::Client::Plugin::PingPong.new]
+```perl6
+ method irc-all-events ($irc, $e) { ... }
+```
+Triggered for all IRC commands received, regardless of their content. As this
+method will be triggered before any others, you can use this to
+pre-process the message, for example. ***WARNING:*** **since
+[`IRC_HANDLED` constant](#irc_handled) is returned by default, if you do not
+explicitly return [`IRC_NOT_HANDLED`](#irc_not_handled), your client will
+stop handling ALL other messages
+***
+
+### `irc-privmsg-me`
+
+```perl6
+ method irc-privmsg-me ($irc, $e) { ... }
+```
+Triggered when the IRC `PRIVMSG` command is received, where the recipient
+is the client (as opposed to some channel).
+
+### `irc-notice-me`
+
+```perl6
+ method irc-notice-me ($irc, $e) { ... }
+```
+Triggered when the IRC `NOTICE` command is received, where the recipient
+is the client (as opposed to some channel).
+
+### `irc-unhandled`
+
+```perl6
+ method irc-unhandled ($irc, $e) { ... }
+```
-This plugin responds to server's `PING` requests and is automatically
-included in the `plugins-essential` by default.
+This is the same as [`irc-all-events`](#irc-all-events), except it's triggered
+**after** all other events were tried. This method can be used to catch
+any unhandled events.
+
+## Contents of the parsed IRC message
+
+```perl6
+ # method irc-366 ($irc, $e) { ... }
+ {
+ command => "366".Str,
+ params => [
+ "Perl6IRC".Str,
+ "#perl6bot".Str,
+ "End of NAMES list".Str,
+ ],
+ pipe => { },
+ who => {
+ host => "irc.example.net".Str,
+ },
+ }
+
+ # method irc-join ($irc, $e) { ... }
+ {
+ command => "JOIN".Str,
+ params => [
+ "#perl6bot".Str,
+ ],
+ pipe => { },
+ who => {
+ host => "localhost".Str,
+ nick => "ZoffixW".Str,
+ user => "~ZoffixW".Str,
+ },
+ }
+
+ # method irc-privmsg ($irc, $e) { ... }
+ {
+ command => "PRIVMSG".Str,
+ params => [
+ "#perl6bot".Str,
+ "Perl6IRC, hello!".Str,
+ ],
+ pipe => { },
+ who => {
+ host => "localhost".Str,
+ nick => "ZoffixW".Str,
+ user => "~ZoffixW".Str,
+ },
+ }
+
+ # method irc-notice-me ($irc, $e) { ... }
+ {
+ command => "NOTICE".Str,
+ params => [
+ "Perl6IRC".Str,
+ "you there?".Str,
+ ],
+ pipe => { },
+ who => {
+ host => "localhost".Str,
+ nick => "ZoffixW".Str,
+ user => "~ZoffixW".Str,
+ },
+ }
+```
+
+The second argument to event handlers is the parsed IRC message that is a
+hash with the following keys:
+
+### `command`
+
+```perl6
+ command => "NOTICE".Str,
+```
+Contains the IRC command this message represents.
+
+### `params`
+
+```perl6
+ params => [
+ "Perl6IRC".Str,
+ "you there?".Str,
+ ],
+```
+Constains the array of parameters for the IRC command.
+
+### `pipe`
+
+```perl6
+ pipe => { },
+```
+This is a special key that can be used for communication between plugins.
+While any plugin can modify any key of the parsed command's hash, the provided
+`pipe` hash is simply a means to provide some standard, agreed-upon name
+of a key to pass information around.
+
+### `who`
+
+```perl6
+ #fdss
+ who => {
+ host => "localhost".Str,
+ nick => "ZoffixW".Str,
+ user => "~ZoffixW".Str,
+ },
+
+ who => {
+ host => "irc.example.net".Str,
+ },
+```
+A hash containing information on who sent the message. Messages sent by the
+server do not have `nick`/`user` keys specified.
# REPOSITORY
@@ -243,7 +578,7 @@ https://github.com/zoffixznet/perl6-IRC-Client/issues
# AUTHOR
-http://zoffix.com/
+Zoffix Znet (http://zoffix.com/)
# LICENSE