I agree - it will probably be best to accept the project just as any other shrink wrapped system we buy.
I is a terrible shame though that all the effort that has gone into this project has ended with such a poor result. If it had been done according to 'proper' software engineering methods, it could have been augmented with you referrer-scanning logic and my additions.
It does make the program less useful because you and I have had to do something else, and thus we have had to spread our tuits. The program could have saved us valuable time for something vital (like playing with the dogs) instead of having to do something that has beeen done many times already. If the implementation is 'nice' (from an engineering point of view) it adds considerable value. OK: it does as advertised, but extra value can be had if it is possible to reuse parts of it in new and unforseen ways. I think that perl (and Perl) is a good example of this.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||