It's just a light wrapper on LPW, but then it's exacly what is needed to use Paypal: no loads of dependencies such as SOAP (it uses the NVP Paypal interface) and a very lightweight module which basically just avoids the need to write boilerplate code.
Everything is forwarded as-is to Paypal, so the Paypal developer documentation is the only thing you need.
This Catalyst plugin does a good job of resolving the issue of passing status messages between pages.
It works well and the documentation is clear.
A possible improvement which comes to my mind is not lot limit it to 2 kind of messages (error_message and status_message) but to be able to configure an indefinite number of them. However I'll only understand as I use the plugin if it's actually an interesting feature or not.
Email::Sender is a great module for sending emails: it aims to and it should become the standard for sending emails using Perl. There are way too many modules out there now, and not all of them work as they should.
Even though there is some useful documentation (Manual::QuickStart and the source code of course), it really needs comprehensive doc to be written.
Very nice module to create multipart emails. Used together with Email::Sender become a full-featured and also easy to use way to create and send e-mails, multipart or not, using a variety of transports.
Very useful module: I use XUL (Takahashi) slides and almost all events where I speak want some PDF for their archival.
Even though I think something could be done reimplementing the Takahashi thing in Perl and then using PDF::API2, this solution through PPT works well. Only thing is that text in the final PPT is not text but an image, but it's likely a minor problem.
Although the documentation states it's been obsoleted by CHI, this is the only one good in non persistent-application environments (fex. CGI or even mod_perlite), as CHI is based on Moose and therefore (presently) slow to load.
This module would benefit from an option to use the SVN libs already on the system. The bundled Subversion 1.4 (which is a bit old, actually) seems to be not installable on my Gentoo Linux (but I have 1.6.4 installed and working).
DBIx::Simple is sugar spread on DBI (it should really have been named DBI::Sweet). It's usage will make you code far more readable, quicker to write, and with a lot less boilerplate code.
This is my #1 choice for database management, as using the DBI directly requires some tedious coding which is senseless to do by hand.
DBIx::Simple, even though it does provide optional query abstraction through SQL::Abstract, does not feature database abstraction. For that you should take a look at more advanced modules such as DBIx::Class and Rose::DB::Object. However, for the quick and simple case, DBIx::Simple just rocks.
Nice thing to play with, but should not really be a choice or we would end up having modules developed with too many different class systems (which already happens, to a degree, even though Moose is trying to save us).