Hey all- I've got three new modules that I'd like to have registered on the module list if there are no objections: Name DSLI Description ---------------- ---- -------------------------------------------- Class::Handler bdph Make Apache-like pseudoclass event handlers Text::Header Rdpf RFC 822/2068 header manipulation functions HTML::ActiveLink adp0 Dynamically activate HTML links based on URL The first one is unique to CPAN; it just plays tricks with AUTOLOAD and @ISA so that it can create classes which inherit from others but don't provide methods of their own. This has actually turned out to be pretty handy since it lets you create "event handlers". The Text::Header module provides header() and unheader() functions that tweak SMTP/HTTP/etc headers. They are generalized and extensible versions of similar functions found in CGI.pm and HTTP::Headers. They're designed to work with any text processing, hence the reason they live in Text::, and are content independent. Finally, the HTML::ActiveLink module provides a lightweight yet useful method for auto-parsing and activation of HTML links. What this means is that you can create an HTML template that looks like this: <a href="/">Home</a> | <a href="/faq/">FAQ</a> And then run this code across the CGI or elsewhere: $al = new HTML::ActiveLink; print $al->activelink($html_doc); And if you were running in the /faq/ directory the above HTML would become something like this: <a href="/">Home</a> | <font color="red">FAQ</font> Since it's separate, this can be used with HTML::Template or MASON or other modules without tying the author to any one particular formatting module. It's also much more flexible than this simplistic example shows. In any event, if you could please give me some feedback as to whether these are valid namespaces, etc, I'd really appreciate it. If all is well, then I'd like to get these registered under my name on CPAN. Thanks as always, Nate
