Moxilnet: SMS toolbar v0.1 released

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

Change Toolbar to Opt In?

Hey! I'm thinking we should change the toolbar to "opt in" and have it off for members by default? But then, the would not have toolbar access to the code tag videos, etc. so then I thought to make it "opt in" after say 30 posts. That way, the toolbar will show to all new users with less...

2. What is on Your Mind?

Should We Keep or Drop the Bottom Toolbar?

Well, it's been a few months now since we started running the toolbar on the bottom with some navigation menu, search, link to code tag video, some social networking tools, etc. So, the question of the day is: Should we keep it, maybe develop more toolbar apps, or dump it? Please vote ...

3. UNIX for Dummies Questions & Answers

HP-UX toolbar help

Hi all, I am trying to set some icons in the toolbar thingy (HP-UX 10.2). I used the Toolboxes->Personal to help me setup, but it put the program icon in the personal toolbox folder. So I dragged it out to the Desktop. Now I've a link on a Desktop. Any ideas on how to create directly on to...

LEARN ABOUT DEBIAN

sms::send::driver

SMS::Send::Driver(3pm)					User Contributed Perl Documentation				    SMS::Send::Driver(3pm)

NAME

       SMS::Send::Driver - Base class for SMS::Send drivers

DESCRIPTION

       The "SMS::Send::Driver" class provides an abstract base class for all SMS::Send driver classes.

       At this time it does not provide any implementation code for drivers (although this may change in the future) with the exception of some
       methods provided to trigger "does not implement method" errors.

       However, it does serve as something you should sub-class your driver from to identify it as a SMS::Send driver.

       Please note that if your driver class not not return true for "$driver-"isa('SMS::Send::Driver')> then the SMS::Send constructor will
       refuse to use your class as a driver.

METHODS

   new
       The "new" constructor is required to be implemented by your driver subclass.

       It recieves a set of arbitrary paired params. The values of these params are assumed to be driver-specific (this is expected to change).

       If your driver will need to login to some system, locate hardware, or do some other form of initialisation to validate the SMS delivery
       mechanism exists, it should do so in "new".

       Should return a new SMS::Send::Driver-subclass object, or die on error.

   send_sms
       The "send_sms" method is required to be implemented by your driver subclass.

       It recieves a set of param pairs as documented in SMS::Send.

       Should return true for either success or fire-and-forget with unknown result, defined-but-false ('' or 0) for a failed message send, or die
       on a fatal error.

SUPPORT

       Bugs should be reported via the CPAN bug tracker at

       http://rt.cpan.org/NoAuth/ReportBug.html?Queue=SMS-Send <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=SMS-Send>

       For other issues, contact the author.

AUTHOR

       Adam Kennedy <adamk@cpan.org>

COPYRIGHT

       Copyright 2005 - 2011 Adam Kennedy.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

       The full text of the license can be found in the LICENSE file included with this module.

perl v5.14.2							    2011-11-09						    SMS::Send::Driver(3pm)

Software Releases - RSS News