Class Irc::Bot::MessageMapper
In: lib/rbot/messagemapper.rb
Parent: Object
BasicUserMessage JoinMessage NamesMessage WhoisMessage ModeChangeMessage KickMessage MotdMessage QuitMessage BanlistMessage UserMessage NoSuchTargetMessage TopicMessage NickMessage WelcomeMessage UnknownMessage InviteMessage PartMessage NetmaskList UserList ArrayOf ChannelList Netmask User\n[lib/rbot/botuser.rb\nlib/rbot/irc.rb] Channel Singleton RfcCasemap StrictRfcCasemap AsciiCasemap Casemap PrivMessage NoticeMessage TokyoCabinet::BDB CIBDB Btree CIBtree Socket MessageQueue QueueRing Client DBHash\n[lib/rbot/registry/bdb.rb\nlib/rbot/registry/tc.rb] DBTree\n[lib/rbot/registry/bdb.rb\nlib/rbot/registry/tc.rb] Server NetmaskDb Bot\n[lib/rbot/botuser.rb\nlib/rbot/config.rb\nlib/rbot/ircbot.rb\nlib/rbot/language.rb\nlib/rbot/message.rb\nlib/rbot/messagemapper.rb\nlib/rbot/plugins.rb\nlib/rbot/rbotconfig.rb\nlib/rbot/registry/bdb.rb\nlib/rbot/registry/tc.rb] lib/rbot/ircsocket.rb lib/rbot/rfc2812.rb lib/rbot/registry/tc.rb lib/rbot/irc.rb lib/rbot/maskdb.rb lib/rbot/message.rb lib/rbot/messagemapper.rb lib/rbot/botuser.rb lib/rbot/registry/tc.rb (null) BotConfig PKGConfig ServerOrCasemap Irc dot/m_35_0.png

MessageMapper is a class designed to reduce the amount of regexps and string parsing plugins and bot modules need to do, in order to process and respond to messages.

You add templates to the MessageMapper which are examined by the handle method when handling a message. The templates tell the mapper which method in its parent class (your class) to invoke for that message. The string is split, optionally defaulted and validated before being passed to the matched method.

A template such as "foo :option :otheroption" will match the string "foo bar baz" and, by default, result in method foo being called, if present, in the parent class. It will receive two parameters, the message (derived from BasicUserMessage) and a Hash containing

  {:option => "bar", :otheroption => "baz"}

See the map method for more details.

Methods

each   handle   last   map   new  

Classes and Modules

Class Irc::Bot::MessageMapper::Failure
Class Irc::Bot::MessageMapper::FriendlyFailure
Class Irc::Bot::MessageMapper::NoActionFailure
Class Irc::Bot::MessageMapper::NoMatchFailure
Class Irc::Bot::MessageMapper::NotPrivateFailure
Class Irc::Bot::MessageMapper::NotPublicFailure
Class Irc::Bot::MessageMapper::PartialMatchFailure

Attributes

fallback  [W]  used to set the method name used as a fallback for unmatched messages. The default fallback is a method called "usage".

Public Class methods

parent:parent class which will receive mapped messages

Create a new MessageMapper with parent class parent. This class will receive messages from the mapper via the handle() method.

[Source]

     # File lib/rbot/messagemapper.rb, line 114
114:     def initialize(parent)
115:       @parent = parent
116:       @templates = Array.new
117:       @fallback = :usage
118:     end

Public Instance methods

Iterate over each MessageTemplate handled.

[Source]

     # File lib/rbot/messagemapper.rb, line 227
227:     def each
228:       @templates.each {|tmpl| yield tmpl}
229:     end
m:derived from BasicUserMessage

Examine the message m, comparing it with each map()’d template to find and process a match. Templates are examined in the order they were map()’d - first match wins.

Returns true if a match is found including fallbacks, false otherwise.

[Source]

     # File lib/rbot/messagemapper.rb, line 244
244:     def handle(m)
245:       return false if @templates.empty?
246:       failures = []
247:       @templates.each do |tmpl|
248:         options = tmpl.recognize(m)
249:         if options.kind_of? Failure
250:           failures << options
251:         else
252:           action = tmpl.options[:action]
253:           unless @parent.respond_to?(action)
254:             failures << NoActionFailure.new(tmpl, m)
255:             next
256:           end
257:           auth = tmpl.options[:full_auth_path]
258:           debug "checking auth for #{auth}"
259:           if m.bot.auth.allow?(auth, m.source, m.replyto)
260:             debug "template match found and auth'd: #{action.inspect} #{options.inspect}"
261:             if !m.in_thread && (tmpl.options[:thread] || tmpl.options[:threaded])
262:               Thread.new do
263:                 begin
264:                   @parent.send(action, m, options)
265:                 rescue Exception => e
266:                   error "In threaded action: #{e.message}"
267:                   debug e.backtrace.join("\n")
268:                 end
269:               end
270:             else
271:               @parent.send(action, m, options)
272:             end
273: 
274:             return true
275:           end
276:           debug "auth failed for #{auth}"
277:           # if it's just an auth failure but otherwise the match is good,
278:           # don't try any more handlers
279:           return false
280:         end
281:       end
282:       failures.each {|r|
283:         debug "#{r.template.inspect} => #{r}"
284:       }
285:       debug "no handler found, trying fallback"
286:       if @fallback && @parent.respond_to?(@fallback)
287:         if m.bot.auth.allow?(@fallback, m.source, m.replyto)
288:           @parent.send(@fallback, m, {:failures => failures})
289:           return true
290:         end
291:       end
292:       return false
293:     end

Return the last added MessageTemplate

[Source]

     # File lib/rbot/messagemapper.rb, line 232
232:     def last
233:       @templates.last
234:     end
botmodule:the BotModule which will handle this map
template:a String describing the messages to be matched
options:a Hash holding variouns options

This method is used to register a new MessageTemplate that will map any BasicUserMessage matching the given template to a corresponding action. A simple example:

  plugin.map 'myplugin :parameter'

(other examples follow).

By default, the action to which the messages are mapped is a method named like the first word of the template. The

  :action => 'method_name'

option can be used to override this default behaviour. Example:

  plugin.map 'myplugin :parameter', :action => 'mymethod'

By default whether a handler is fired depends on an auth check. In rbot versions up to 0.9.10, the first component of the string was used for the auth check, unless overridden via the :auth => ‘auth_name’ option. Since version 0.9.11, a new auth method has been implemented. TODO document.

Static parameters (not prefixed with ’:’ or ’*’) must match the respective component of the message exactly. Example:

  plugin.map 'myplugin :foo is :bar'

will only match messages of the form "myplugin something is somethingelse"

Dynamic parameters can be specified by a colon ’:’ to match a single component (whitespace separated), or a * to suck up all following parameters into an array. Example:

  plugin.map 'myplugin :parameter1 *rest'

You can provide defaults for dynamic components using the :defaults parameter. If a component has a default, then it is optional. e.g:

  plugin.map 'myplugin :foo :bar', :defaults => {:bar => 'qux'}

would match ‘myplugin param param2’ and also ‘myplugin param’. In the latter case, :bar would be provided from the default.

Static and dynamic parameters can also be made optional by wrapping them in square brackets []. For example

  plugin.map 'myplugin :foo [is] :bar'

will match both ‘myplugin something is somethingelse’ and ‘myplugin something somethingelse’.

Components can be validated before being allowed to match, for example if you need a component to be a number:

  plugin.map 'myplugin :param', :requirements => {:param => /^\d+$/}

will only match strings of the form ‘myplugin 1234’ or some other number.

Templates can be set not to match public or private messages using the :public or :private boolean options.

Summary of recognized options:

action:method to call when the template is matched
auth_path:TODO document
requirements:a Hash whose keys are names of dynamic parameters and whose values are regular expressions that the parameters must match
defaults:a Hash whose keys are names of dynamic parameters and whose values are the values to be assigned to those parameters when they are missing from the message. Any dynamic parameter appearing in the :defaults Hash is therefore optional
public:a boolean (defaults to true) that determines whether the template should match public (in channel) messages.
private:a boolean (defaults to true) that determines whether the template should match private (not in channel) messages.
threaded:a boolean (defaults to false) that determines whether the action should be called in a separate thread.

Further examples:

  # match 'karmastats' and call my stats() method
  plugin.map 'karmastats', :action => 'stats'
  # match 'karma' with an optional 'key' and call my karma() method
  plugin.map 'karma :key', :defaults => {:key => false}
  # match 'karma for something' and call my karma() method
  plugin.map 'karma for :key'

  # two matches, one for public messages in a channel, one for
  # private messages which therefore require a channel argument
  plugin.map 'urls search :channel :limit :string',
            :action => 'search',
            :defaults => {:limit => 4},
            :requirements => {:limit => /^\d+$/},
            :public => false
  plugin.map 'urls search :limit :string',
            :action => 'search',
            :defaults => {:limit => 4},
            :requirements => {:limit => /^\d+$/},
            :private => false

[Source]

     # File lib/rbot/messagemapper.rb, line 222
222:     def map(botmodule, *args)
223:       @templates << MessageTemplate.new(botmodule, *args)
224:     end

[Validate]