Nice work! I like being able to see this info in a graphical context. I only have a couple of suggestions for improving it. These came up through personal trial and error trying to get this to run for myself.
- Suggest using something else than PerlMonksChat for getting a user's page. This one gave me a lot of problems, and I ended up throwing it away in favor of a request that looks like this :
my $url ="$pmsite?user=$username&"
(Code shamelessly stolen from jcwren's luke_repwalker.pl). This brings up point 2,
- Some people (not myself..yet) have more than 50 writeups, so the url query will have to be repeated multiple times in order to get all writeups. Granted, your code will give a good synopsis, but I imagine there are people out there who want all the info at once. For an example of how to do multiple fetches to get all of the writeups, look again to luke_repwalker
Other than those suggestions, I would say your code works great for me.Update (2):
Fixed the code wrap. Thnx nuance
Negaterd character class uber alles!
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.