package POE::Component::IRC::Plugin::WWW::Lipsum; use warnings; use strict; our $VERSION = '0.0102'; use base 'POE::Component::IRC::Plugin::BasePoCoWrap'; use POE::Component::WWW::Lipsum; sub _make_default_args { return ( response_event => 'irc_lipsum', trigger => qr/^lipsum\s*/i, line_lengths => { public => 350, notice => 350, privmsg => 350, }, max_lines => { public => 1, notice => 5, privmsg => 5, }, ); } sub _make_poco { my $self = shift; if ( not ref $self->{max_lines} ) { $self->{max_lines} = { public => $self->{max_lines}, notice => $self->{max_lines}, privmsg => $self->{max_lines}, }; } else { $self->{max_lines} = { public => 1, notice => 5, privmsg => 5, %{ $self->{max_lines} }, }; } if ( not ref $self->{line_lengths} ) { $self->{line_lengths} = { public => $self->{line_lengths}, notice => $self->{line_lengths}, privmsg => $self->{line_lengths}, }; } else { $self->{line_lengths} = { public => 350, notice => 350, privmsg => 350, %{ $self->{line_lengths} }, }; } return POE::Component::WWW::Lipsum->spawn( debug => $self->{debug}, ); } sub _make_response_message { my ( $self, $in_ref ) = @_; if ( $in_ref->{error} ) { return [ $in_ref->{error} ]; } my $text = join ' ', @{ $in_ref->{lipsum} }; $text =~ s/\s+/ /g; my $line_max_length = $self->{line_lengths}{ $in_ref->{_type} } || 350; while ( length( $text ) > $line_max_length ) { push @{ $in_ref->{out} }, substr $text, 0, $line_max_length; $text = substr $text, $line_max_length; } push @{ $in_ref->{out} }, $text; my $line_num_max = $self->{max_lines}{ $in_ref->{_type} }; unless ( defined $line_num_max ) { if ( $in_ref->{_type} eq 'public' ) { $line_num_max = 1; } else { $line_num_max = 5; } } @{ $in_ref->{out} } = splice @{ $in_ref->{out} }, 0, $line_num_max; return $in_ref->{out}; } sub _make_response_event { my $self = shift; my $in_ref = shift; return { lipsum => $in_ref->{lipsum}, ( exists $in_ref->{error} ? ( error => $in_ref->{error} ) : ( out => $in_ref->{out}, ) ), map { $_ => $in_ref->{"_$_"} } qw( who channel message type what ), } } sub _make_poco_call { my $self = shift; my $data_ref = shift; my %args; @args{ qw/amount what start html/ } = map lc, split m|[/\s,]+|, $data_ref->{what}; $args{what} ||= 'words'; $args{amount} ||= '15'; if ( $args{html} =~ /yes/ ) { $args{html} = 1 } else { delete $args{html}; } my %max_amount_for = ( words => 7000, paras => 100, lists => 100, bytes => 56000, ); if ( $args{amount} > $max_amount_for{ $args{what} } ) { $args{amount} = $max_amount_for{ $args{what} }; } $self->{poco}->generate( { event => '_poco_done', args => \%args, map +( "_$_" => $data_ref->{$_} ), keys %$data_ref, } ); } 1; __END__ =head1 NAME POE::Component::IRC::Plugin::WWW::Lipsum - plugin to generate Lorem Ipsum text in IRC =head1 SYNOPSIS use strict; use warnings; use POE qw(Component::IRC Component::IRC::Plugin::WWW::Lipsum); my $irc = POE::Component::IRC->spawn( nick => 'LipsumBot', server => 'irc.freenode.net', port => 6667, ircname => 'Lorem Ipsum Bot', plugin_debug => 1, ); POE::Session->create( package_states => [ main => [ qw(_start irc_001) ], ], ); $poe_kernel->run; sub _start { $irc->yield( register => 'all' ); $irc->plugin_add( 'lipsum' => POE::Component::IRC::Plugin::WWW::Lipsum->new ); $irc->yield( connect => {} ); } sub irc_001 { $_[KERNEL]->post( $_[SENDER] => join => '#zofbot' ); } LipsumBot, lipsum Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut velit lectus, ullamcorper non, sagittis id. LipsumBot, lipsum 10 Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Mauris volutpat. LipsumBot, lipsum 10/paras Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Curabitur sodales justo in nibh. Aenean placerat pretium nisl. Nulla enim arcu, porta in, molestie nec, consequat sed, nisi. Quisque eu urna. In hac habitasse platea dictumst. Sed sed augue. Pellentesque pellentesque fringilla pede. Nulla pharetra mattis dui. Donec diam ligula, imperdiet et, LipsumBot, lipsum 10/paras/no Fusce dignissim, urna quis posuere cursus, erat est elementum dolor, non sollicitudin ligula nisl sed enim. Vivamus magna mi, pretium in, blandit non, ultrices ac, velit. Morbi nisl. Aenean quam massa, faucibus a, adipiscing at, sollicitudin nec, eros. Morbi pellentesque, erat ac porttitor ultricies, lacus arcu congue dolor, at malesuada urna nunc LipsumBot, lipsum 10/paras/no/1

Aliquam quis est eget nulla ornare volutpat. Mauris a sapien. Nullam interdum justo quis metus. Quisque ultricies est eget dolor. Suspendisse nec neque nec diam semper gravida. In in odio in purus scelerisque sagittis. Nam suscipit quam vel lorem. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Praesent i LipsumBot, lipsum 10 paras no 1

Suspendisse potenti. Ut ligula libero, posuere ac, euismod sit amet, dignissim eu, quam. Donec massa. Cras mollis pulvinar risus. Aenean porta porttitor nulla. Suspendisse potenti. Etiam nulla nisi, scelerisque vel, consequat vitae, ultrices aliquam, mauris. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; =head1 DESCRIPTION This module is a L plugin which uses L for its base. It provides interface to get Lorem Ipsum text generated by L. It accepts input from public channel events, C messages as well as C (private messages); although that can be configured at will. =head1 PLUGIN IRC COMMAND SYNTAX LipsumBot, lipsum [AMOUNT] [WHAT] [START WITH LOREM] [MAKE HTML] All arguments are optional. Plugin can be triggered without any arguments, if that's the case then plugin will output 15 words of Lorem Ipsum text. Arguments can be separated either by whitespace, the C character or C<,> character. You cannot skip arguments, if you want to generate 15 paragraphs you B use C even though 15 is the default for C. (proper use is C) =head2 C argument LipsumBot, lipsum 20 The C argument takes a positive integer which represents how many of C (see below) to generate. B C<15> To prevent extremely creative people lagging out the plugin the following maximum values for the C argument are imposed depending on the kind of C argument (see below) used: words => 7000, paras => 100, lists => 100, bytes => 56000, Currently these limits are not configurable. Let me know if you need them to be so. =head2 C argument LipsumBot, lipsum 20 paras The C argument specifies what kind of entity to generate, possible values are: paras - generate paragraphs words - generate words bytes - generate bytes lists - generate lists With C and C the C argument (see below) plays a role. B C =head2 C argument LipsumBot, lipsum 20 words no Specifies whether or not the generated text should start with "Lorem ipsum dolor sit amet". There are only two possible values: C and C. B C =head2 C argument LipsumBot, lipsum 20 paras no yes Applies only when C is set to either C or C. Indicates whether or not the plugin should wrap paragraphs into C<<

>> or C<<

  • >> HTML elements. There are only two possible values: C and C. B C =head1 CONSTRUCTOR =head2 C # plain and simple $irc->plugin_add( 'WWW::Lipsum' => POE::Component::IRC::Plugin::WWW::Lipsum->new ); # juicy flavor $irc->plugin_add( 'WWW::Lipsum' => POE::Component::IRC::Plugin::WWW::Lipsum->new( auto => 1, response_event => 'irc_lipsum', banned => [ qr/aol\.com$/i ], addressed => 1, line_lengths => 350, max_lines => 5, root => [ qr/mah.net$/i ], trigger => qr/^lipsum\s*/i, triggers => { public => qr/^EXAMPLE\s*/i, notice => qr/^EXAMPLE\s*/i, privmsg => qr/^EXAMPLE\s*/i, }, listen_for_input => [ qw(public notice privmsg) ], eat => 1, debug => 0, ) ); The C method constructs and returns a new C object suitable to be fed to L's C method. The constructor takes a few arguments, but I. The possible arguments/values are as follows: =head3 C ->new( auto => 0 ); B. Takes either true or false values, specifies whether or not the plugin should auto respond to requests. When the C argument is set to a true value plugin will respond to the requesting person with the results automatically. When the C argument is set to a false value plugin will not respond and you will have to listen to the events emited by the plugin to retrieve the results (see EMITED EVENTS section and C argument for details). B C<1>. =head3 C line_lengths => 350, line_lengths => { public => 100, notice => 200, privmsg => 350, } B. Specifies the length of one "line" the plugin will output, but line is ment one message sent to IRC. The value can be either a hashref or a scalar. When the value is a hashref, possible keys of it are C, C and C which correspond to appropriate type of IRC messages, where C is the message which came from the channel. If you omit a certain key, it will take on its default value. Thus the following two are equivalent: line_lengths => { public => 300 } line_lengths => { public => 300, notice => 350, privmsg => 350, } You can also specify a scalar value to C key, in this case all of the keys (C, C and C) will be set to that value. B C<350> for all message types. =head3 C max_lines => 5, max_lines => { public => 1, notice => 8, privmsg => 8, }, B. Specifies the maximum number of "lines" (see the C argument for definition of "lines" in this context) which plugin will output. As a value takes either a scalar or a hashref, the same principles as for C argument apply to C as well. B C<1> for C messages and C<5> for C and C messages. =head3 C ->new( response_event => 'event_name_to_recieve_results' ); B. Takes a scalar string specifying the name of the event to emit when the results of the request are ready. See EMITED EVENTS section for more information. B C =head3 C ->new( banned => [ qr/aol\.com$/i ] ); B. Takes an arrayref of regexes as a value. If the usermask of the person (or thing) making the request matches any of the regexes listed in the C arrayref, plugin will ignore the request. B C<[]> (no bans are set). =head3 C ->new( root => [ qr/\Qjust.me.and.my.friend.net\E$/i ] ); B. As opposed to C argument, the C argument B access only to people whose usermasks match B of the regexen you specify in the arrayref the argument takes as a value. B it is not specified. B as opposed to C specifying an empty arrayref to C argument will restrict access to everyone. =head3 C ->new( trigger => qr/^lipsum\s*/i ); B. Takes a regex as an argument. Messages matching this regex, irrelevant of the type of the message, will be considered as requests. See also B option below which is enabled by default as well as B option which is more specific. B the trigger will be B from the message, therefore make sure your trigger doesn't match the actual data that needs to be processed. B C =head3 C ->new( triggers => { public => qr/^EXAMPLE\s+(?=\S)/i, notice => qr/^EXAMPLE\s+(?=\S)/i, privmsg => qr/^EXAMPLE\s+(?=\S)/i, } ); B. Takes a hashref as an argument which may contain either one or all of keys B, B and B which indicates the type of messages: channel messages, notices and private messages respectively. The values of those keys are regexes of the same format and meaning as for the C argument (see above). Messages matching this regex will be considered as requests. The difference is that only messages of type corresponding to the key of C hashref are checked for the trigger. B the C will be matched irrelevant of the setting in C, thus you can have one global and specific "local" triggers. See also B option below which is enabled by default as well as B option which is more specific. B the trigger will be B from the message, therefore make sure your trigger doesn't match the actual data that needs to be processed. B not specified (i.e. everything is triggered by C) =head3 C ->new( addressed => 1 ); B. Takes either true or false values. When set to a true value all the public messages must be I. In other words, if your bot's nickname is C and your trigger is C you would make the request by saying C. When addressed mode is turned on, the bot's nickname, including any whitespace and common punctuation character will be removed before matching the C (see above). When C argument it set to a false value, public messages will only have to match C regex in order to make a request. Note: this argument has no effect on C and C requests. B C<1> =head3 C ->new( listen_for_input => [ qw(public notice privmsg) ] ); B. Takes an arrayref as a value which can contain any of the three elements, namely C, C and C which indicate which kind of input plugin should respond to. When the arrayref contains C element, plugin will respond to requests sent from messages in public channels (see C argument above for specifics). When the arrayref contains C element plugin will respond to requests sent to it via C messages. When the arrayref contains C element, the plugin will respond to requests sent to it via C (private messages). You can specify any of these. In other words, setting C<( listen_for_input => [ qr(notice privmsg) ] )> will enable functionality only via C and C messages. B C<[ qw(public notice privmsg) ]> =head3 C ->new( eat => 0 ); B. If set to a false value plugin will return a C after responding. If eat is set to a true value, plugin will return a C after responding. See L documentation for more information if you are interested. B: C<1> =head3 C ->new( debug => 1 ); B. Takes either a true or false value. When C argument is set to a true value some debugging information will be printed out. When C argument is set to a false value no debug info will be printed. B C<0>. =head1 EMITED EVENTS =head2 C $VAR1 = { 'out' => [ 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Pellentesque placerat pede non metus. Vivamus tellus. ' ], 'what' => '', 'who' => 'Zoffix!n=Zoffix@unaffiliated/zoffix', 'type' => 'public', 'channel' => '#zofbot', 'lipsum' => [ 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Pellentesque placerat pede non metus. Vivamus tellus. ' ], 'message' => 'LipsumBot, lipsum' }; The event handler set up to handle the event, name of which you've specified in the C argument to the constructor (it defaults to C) will recieve input every time request is completed. The input will come in C<$_[ARG0]> on a form of a hashref. The possible keys/values of that hashrefs are as follows: =head3 C 'out' => [ 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Pellentesque placerat pede non metus. Vivamus tellus. ' ], The C key will contain an arrayref of the messages (or "lines") sent to IRC. The content here is affected by C and C constructor arguments. =head3 C 'lipsum' => [ 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Pellentesque placerat pede non metus. Vivamus tellus. ' ], The C key will contain Lorem Ipsum text B it was chopped up and limited by C and C constructor arguments. =head3 C { 'who' => 'Zoffix!Zoffix@i.love.debian.org', } The C key will contain the user mask of the user who sent the request. =head3 C { 'what' => '20 paras yes no', } The C key will contain user's message after stripping the C (see CONSTRUCTOR). =head3 C { 'message' => 'LipsumBot, lipsum 20 paras yes no' } The C key will contain the actual message which the user sent; that is before the trigger is stripped. =head3 C { 'type' => 'public', } The C key will contain the "type" of the message the user have sent. This will be either C, C or C. =head3 C { 'channel' => '#zofbot', } The C key will contain the name of the channel where the message originated. This will only make sense if C key contains C. =head1 SEE ALSO L, L, L =head1 AUTHOR Zoffix Znet, C<< >> (L, L) =head1 BUGS Please report any bugs or feature requests to C, or through the web interface at L. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. =head1 SUPPORT You can find documentation for this module with the perldoc command. perldoc POE::Component::IRC::Plugin::WWW::Lipsum You can also look for information at: =over 4 =item * RT: CPAN's request tracker L =item * AnnoCPAN: Annotated CPAN documentation L =item * CPAN Ratings L =item * Search CPAN L =back =head1 COPYRIGHT & LICENSE Copyright 2008 Zoffix Znet, all rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. =cut