comment on

It might be very instructive to show before and after versions of the scripts.

You can do that easily enough at the moment by pulling down my versions and comparing them with Matt's. I might consider putting Matt's versions in my distribution as a lesson to us all, but I think he's quite protective on things like that.

Finally, CPAN has a scripts archive, though it isn't widely used.

The deputy librarian of CPAN has already shown great interest in these scripts. They will, no doubt, appear there in due course.

I would recommend writing modules which can be scripted via it's API instead of writing scripts proper.

There's a chance that something like that might happen much later. The problem is that Matt's scripts are so popular precisely because they are so easy to use. There's no need to install modules from CPAN or do anything that a novice webmaster might find confusing. If these scripts are to find any kind of popularity they have to be just as simple to use.

--
<http://www.dave.org.uk>

Perl Training in the UK <http://www.iterative-software.com>

In reply to Re: Re: Not Matt's Scripts by davorg
in thread Not Matt's Scripts by davorg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks